Skip to content
Shonin
Beta

Triage API

Send a support message, get intent, complexity, frustration, refund intent and a route.

The split

LLM writes
None
System One decides
Intent, complexity, frustration, refund
Code executes
The routing cascade

Engine

The support-triage recipe: one System One call and a deterministic cascade.

Rulebook

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

  1. R01Refunds route to a person.
  2. R02Very angry customers route to a person.
  3. R03Order status routes to code.

Endpoint

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

{
  "subject": "Duplicate charge",
  "message": "I was charged twice for order A-104. Please refund the duplicate."
}

Intake

  • subject and message text
UNIT
One message triaged
REVIEW LAYER
Automated.
DELIVERY
JSON over HTTPS.
TURNAROUND
~100–800 ms

How we find buyers

  • x402 Bazaar
  • llms.txt
  • Support Triage Desk customers

More like this

BetaAgent API

Shonin Check

Should my agent pay this? A pre-payment check of any x402 payment request: pay, confirm with a person, or block.

UNIT
One check of one payment request
PRICE
$0.01 per check
Under a second without a task; a few seconds with the intent checkOpen
BetaAgent API

Shonin Gate

Execute, confirm or escalate? An approval gate for any agent action, with one confidence bar per risk tier.

UNIT
One gate decision for one proposed action
PRICE
$0.01 per gate
A few secondsOpen
BetaAgent API

Shonin Receipt

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

UNIT
One verified receipt for one payment
PRICE
$0.01 per receipt
A few secondsOpen