Skip to content
Shonin
Beta

Shonin Receipt

Proof for every agent payment: an on-chain settlement check and a signed, normalized receipt for the books.

The split

LLM writes
Nothing
System One decides
Nothing: receipts are exact
Code executes
Chain reads, log decoding, matching and signing

Engine

Code only: it reads the transaction from the chain, decodes the stablecoin transfer and the EIP-3009 authorization, compares them with what you expected, and signs the result.

Rulebook

What correct means here, and the mistakes we've already caught. It grows one job at a time.

  1. R01Only known stablecoins count as payments; other token transfers are ignored.
  2. R02A reverted or missing transaction is reported as such, never as settled.
  3. R03Receipts are signed over sorted-key JSON, so anyone can verify them.

Endpoint

POST /api/v1/receipt  # $0.01 per call, USDC via x402

{
  "network": "eip155:42220",
  "transaction": "0xf6f71df2f84279c483b138a43c8adcfcd7c1e319459f2b1b2497cdb706a38b38"
}

Intake

  • The PAYMENT-RESPONSE header, or the network and transaction hash
  • Optional: the payee, amount and payer you expected
UNIT
One verified receipt for one payment
REVIEW LAYER
Automated: every expectation the caller sent comes back as matched or not.
DELIVERY
A JSON receipt with an explorer link, signed when a receipt key is configured.
TURNAROUND
A few seconds

How we find buyers

  • x402 Bazaar, llms.txt and the agent card
  • MCP registries
  • x402 sellers who want receipts for their buyers
  • Finance teams of companies running paying agents

More like this