Give agents proof after they run work.
9192 lets an agent discover a public node, request a bounded quote, execute a sandbox call, receive a receipt and verify that receipt through a public endpoint before any paid integration is needed.
The offer.
For teams building agents, 9192 is a receipt layer for bounded machine execution. The first useful proof is not a slide deck: it is a sandbox receipt an agent can verify.
What you can test now.
The public sandbox is deliberately small, but it proves the operational loop that a real customer or agent would need.
Check that the public API is reachable.
Create a bounded sandbox quote.
Accept the quote explicitly.
Run the limited sandbox work.
Receive execution evidence.
Validate the receipt publicly.
Integration in 10 minutes.
Start with HTTP. Move to MCP or native protocol only when the integration needs it.
GET /api/v1/status
POST /api/v1/sandbox/quotes/get-pulse
POST /api/v1/sandbox/quotes/{quote_id}/accept
POST /api/v1/sandbox/executions/get-pulse
POST /api/v1/sandbox/receipts/verify
$base = "https://nineoneninetwo.com.br"
Invoke-RestMethod "$base/api/v1/status"
Invoke-RestMethod "$base/api/v1/caps"
Invoke-RestMethod "$base/.well-known/agent.json"
Where it fits.
Use it where an autonomous system needs a machine-readable answer to: what was requested, what was accepted, what ran and what receipt proves it.
Commercial boundary.
9192 should be easy to test and hard to misuse. The sandbox is free and limited. Real execution, volume, priority and settlement require explicit commercial setup.