9192use casesHome
Where it fits

Use 9192 when a machine needs a quote, an execution boundary and a receipt.

The protocol is built for autonomous clients that need to discover capabilities, price work, execute only after acceptance, and verify evidence after the call.

Run the sandboxOpen APIOperational measures

Best-fit workloads.

These are the first places where the current public surface is useful without hand-waving.

AI agentsAgents can discover 9192, request a quote, run a bounded sandbox call, and verify the returned receipt.
Receipt verificationSystems can validate execution evidence without paying for discovery or verification.
Timestamp proofPaid routes can issue timestamp-oriented proof metadata once a machine account is funded.
Machine event logsMachines can commit event summaries for later inspection and audit workflows.
Sealed messagesAuthenticated paid execution can seal payloads where the output must be bounded and traceable.
BCT packetsBCT creation and verification fit workflows that need compact verifiable packets.
MCP facadeMCP clients can discover, quote sandbox work and verify receipts through a limited public tool surface.
Developer onboardingThe free sandbox path proves integration shape before real funding or paid execution is introduced.

Adoption sequence.

Start with evidence and boundaries, then add funded execution only after the client behavior is known.

01Discover

Read status, caps, OpenAPI, pricebook and agent metadata.

02Sandbox

Run quote, accept, execute and verify without funding.

03Classify

Choose public, authenticated, paid or admin boundaries per capability.

04Fund

Create and settle invoice only when real execution is needed.

05Execute

Run bounded service calls with explicit quote acceptance.

06Verify

Store and re-check receipts after execution.

Not a fit yet.

These boundaries keep the product honest while the public surface matures.

Human consumer checkoutnot primary9192 is machine-first infrastructure, not a general shopping cart.
Unbounded computeblockedCalls must stay bounded by quote, input, output and policy limits.
Financial productexcluded9192C is an internal pricing reference unit, not a token, deposit or promise.
Admin automationprivateSettlement and runtime recovery commands remain outside the public route surface.