/v1.
What can change without notice
Additive changes are not breaking and can land at any time:- New fields in existing responses
- New endpoints, query parameters, chains, and protocols
- New error codes within the documented status families
What gets a new version
Changes that would break a correct client — removing or renaming fields, changing types or semantics, retiring an endpoint — ship under a new version path. Deprecations are announced in the changelog before the old behavior is retired.Machine-readable spec
The full OpenAPI specification is served at/openapi.yaml — the same file this reference is generated from. The docs also serve /llms.txt for AI clients.