The full API reference is published at openapi.intention-testnet.xyz and the developer site at dev.intention.xyz. Payload shapes are still moving in places, so email is faster than the spec for anything that looks inconsistent.
Questions about API usage
If you are integrating ahead of the published reference, emailcontact@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 page covers execution; IntentionBFT covers consensus; the Bridge page covers deposits and withdrawals. If after reading those you still have a question that is architectural rather than operational, emailcontact@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 tocontact@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 tocontact@intention.xyz with Security in the subject line, so they are routed ahead of ordinary mail. The program rules are on the Bug bounty page. Read that page before submitting; following the documented procedure is how you qualify for the bounty.
Summary
Everything goes to
contact@intention.xyz. A clear first message reduces back-and-forth substantially.