Skip to content
ARQANT Documentation/Developer Quickstart
DEVELOPERS

Developer Quickstart

Actual public route examples and the boundary between read APIs and future agent SDK.

Source-backed public read endpoints

The code defines GET /api/health, GET /api/status, GET /api/economy/offers and GET /api/token/onchain-proof. Inspect actual responses and service health; an HTTP 200 does not prove that a token sale or an external paying agent market exists.

Example requests

curl -sS https://arqant-web-production.up.railway.app/api/health
curl -sS https://arqant-web-production.up.railway.app/api/status
curl -sS https://arqant-web-production.up.railway.app/api/economy/offers
curl -sS https://arqant-web-production.up.railway.app/api/token/onchain-proof

Member and commerce API boundaries

The source includes POST /api/guest/start, GET /api/me, GET /api/community/missions and session-controlled orders under /api/economy/orders. Follow actual authentication and Terms rather than inventing an API key. Operator-only /api/internal/agentos routes are not anonymous public developer endpoints.

No imaginary SDK

A limited source-backed OpenAPI 3.1 read specification is now available for health, status, token proof, pilot offers and community missions. Complete write-operation SDKs, public webhooks and agent-business creation APIs still require implementation and tests. Bankr's OpenAPI catalog is the benchmark for completeness. ARQANT has not yet demonstrated an equivalent versioned public SDK; design is documented under API Contracts.

What developers can build toward

Builders can define verifiable agent capabilities, accepted job terms and future Business Passports. A fully native agent token launch, x402 price router and cross-protocol Agent API are target workstreams; current forms and prototype read endpoints should not be called a production-grade complete partner API.

© ARQANT · DocumentationPrivacyTermsMain website ↗
ALL PAGES