Runtime and machine-commerce infrastructure.
xytara is where machine execution, pricing, payment flows, delivery, and runtime consequence are operated. It is the runtime side of the stack for systems that need payment, control, and consequence to stay explicit.
What xytara owns
xytara is the runtime side of the stack. It owns execution, quote policy, payment flows, delivery visibility, runtime capability registry, and the integration posture needed to put machine work into production.
- Execution without quoting and payment is too thin.
- Execution without lifecycle visibility is too thin.
- Execution without trust and consequence continuity is too thin.
Public runtime surfaces
Live and purchasable today: x402 pay-per-call execution ($0.01 USDC on Base mainnet ($0.001 USDC on Base Sepolia testnet), or $0.02 for the two attesting tools) of adapter.mcp.invoke and adapter.xoonya.invoke, A2A message/send for those skills, the x402 credits top-up, and the open provider network with on-chain payouts.
- POST https://api.naxytra.com/x402/commands/execute (x402) and credits_first spend with a Bearer spend credential
- Catalog surfaces (pricing, trust, capability, participation, integration matrix) are reference material
Adapters, protocols, and catalog operations
xytara's public runtime face now carries 27 integrations, 13 protocol families, and explicit catalog operations for discovery, review, promotion, and registry inspection.
- Works with MCP and agent clients such as: claude mcp, openai codex (client compatibility profiles, not partnerships)
- Framework compatibility profiles: autogen, langchain, langgraph, semantic kernel, crewai, llamaindex
- Protocols: a2a, a2c, acp, grpc, kafka, mcp, mqtt, nats, ros2, webhook_event_bus
- Canonical rails: evm, base, usdc (live: x402 USDC on Base); bsv_teranode (catalog/reference only, not live settlement)
- Major rails family: antelope, constellation_dag, digibyte_dgb, hedera_hbar, kaspa_kas, metal, polkadot_dot, proton_xpr_and_metal, solana (catalog/reference only, not live settlement)
- Interface and interop contracts: openapi, asyncapi, cloudevents, auth_interop, identity_interop
Launch families
The launch story is stronger when people can see the first-run, delivery, revenue, and continuity lanes as explicit family paths instead of one blurred runtime promise. xytara already surfaces those paths as public JSON and commandable summaries.
- Provider runtime journeys stay inspectable for first-contact and followthrough.
- Lifecycle continuity stays explicit from discover through verify.
- Revenue launch paths keep money-in, paid execution, and reversal posture visible.
- Delivery and durability paths stay separate from release marketing.
Provider journeys · Lifecycle continuity · Revenue launch paths · Delivery summary
Builder start path
Install the xytara client (the runtime itself is hosted; the package is the client), run the one-line start path, quote a task without a wallet, then pay per call with x402 or spend prepaid credits from CLI, API, browser, chat, or any environment that can issue commands or HTTP calls.
- npm install xytara
- xytara start-here
- xytara first-run --offline --json
- xytara-run --help
- Supports x402 pay-per-call and prepaid credits from the x402 top-up; hosted card checkout is not live.
How xytara charges
Public pricing should feel predictable before commitment and flexible after adoption. xytara therefore keeps auth, discovery, and onboarding friction low, then charges at the point where execution, automation, or economic consequence begins.
- Auth, docs, and first-contact discovery should not be the paywall.
- Quotes come before payment so integrators can inspect cost before execution.
- Callers pay per call with x402 ($0.01 USDC on Base mainnet ($0.001 USDC on Base Sepolia testnet), or $0.02 for the two attesting tools) or spend prepaid credits bought with the x402 top-up ($1.00 = 400 credits); hosted card checkout is not live.
- Quote-based pricing keeps simple usage affordable while leaving room to price higher-value work correctly.
Where runtime sits in the stack
xytara is the runtime side of the system, but it is most useful when it stays visibly connected to the rest of the public map. This page links runtime back to the stack split, the first-run path, the catalog, and the release line so the product surface stays easy to navigate.
- The stack page explains the runtime/proof split.
- The try and start pages show the builder loop.
- The catalog page shows the runtime matrices (reference).
- The releases page shows the deploy and release signals.
- The claim page shows the full catalog claim.