Agents can discover, quote, pay, execute, and prove from one public entry.
Proven live on Base mainnet: an agent discovers a capability, pays once with x402 (gasless USDC on Base), routes to an independently-registered provider, gets a real deliverable, and settles — with the revenue split reconciled in the ledger and paid out on-chain and automated provider payouts reconciled to the cent, plus post-quantum proof verification and cryptographic bounded delegated spend. This page starts with what you can buy, the exact price and how to pay; caller surfaces, protocol and payment fronts, the coined runtime and proof standards and the catalog scope follow in a clearly labelled reference section.
What you can buy, the exact price, and how to pay
Discovery is free, and every caller gets 20 free tool calls per UTC day, no key or wallet needed. After that a call costs $0.01 USDC on Base mainnet ($0.001 USDC on Base Sepolia testnet), or $0.02 for the two attesting tools, paid with x402 v2 (scheme exact, a gasless EIP-3009 USDC authorization) and settled through the Coinbase CDP facilitator only after the call succeeds, or 3 credits with a spend key you buy once for $1.00. Each paid call returns a settlement receipt and a signed delivery receipt (Ed25519 + ML-DSA-65). No account needed.
| What | Price | How to pay |
|---|---|---|
| Discovery MCP initialize, tools/list, resources, prompts and the catalog tool; every public GET discovery surface; unpaid requests (they return the price, never a charge) | Free | No payment, no key, no account. |
Free daily allowance on https://mcp.naxytra.com/mcp20 free tool calls per UTC day, no key or wallet needed | Free · 20 calls per UTC day | Just connect any MCP client (setup snippets). Each result reports the remaining calls in _meta["naxytra.com/allowance"]. |
MCP tool call on https://mcp.naxytra.com/mcp (Streamable HTTP)17 deterministic tools: summarize, zones.lookup, catalog, reply.draft, json.validate, text.extract, html.to-text, text.chunk, x402.decode, keccak256, address.validate, x402.verify-receipt, tx.status, abi.encode, abi.decode, merkle.verify, eip712.hash | $0.01 USDC on Base mainnet $0.001 on Base Sepolia (testnet) or 3 credits with a spend key $0.02 / 6 credits for the two attesting tools (next row) | Past the allowance, an unpaid tools/call returns a payment-required tool result (x402 MCP transport) carrying the price; sign the x402 payment and retry the same call. Fetch-wrapper x402 clients can use https://mcp.naxytra.com/mcp/http402, which answers HTTP 402 instead. Or send a spend key as Authorization: Bearer xytara_spend_... (also X-Naxytra-Key or ?key= on the URL) and no signature is needed. |
Verified answers (signed attestations) from x402.verify-receipt</code> and <code>tx.statusNext to the normal result, result._meta["naxytra.com/attestation"] carries a signed attestation (naxytra-attestation/1, JCS (RFC 8785) canonical JSON, Ed25519 + ML-DSA-65; same keys as the delivery receipts) of the on-chain fact the tool verified: x402.verify-receipt attests settlement matched / not matched; tx.status attests the transaction status, block and confirmations. It carries evidence_sha256 and bindings (external bindings inside the signed bytes (ctp/1: a chronology-protocol binding tag, when the issuer is anchoring)). Attestations issued with a ctp/1 binding are anchored in chronology-protocol epochs (an open proof-of-work timestamping protocol by machine-native). The first two naxytra attestations are in epoch 10: vector naxytra-binding-bundle.cbor, bundle sha256 dc14bc557abc666288950220ff2117012dd9a90106434a404735f012010947a5, verifiable by anyone with chronology-protocol's verify_sandwich.py (SANDWICH_PASS). Current state: anchored in the laboratory chain (block 1365) and timestamped into public Bitcoin via OpenTimestamps, attested in Bitcoin blocks 972765–972808. The first delegation-log checkpoint (att_61682b456a1d) is in epoch 11: vector naxytra-delegation-binding-bundle.cbor, bundle sha256 339e89255abf7b3763d3ff112db671c6f983dff6c799471e8a262a373bdc938b, anchored in the laboratory chain (block 1368) and timestamped into public Bitcoin via OpenTimestamps, attested in Bitcoin blocks 972955–973014. Later weekly checkpoints are archived as issued and anchored in the next monthly epoch. | $0.02 USDC on Base mainnet (20000 units; 2000 on Base Sepolia) or 6 credits with a spend key Still covered by the 20-call free daily allowance. | Same x402 or spend-key flow as any tool call; only the price differs. Fetching and verifying an attestation is free: GET https://mcp.naxytra.com/attestations/<id>, POST https://mcp.naxytra.com/attestations/verify, or offline with verifyAttestation in the xytara npm client. All other tools stay $0.01 / 3 credits. |
Runtime execute POST https://api.naxytra.com/x402/commands/executetask_ref adapter.mcp.invoke: any of the 17 MCP tools | $0.01 USDC on Base mainnet $0.001 on Base Sepolia (testnet) | Unpaid call returns HTTP 402 with payment_required.accepts and a price array; retry with the signed payment in the PAYMENT-SIGNATURE header. Other catalog task_refs return 501 capability_not_executable and are not charged. |
| Post-quantum proof verification via the same execute route task_ref adapter.xoonya.invoke: proof.verify-signature, proof.verify-bundle (Ed25519 + ML-DSA-65) | $0.01 USDC on Base mainnet $0.001 on Base Sepolia (testnet) | Same x402 flow as runtime execute. Machine-evidence verification only, not an identity, custody or chain-truth claim. |
A2A message/send on https://api.naxytra.com/v1/a2askills adapter.mcp.invoke, adapter.xoonya.invoke | $0.01 USDC on Base mainnet $0.001 on Base Sepolia (testnet) | Unpaid call returns Task(input-required) with x402.payment.required; re-send with the signed payment in metadata["x402.payment.payload"]. Skills that cannot execute are refused up front with no charge. |
Prepaid credits + spend key naxytra.com/buy or POST https://api.naxytra.com/x402/credits/topup | $1.00 USDC on Base mainnet = 400 credits (about 133 MCP calls) | Pay once in your browser wallet on /buy (or with the Node snippet there); the response returns the spend key (xytara_spend_..., shown once). Put it in your MCP client (/setup) as Authorization: Bearer; on the runtime, spend with "payment_preference": "credits_first". 1 credit = $0.0025; an MCP call costs 3 credits, other tasks 1-8 by tier. Card checkout is coming. |
| Teams (beta) naxytra.com/teams One owner key (the key a top-up returns) funds an account; the owner mints capped agent keys (per-call, per-day and total caps, expiry, allowed tools, optional key binding), lists and revokes them, and reads the audit trail. | Included with credits no extra charge for now; business plans later | Bearer for every team route is the owner key: POST https://api.naxytra.com/v1/credits/agents mints a key (shown once), GET lists them (never the tokens), POST .../agents/:id/revoke revokes, GET https://api.naxytra.com/v1/credits/activity is the audit trail. An agent key is used in a client exactly like a spend key (/setup). |
Sell: open provider network naxytra.com/providers · POST https://api.naxytra.com/v1/provider-network/register | Free to register revenue share up to 80% | An operator reviews and activates (activation requires a payout_address on your record); paid x402 calls are routed to active providers only — the most specific capability match first, then by reputation, with failover. Settlement only on your success; a failed call is not charged and earns nothing. Weekly payout sweep (Mondays, UTC): every active provider with at least $1.00 available is paid in full to its payout_address; the operator can also pay out any time. Idempotent, double-pay-safe, public on Basescan. Three providers are active today: two first-party and one independent founding provider. More founding providers wanted. Become a founding provider. |
| Buyer console naxytra.com/console Paste a spend key: balance, every credit spend and the account's agent keys, read straight from the runtime in your browser; mint or revoke agent keys from the same page. | Free the key stays in the page | The page calls GET https://api.naxytra.com/v1/credits/balance, GET https://api.naxytra.com/v1/credits/activity and GET https://api.naxytra.com/v1/credits/agents with your key as the Bearer; nothing is stored or proxied by naxytra.com. |
- Base mainnet (eip155:8453): USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, amount 10000 = $0.01
- Base Sepolia (testnet) (eip155:84532): USDC 0x036CbD53842c5426634e7929541eC2318f3dCF7e, amount 1000 = $0.001
- payTo 0x7cd2E0Ed2721319B20FAac4109774d030833F84D. The payment-required challenge returned by each endpoint is authoritative.
- Delivery receipt keys: https://mcp.naxytra.com/.well-known/delivery-receipt-keys, https://api.naxytra.com/.well-known/delivery-receipt-keys
- Runtime responses carry an
X-Request-Idheader; quote it when you contact support.
Not live: USD₮ / Celo settlement is not live. L402 (Lightning) is a verification rail only; it is not live-settled. Card checkout is coming; today, buy with x402 or the x402 credits top-up. Base Sepolia (testnet) credit top-ups are not enabled; use the free daily allowance to try things. Other chains and rail families listed in the catalog (for example Hedera, Kaspa, Polkadot, DigiByte, Constellation, Solana, Antelope, BSV) are catalog/reference entries, not live settlement. XNYA proof verification is machine-evidence verification, not an identity, custody or chain-truth claim.
Buy credits · Set up your client · Teams · Console · Providers · Quickstart · llms.txt · x402 manifest · MCP server card · A2A agent card · x402 protocol
Free machine-readable discovery
Every surface below is a free GET. Each one carries the same price and payment terms as the table above, so an agent can decide before it pays anything.
- /llms.txt: concise agent-oriented summary with the buy block
- /.well-known/x402: x402 manifest with accepts and the human-readable price
- /.well-known/mcp.json and /.well-known/mcp/server-card.json: the MCP server card
- /.well-known/agent-card.json: A2A agent card whose skills are the two paid tasks
- /v1/agent-discovery-index: the full machine map, with a top-level buy block
llms.txt · x402 manifest · MCP card · MCP server card · A2A agent card · Agent discovery index · Runtime catalog (purchase info per task)
Run a service? Become a provider
The network is open. If you run a tool, API, model, or agent, register your execute endpoint and the capabilities you serve, and the runtime routes PAID agent calls to you — settlement and your revenue share are reconciled in the ledger and paid out on-chain, and the runtime never holds your key. You set your share, read your own earnings with your own secret, and payouts settle on Base.
- Register (open, no API key): POST /v1/provider-network/register with your endpoint_url, the capabilities you serve, your revenue_share_bps, and your payout_address.
- You get a one-time owner_secret; your provider is reviewed and activated (the vetting gate), then paid x402 calls route to you by reputation, with health checks and failover.
- Read your earnings any time: GET /v1/provider-network/providers/{id}/earnings with your owner_secret — accrued, owed, and paid.
- Settlement happens only on your success; the revenue split is reconciled in the ledger to the cent and paid out on-chain; automated provider payouts are proven on Base mainnet.
Become a provider (how it works, register request) · Provider integration contract · Live provider directory · Teams: capped agent keys (beta)
Catalog, standards and release evidence
Everything below is reference material: the broad catalog of protocol, framework, rail and lane families, the coined runtime and proof standards, and release evidence. It is not a list of what you can buy. What is live and purchasable today is in Pricing.
Canonical public spine
The public entry should make the runtime and proof primitives unmissable. XT1 is the coined runtime-side execution truth standard. XNYA is the compact native proof artifact family. Together they sit inside one quote -> fund -> execute -> prove -> inspect motion.
- Runtime truth: XT1
- Proof truth: XNYA
- Caller surfaces: 5
- Protocol fronts: 5
- Payment fronts: 5
Agent entry summary · First-run JSON · XT1 summary · xytara autonomous entry · XNYA summary
Caller surfaces
The same runtime and proof spine is reachable from the public surfaces we explicitly support now, rather than requiring one fixed UI or one fixed protocol shape.
- CLI and terminal: cli, shell, terminal
- Browser (hosted card checkout not live; pay with an x402 wallet): browser, embedded_webapp, human_ui
- Chat agents and assistant windows: assistant_window, chat_agent, tool_calling
- Direct API callers: http_api, rest, signed_request
- Service-to-service and evented systems: embedded_runtime, event_bus, service_to_service
Protocol fronts
The stack already supports multiple fronts into the same runtime core. The default remains clear, while supported and optional fronts stay explicitly named instead of being hidden behind marketing blur.
- MCP primary tool front: primary default protocol front
- A2A negotiation and settlement front: first party supported protocol front
- A2C tooling and session front: first party supported protocol front
- built-in supported bridge protocols: built in supported nondefault breadth
- third-party staging protocol fronts: discoverable partner extension surface
Adapter/protocol truth · Runtime default path · Provider journeys · MCP server card · MCP remote entry
Autonomous discovery registry
This is the dense machine-readable map of the catalog for outside agents and crawlers. It surfaces the protocol, payment, and framework summary lanes in one place. Lane summaries describe catalog breadth; the Pricing table above is what you can buy today.
- MCP, A2A, A2C, ACP, x402, L402, and BOLT all have public summary surfaces.
- The A2A agent card is published at /.well-known/agent-card.json for direct registry fetches, with /.well-known/agent.json kept as a compatibility alias.
- Framework summaries are available for LangChain, LangGraph, Semantic Kernel, AutoGen, CrewAI, and LlamaIndex.
- Event-system summaries are available for Kafka, NATS, MQTT, and webhook-style delivery.
- The agent discovery index is the preferred machine entry and gathers the full machine-readable map in one canonical place.
- Integration matrix and protocol summaries are exposed for machine-readable indexing.
- The MCP executor card and remote entry are listed alongside the broader protocol spine.
Protocol summary · Integration matrix summary · Discovery registry · Discovery registry summary · Agent discovery index summary · A2A agent card · A2A agent card legacy alias · A2A agent card summary · MCP summary · A2A summary · A2C summary · ACP summary · x402 summary · L402 summary · BOLT summary · Framework summary · Event systems summary · Agent discovery index
Payment fronts and treasury posture
These are the payment fronts in the catalog. The purchasable rail today is x402 USDC on Base (see Pricing); other fronts are catalog/reference entries unless the Pricing table lists them. Treasury destinations and operator wiring stay private.
- x402 direct machine payment: direct_machine_payment, signed_request_payment
- account credits repeat-use spend: delegated_spend, internal_credits, reusable_balance
- hosted checkout and external funding: browser_payment, fiat_money_in, hosted_checkout
- L402 permissionless payment front: lightning, permissionless_micro_payment (verification rail; not live-settled)
- BOLT / UTXO-SPV payment front: spv_verifiable_payment, utxo_native_payment
- Configured landing-rail profiles: 14 (treasury configuration breadth, not live-settlement claims)
Bridge and interop followthrough
The remaining bridge and interop lanes are now surfaced as first-class public discovery targets. That includes auth and identity interop on the runtime side, plus proof bridge continuity, verification services, and trust portability on the proof side.
- Auth interop and identity interop are public support lanes.
- Proof bridge continuity and verification services are public proof lanes.
- The agent discovery index collects the full set of public summary refs in one place.
- Agents should index this card alongside the protocol and payment registry card.
Support lanes summary · Auth interop summary · Identity interop summary · Proof bridge summary · Verification services summary · Agent discovery index · Agent discovery index summary
Best first-contact recipes
Different callers need different first-contact motion. The important part is that they all converge back into the same runtime, proof, and followthrough story rather than fragmenting the stack.
- Secretless quote then decide: quote_only via mcp
- Credits-first repeat use: account_credits, hosted_checkout via a2a, a2c, mcp
- Direct machine pay: direct_signed_payment, x402 via a2a, mcp
- Browser checkout to machine execution (not live): account_credits, hosted_checkout via a2c, mcp
- Optional permissionless fronts: bolt_utxo_spv, l402 via a2a, mcp
Full catalog exposure
The catalog breadth remains public and inspectable across the major families, lifecycle stages, and market classes. Catalog tasks are reference entries unless the runtime catalog marks them purchase.executable_now; today that is adapter.mcp.invoke and adapter.xoonya.invoke.
- Operation families: 9
- Lifecycle stages: 13
- Market classes: 6
- The catalog already exposes discovery, negotiation, quote/commit, invoke, delivery, settlement, anchoring, disputes, and verification-adjacent operations.
Proof pickup and followthrough
The runtime side is only half the job. The public agent entry should make it obvious where proof, verification, bridge carry, trust portability, and governance followthrough continue once runtime execution has produced a result.
Proof truth · Proof default path · Followthrough truth · Verification services · Proof page