/v1: every route, the
credential it takes, its parameters, validation rules, response fields, and the errors it returns.
The hub is the orchestration service in front of the Open Intents Framework aggregator and the
solver engines. A client asks it for a quote (it runs one round across the configured
providers, vets the answers through its own firewall and discloses the winner), then submits an
order against that quote, then follows the order through three status views.
It is an exposure layer: it lets a frontend or an integrator’s backend start flows and see order state.
It is not what makes the system safe — the contracts, the engines and the attestation committee
are — so a hub-side check is defence in depth for the paths the hub serves.
Base URL.
https://proxy-api.infinimesh.net/v1: the public test hub, which runs on test
networks only (Testing). Every example in this reference
uses it, for example https://proxy-api.infinimesh.net/v1/catalog; your production address comes
with your integration access. The API is served by the hub’s gateway, which checks your credential
and passes the hub’s answers back unchanged.The API’s machine contract is the gateway’s OpenAPI document
(Get OpenAPI document): the routes under
/v1, the two credentials
and the EPX codes, with the hub’s bodies, which the gateway passes through unchanged. This
reference describes the hub’s contract version 2026-09-23.Credentials
Every call carries one credential header: your secret API key (x-api-key) from a server, or your
public project id (x-project-id) from a web page. There is no sign-in and no session. A key opens
every route below; a project id opens every route but GET /orders, the order history. The seven
routes that read X-Infinity-Subject require it: the user of yours, or the page’s visitor, a call
is for (Authentication — your users). See
Authentication, and
API keys and rate limits.
Discovery
GET /catalog— the deployment’s declared chains and assetsGET /openapi.yaml— the API’s contract, as raw YAML
Quotes
POST /quote— run one quote round and disclose the winnerPOST /quote/preview— indicative offers for browsingPOST /quote/prepare— prepare one chosen provider under a stable id
Orders
POST /order/openfor— submit a gasless order, or register a proxy-lane orderPOST /order— register acceptance of an open-flow winner
Status
GET /order/{orderId}/status— the aggregator-backed projection (openFor)GET /status/{orderId}— the hub’s own event-derived lifecycleGET /orders— every openFor submission of your organization, or of one of your users
On-chain views
GET /onchain/{orderId}/fill— observed fill factsGET /onchain/tx/{chainDomain}/{txHash}/order— resolve a transaction hashGET /onchain/{orderId}/order— the escrow’s raw order tuple (EVM refunds)GET /onchain/{orderId}/refund— a Solana order’s refund, as an unsigned transaction
Environments
Partners test against the public test hub,https://proxy-api.infinimesh.net, which runs on test
networks only: see Testing.
c8ntinuum Testnet is reachable as the chain
eip155-8888 on whichever hub deployment declares it.
More
- Quickstart — a gasless order in five calls and one signature
- Conventions — base URL, headers, the response envelope and its statuses, timeouts, value formats, id namespaces, unknown fields
- Flows — the sequences at a glance; the explanations are under Concepts
- Errors — the full
EIN/EPX/EMCcatalogue - Limits — rate limits, timeouts and other operational behaviour
- Concepts — step execution, trade types, input validation, handling errors, rate limits, execution errors, refunds, order lifecycle
- Troubleshooting — symptom → cause → fix, by phase
- SDK:
@c8ntinuum/infinity-interop-sdkcovers every partner route with exact types, and runs the flows end to end
/v1):
The hub’s operator routes are not part of the partner API.