> ## 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 public API surface has not yet been finalized. Endpoints, payload shapes, and authentication flows may change before the first production release. Treat any current documentation as a working draft until the mainnet API is announced.
</Note>

## Questions about API usage

The [API reference](/api-reference/introduction) is the canonical description of every endpoint Intention exposes. Before asking a question, check that the endpoint you are calling exists in the reference and that your payload matches the schema published there. A large fraction of integration tickets resolve immediately once the request is validated against the schema.

If the reference is unclear, or if an endpoint behaves differently than documented, email `support@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](/architecture/intention-kernel) page covers execution; [IntentionBFT](/architecture/intention-bft) covers consensus; the [Bridge](/architecture/bridge) page covers deposits and withdrawals. If after reading those you still have a question that is architectural rather than operational, email `support@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 and builder codes

Partnerships, builder-code arrangements, 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 — do not go to `contact@intention.xyz` and do not go to the general support mailbox. They go to `security@intention.xyz`, and the program rules are on the [Bug bounty](/risk-security/bug-bounty) page. Please read that page before submitting; following the documented procedure is how you qualify for the bounty.

## Summary

| Topic                                       | Channel                                                              |
| ------------------------------------------- | -------------------------------------------------------------------- |
| API endpoint behaves wrong                  | `support@intention.xyz`                                              |
| Ambiguous protocol doc                      | `support@intention.xyz`                                              |
| Commercial integration                      | `contact@intention.xyz`                                              |
| Security disclosure                         | `security@intention.xyz` and [Bug bounty](/risk-security/bug-bounty) |
| Everything else about building on Intention | `support@intention.xyz`                                              |