> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stateset.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Getting Help

> Where to ask, what to check first, and how problems get resolved — Discord, a call with the team, host status, and the outcome dispute process.

## Check these first

<CardGroup cols={2}>
  <Card title="Host status" icon="activity" href="/api-reference/hosts">
    Probed, with a checked date. If a host says *being provisioned*, a 503 is expected and not
    yours to debug.
  </Card>

  <Card title="Errors across the engines" icon="triangle-alert" href="/api-reference/errors-across-engines">
    Every error envelope side by side, and the five families with what to do about each.
  </Card>

  <Card title="Which API am I calling?" icon="signpost" href="/api-reference/introduction">
    The most common cause of a mystery 401 or 404 is the right key on the wrong engine.
  </Card>

  <Card title="API history" icon="clock" href="/api-reference/commerce/history">
    If a call that used to work stopped, the tab's history page says what changed in the surface.
  </Card>
</CardGroup>

## Ask a person

* **[Discord](https://discord.gg/VfcaqgZywq)** — the fastest path for build questions; the team
  and other builders are in the channel.
* **[Book time with the team](https://calendly.com/stateset)** — onboarding, architecture review,
  or anything commercial.
* **Tell us when a page is wrong** — say so in Discord with the URL; we treat "this page is
  wrong" as a bug report, and the docs are regenerated from the servers' own contracts, so a fix
  usually lands the same day.

## When money is involved

Billing follows the outcome model: outcomes can be **disputed within 14 days**, a dispute lands
as a credit on your next invoice, and the ledger is visible in the billing portal — the process
and the High-Value Action gate are documented in [Billing](/stateset-billing).

<Note>
  When you report an API problem, include the request id from the response (`request_id`,
  `meta.requestId`, or the correlation header, depending on the engine — the
  [errors page](/api-reference/errors-across-engines) says which) and the timestamp. That turns a
  mystery into a lookup.
</Note>