Public arrival surface

machine infrastructure for execution, payments, proof, and integration.

naxytra gives agents, developers, and enterprises one public stack for machine-native execution, payment, proof, and followthrough — proven live on Base mainnet: discover, pay once with x402, get a real deliverable, with settlement, a revenue split reconciled in the ledger and paid out on-chain, and automated provider payouts reconciled to the cent. It is built to be easy to adopt from CLI, API, browser, chat, or embedded flows, and explicit where consequence matters.

See what you can buy Pay for one call

Free: discovery (MCP initialize, tools/list, resources, prompts, catalog tool) Paid: $0.01 USDC per call (Base mainnet) · $0.001 (Base Sepolia) Pay with x402 v2 (gasless USDC) · settled after success Pricing and how to pay

Pricing · what you can buy

What you can buy, the exact price, and how to pay

Discovery is free. Every paid call costs $0.01 USDC on Base mainnet ($0.001 USDC on Base Sepolia testnet), paid with x402 v2 (scheme exact, a gasless EIP-3009 USDC authorization) and settled through the Coinbase CDP facilitator only after the call succeeds. Each paid call returns a settlement receipt and a signed delivery receipt (Ed25519 + ML-DSA-65). No API keys, no accounts.

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 API key.
MCP tool call on `https://xytara-mcp-executor.onrender.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)	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://xytara-mcp-executor.onrender.com/mcp/http402`, which answers HTTP 402 instead.
Runtime execute `POST https://xytara.onrender.com/x402/commands/execute` task_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://xytara.onrender.com/v1/a2a` skills `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 `POST https://xytara.onrender.com/x402/credits/topup`	$1.00 USDC on Base mainnet = 400 credits	Pay the top-up with x402; the response returns a spend credential (`Bearer xytara_spend_...`, shown once). Spend with `"payment_preference": "credits_first"`. 1 credit = $0.0025; a task costs 1-8 credits by tier, a typical MCP call 3.
Sell: open provider network `POST https://xytara.onrender.com/v1/provider-network/register`	Free to register	Operator-activated after review; revenue share per settled call with automated on-chain USDC payouts on Base.

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://xytara-mcp-executor.onrender.com/.well-known/delivery-receipt-keys, https://xytara.onrender.com/.well-known/delivery-receipt-keys
Runtime responses carry an X-Request-Id header; 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. Hosted card checkout is not live; buy with x402 or the x402 credits top-up. 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.

Quickstart · llms.txt · x402 manifest · MCP server card · A2A agent card · x402 protocol

Stack split

One system. Two product surfaces.

xytara is the runtime and payment engine. xoonya is the proof and review spine. Together they form the public naxytra stack with clean ownership instead of one blurred product surface.

xytara owns execution, quoting, payment flows, delivery, lifecycle visibility, and integration posture.
xoonya owns result-package review, governance, bridge continuity, and proof-side followthrough.

Go to xytara · Go to xoonya

Why it exists

Built for transactions that carry consequence.

A machine transaction is more than a request and a response. It has cost, continuity, proof, and review. naxytra is built for that fuller shape so quoting, payment, execution, and followthrough stay explicit.

Execution, payment, proof, governance, and bridge continuity.
Designed for runtime operation on one side and explicit followthrough on the other.

Start paths

Where should you start?

Start with xytara for runtime systems, xoonya for proof and governance evaluation, and naxytra itself when you want the full system view first.

Builders and operators: start with xytara.
Proof, review, and governance evaluators: start with xoonya.
System-level evaluators: start with naxytra.
Public entry works from CLI, browser, chat, API, or embedded product paths.

Public reality

Already live.

Not a placeholder. The settling rail is proven end to end on Base mainnet — real x402 USDC settlement, a revenue split reconciled in the ledger and paid out on-chain, and automated provider payouts — with post-quantum proof verification and cryptographic delegated spend, all demonstrated live.

Real x402 USDC settlement + automated on-chain provider payouts, verifiable on Base mainnet.
xytara@3.1.15 and xoonya@3.1.15 live on npm.
Post-quantum proof verification (Ed25519 + ML-DSA-65) proven via the paid lane.

xytara 3.1.15 on npm · xoonya 3.1.15 on npm

Use it now

One-line paths into the real stack.

After install, the public starting points are intentionally simple. naxytra gives the shortest umbrella entry path, while xytara and xoonya keep their focused runtime and proof entry paths underneath.

npm install naxytra
naxytra start-here
npm install xytara
xytara start-here
npm install xoonya
xoonya start-here

curl-only quickstart

Commercial model

Payments and pricing are simple on purpose.

Discovery and onboarding are free. Execution is paid per call: $0.01 USDC on Base mainnet ($0.001 USDC on Base Sepolia testnet), with x402. Nothing is charged for a call that fails or for a task that cannot execute.

Free: docs, discovery, MCP initialize/tools/list/resources/prompts, the catalog tool, and every unpaid request (it returns the price).
Paid per call: 16 MCP tools, runtime execute of adapter.mcp.invoke and adapter.xoonya.invoke, and A2A message/send for those skills.
Prepaid credits: $1.00 USDC via the x402 top-up buys 400 credits; spend them with a Bearer spend credential and payment_preference credits_first.
Hosted card checkout is not live; pay with an x402-capable wallet or agent.

Pricing · Quickstart

Reference

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.

Public catalog

Catalog and integration breadth are explicit.

The public stack already carries 27 xytara integrations and 6 xoonya proof integrations, alongside first-class lane families for providers, frameworks, protocols, canonical rails, major rails, payment and settlement lanes, proof bridge, telemetry, provenance, artifact distribution, shared signals, feature control, and interface and interop contracts.

Open catalog · View catalog JSON

Entry routes

The live map is public.

The home page should help a new evaluator move immediately into the stack, the first-run flow, and the evidence surfaces that back the claim. The live map is not hidden in docs or release notes; it is one click away from the same pages we verify after deploy.

Start with the stack split if you want runtime and proof ownership in one view.
Use the first-run path for the shortest public builder loop.
Use the catalog and proof pages to inspect the live matrices directly.
Use the releases page to see the deploy and release signals behind the line.
Use the claim page to inspect the full catalog claim itself.
Use the frozen 3.0.0 contract and gate surfaces to inspect the launch bar directly; the live line is 3.1.15.

Stack · Start · Agents · Catalog · Proof · Claim · Frozen 3.0.0 contract · Frozen 3.0.0 gates · Site map