Five-minute path

Try the public loop: quote, fund or spend credits, execute, and prove.

This is the shortest public entry for a new builder. It stays secretless for first contact, keeps runtime and proof roles separate, and shows the exact path from quote to visible proof without requiring private operator context. If the account already has approved credits, the flow can continue without exposing wallet secrets.

View the path JSON Open the start guide
Step 1

Install, inspect, and choose the lane

Install the two public packages, inspect the JSON path, then decide whether you want quote-only first or credits-first execution. That keeps the runtime and proof split visible from the start.

  • npm install xytara xoonya
  • xytara start-here && xoonya start-here
  • GET /v1/first-run-path/summary
  • GET /v1/first-run-kit/summary

Path JSON · Command kit · Money-in

Step 2

Ask for a quote

Quote-only mode is the safe first contact lane. It shows the cost boundary without wallet secrets or direct payment material, so a builder can see the shape of the transaction before funding anything.

  • xytara first-run --run-quote --account ACCOUNT_REF --pretty
  • Quote-only mode is the public first-contact lane.
  • The output should stay bounded and inspectable.

Proof summary · Catalog summary · Revenue paths · Governance disputes · Money-in

Step 3

Fund or spend credits

After quote, use direct signed payment for controlled wallet tests or credits-first for repeat usage after approved funding. That keeps money-in explicit while the public surface stays easy to inspect, and it leaves the launch-day money-in boundary legible.

  • direct signed payment for controlled machine-wallet tests
  • credits-first for repeat usage after approved funding
  • xytara first-run --execute-with-credits --account ACCOUNT_REF --pretty

Revenue paths · Revenue path JSON

Step 4

Execute and prove

Run the task, then verify the result bundle in xoonya. The proof side stays separate from the runtime side, but the public loop still shows the handoff clearly and keeps the claim boundaries honest.

  • xytara first-run --execute-with-credits --account ACCOUNT_REF --pretty
  • xoonya first-run --verify-native --pretty
  • Public proof summaries stay bounded and readable.

Kit summary · Proof page

Entry points

Use the right public entry

The /try page is the quickest public entry. /start stays available as a compatibility guide, while the JSON path and command kit remain available for agents and CLI users. The page is deliberately narrow so first contact stays obvious, bounded, and reusable.

  • Try page: browser-first quick start
  • Start guide: broader public orientation
  • JSON path: machine-readable first-run summary
  • Command kit: copyable CLI boundary

Try page · Start guide · Command kit · Claim · Governance disputes · Site map

Live families

What the loop maps to

The first-run path is short, but it sits on top of the same live families the rest of the public stack exposes. That keeps the try page honest about the broader runtime, proof, and release map behind the loop.

  • Provider journeys and lifecycle continuity stay visible in the runtime layer.
  • Delivery, durability, and revenue-launch paths stay public and inspectable.
  • Proof and release summaries remain one click away from the try flow.
  • The catalog, claim, and stack pages remain the stable map for deeper browsing.

Provider journeys · Lifecycle continuity · Delivery summary · Claim · Full catalog summary · Catalog summary · Operator shell · Governance disputes · Money-in