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. It is built to be easy to adopt from CLI, API, browser, chat, or embedded flows, and explicit where consequence matters.

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.

The repos are public. The npm packages are live. The current release line is already out. This is an arrival surface for a stack that exists now rather than a placeholder for later.

  • xytara@2.5.0 live on npm.
  • xoonya@2.5.0 live on npm.
  • GitHub releases and public docs are already available.

xytara 2.5.0 · xoonya 2.5.0

Use it now

One-line paths into the real stack.

After install, the public starting points are intentionally simple. xytara and xoonya each expose one-line CLI entry paths, while their service contracts surface the deeper runtime and proof lanes underneath.

  • npm install xytara
  • xytara start-here
  • npm install xoonya
  • xoonya start-here
Public catalog

Catalog and integration breadth are explicit.

The public stack already carries 25 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

Commercial model

Payments and pricing are simple on purpose.

The public model is designed to reduce adoption friction without giving away the value layer. Discovery and onboarding stay easy. Execution and consequence stay paid. Pricing stays quote-based so the same stack can serve both lightweight usage and high-consequence work.

  • Free: docs, discovery, auth, install, evaluation, and low-friction first contact.
  • Paid: execution, funded workflows, repeated automation, and high-consequence operations.
  • Payment options: direct machine pay, hosted checkout, or reusable credits depending on the caller path.
  • Pricing posture: quote first, then pay or spend credits, then execute and receive proof-aware outputs.