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

# API and Integration Questions

> Where to take builder and integrator questions about the Intention API, protocol internals, and commercial integrations.

This page routes builder and integrator questions to the right place. Pick the category that fits and follow the instructions there.

<Note>
  The full API reference is published at [openapi.intention-testnet.xyz](https://openapi.intention-testnet.xyz) and the developer site at [dev.intention.xyz](https://dev.intention.xyz/). Payload shapes are still moving in places, so email is faster than the spec for anything that looks inconsistent.
</Note>

## Questions about API usage

If you are integrating ahead of the published reference, email `contact@intention.xyz` with a one-line description of what you are building and the endpoints you expect to need. The integration team can share the working shape of the surface and flag anything likely to change before launch.

Once you are running against an endpoint and it behaves differently than expected, email `contact@intention.xyz` and include the request body, the response body, the relevant headers, and the UTC time of the call. Tickets that cite the offending payload and the observed response are usually resolved within a single round-trip, because the integration team can replay them directly against staging.

## Questions about protocol internals

If you are trying to understand why the protocol behaves a certain way — matching semantics, sequencing guarantees, fee flow, margin math, oracle certification — start with the architecture section of this site. The [IntentionKernel](/protocol/architecture/kernel) page covers execution; [IntentionBFT](/protocol/architecture/intention-bft) covers consensus; the [Bridge](/protocol/architecture/bridge) page covers deposits and withdrawals. If after reading those you still have a question that is architectural rather than operational, email `contact@intention.xyz` with a one-paragraph framing of what you are trying to reason about and which page you started from. The protocol team triages those questions and either answers directly or commissions a docs improvement so the next reader doesn't have to ask.

## Commercial integration

Partnerships, listings, market-making agreements, and anything that implies a business relationship go to `contact@intention.xyz`. Include a one-line description of what you are building, who you are, and what you need from Intention Labs to make it work. A clear first message reduces back-and-forth substantially.

## Security disclosures

Security issues — anything you would not want a random person on the internet to see before there is a fix — go to `contact@intention.xyz` with **Security** in the subject line, so they are routed ahead of ordinary mail. The program rules are on the [Bug bounty](/protocol/security/bug-bounty) page. Read that page before submitting; following the documented procedure is how you qualify for the bounty.

## Summary

| Topic                            | What to include                                                                                         |
| -------------------------------- | ------------------------------------------------------------------------------------------------------- |
| An endpoint behaves unexpectedly | Request body, response body, headers, and the UTC time of the call                                      |
| A protocol document is ambiguous | Which page you started from, and what you were trying to reason about                                   |
| Commercial integration           | What you are building, who you are, and what you need from Intention Labs                               |
| Security disclosure              | Put **Security** in the subject line and follow the [bug bounty](/protocol/security/bug-bounty) process |

Everything goes to `contact@intention.xyz`. A clear first message reduces back-and-forth substantially.