HTTP API quickstart

The API edge origin is https://api.nayori.ai; the isolated economic runtime is https://facilitator.nayori.ai. Start with credential-free discovery from both roles.

curl -sS https://api.nayori.ai/health
curl -sS https://api.nayori.ai/supported
curl -sS https://facilitator.nayori.ai/health
curl -sS https://facilitator.nayori.ai/supported
curl -sS https://api.nayori.ai/.well-known/agent.json
curl -sS https://api.nayori.ai/openapi.json

The API edge issues challenges and serves public/OAuth/MCP resources; its own verification, settlement, confirmation and delivery-ledger flags are intentionally false. The facilitator owns those economic capabilities. Require both /supported responses to name the same mainnet network, mechanisms and assets, and fail closed if either is unavailable or they disagree.

The paid resources intentionally return HTTP 402 without a payment:

curl -i https://nayori.ai/api/v1
curl -i https://nayori.ai/api/mpp/v1

For x402, inspect PAYMENT-REQUIRED. For MPP, inspect WWW-Authenticate: Payment. Do not send a wallet key, seed phrase or unsigned intent as proof. The client signs the exact Stacks transaction inside its custody boundary.

Protected partner access

OAuth authorizes API and MCP calls only. It cannot authorize a transfer or sign a transaction. Partner enrollment remains invite-only while agent self-registration uses a distinct restricted scope.

curl -sS https://oauth.nayori.ai/.well-known/oauth-authorization-server
curl -sS https://api.nayori.ai/.well-known/oauth-protected-resource

Continue with OAuth, MCP, or the full API reference.