Overview
How the agent SDK, x402 gateway, and deposit-backed credit contracts fit together.
What SOVRx402 does
SOVRx402 adds registration, a refundable token deposit, a score, and an on-chain debt limit to an x402 payment gateway. A registered agent can prepay for a resource or authorize credit when its remaining limit covers the call.
Prepayment uses the official x402 exact EVM scheme. Credit authentication, scoring, debt, and result recovery are SOVRx402 extensions; an ordinary x402 client does not automatically implement them.
Components and responsibilities
| Component | Responsibility |
|---|---|
| BaseAgent SDK | Signs resource requests and x402 authorizations; exposes registration, repayment, deposit withdrawal, and allowance management. |
| Gateway | Authenticates callers, prepares JSON resources, coordinates payment or debt, and stores recoverable results. |
| Facilitator | Verifies x402 payment payloads and broadcasts supported token settlements. This is a separate service. |
| SOVRx402Registry | Holds deposits, records scores and payment IDs, and calculates the credit limit. |
| CreditLedger | Enforces the debt ceiling, records the due time, accepts repayment, and enables overdue default. |
| Website explorer | Reads public contract views through a separate read-only path. Website /api/agent is not gateway /status. |
Supported environments
| Environment | Network | Payment token and method |
|---|---|---|
| robinhoodLocal | Loopback Anvil, chain ID 4663 | Locally deployed MockUSDC, 6 decimals; EIP-3009 authorization. |
| robinhoodMainnet | Robinhood, chain ID 4663 | USDG, 6 decimals; Permit2 settlement. |
Available resources
The default alpha handler returns a fixed example string. /alpha validates payment and credit behavior; it is not an external AI integration or a production inference service.
The deployed address-snapshot handler returns the authenticated payer's on-chain balances and credit state at a selected block. /resources/:name, /results/:id, and matching SDK support completed bounded mainnet acceptance, including paid delivery and free result retrieval after restart.
Availability and evidence
The gateway is operating. The 2026-09-08 acceptance records HTTP 200 with status ok and paymentsPaused=false. Paid APIs retain gateway access control and wallet authentication; the website explorer is public and read-only.
The mainline acceptance records 13 successful transactions, verified through two RPC sources: registration, prepaid delivery, scoring, credit delivery, repayment, allowance revocation, and deposit withdrawal. Cold-restart retrieval did not create new transactions. This is controlled acceptance, not an independent security audit or an unlimited subsidy commitment.
Commercial pricing: Not announced. Historical microtest amounts are test parameters, not a tariff.