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

# Support

> What partner support covers, and where developers find answers in the docs.

## Partner support

Every partner has a contact at MagicMarkets. Use it for:

* Integration questions the [developer docs](/developers/overview) do not answer.
* Rate limits. Tell us the volume you expect, and we discuss what your integration needs.
* Attribution checks. We run a test signup through your code with you before you send traffic.
* Dividend questions.

Partners cannot change a user's account, balance or settings, or contact support on the user's behalf. For anything about their own account, the user contacts support directly.

## Test against production

There is no separate sandbox. Build against the production API with small amounts, and use the safety features: idempotent placement with a `request_uuid`, heartbeats, and the read-only default in the MCP server built into the `magicmarkets` CLI (command line interface). The CLI's `offers` command reads the live book, and `betslip create` requests a quote without placing an order. See [Safety](/developers/safety).

## Self-serve first

Most of what a developer needs is in the Developers section. Start with the CLI:

<Columns cols={2}>
  <Card title="CLI" icon="square-terminal" href="/developers/tools/cli" />

  <Card title="Quickstart" icon="rocket" href="/developers/quickstart" />

  <Card title="Concepts" icon="lightbulb" href="/developers/concepts" />

  <Card title="API reference" icon="book-open-text" href="/developers/api-reference/introduction" />
</Columns>

The API also publishes machine-readable docs your agents can read directly. See [Machine-readable docs](/developers/tools/machine-readable-docs).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.