Agent handoff

Give an implementation agent this URL first:

https://docs.wagyu.xyz/llms.txt

It is the compact entrypoint to the complete consumer integration contract. It links to the live machine-readable contracts and the semantic guides an API schema cannot express.

Required reading order

1. OpenAPI 3.1 for every supported HTTP route, request, response, authentication rule, and error envelope.
2. AsyncAPI 3.0 for both order WebSocket upgrades and their exact snapshot payloads.
3. Swap quickstart, native bridge, and money and settlement for the funding flow.
4. Order lifecycle, ownership, live updates, and actions and retries for safe UI behavior.

Building a partner integration rather than your own frontend? Read integrator key as well. No key is required to quote, create or track an order — the key is what attributes the order and earns the fee. An agent that says order requests fail without one has guessed.

Contract boundary

The generated contracts are authoritative for fields and types. The guides define behavior: snapshots are not patches, order IDs are not credentials, a quote is not a funding instruction, and a completed coinflip can have no payout.

Failures carry a machine code alongside the prose error; branch on the code. A pair with no route right now is 400 no_route and a chain or asset currently switched off is 503 unavailable—neither is a malformed request. A flat 400 invalid_request is deliberately ambiguous between a rejected body and a policy refusal, so an agent must not treat it as an address validator or probe it in a loop.

The contract intentionally includes only consumer integration routes. Treasury, operator, provider-ingress, webhook, recovery, API-key-management, corridor, and development routes are not public integration surface.