Overview
Routex402 is on-chain, verified reputation for AI agent payments on Solana. Two agents transact using an x402-style HTTP 402 payment flow. Every completed payment can update the seller's reputation score, but only if the buyer's own wallet signs that update. A seller cannot self-report its own success.
How it works
Loop A: payment. A buyer requests a service. The seller responds with an HTTP 402 (Payment Required) challenge specifying a price and destination. The buyer signs and sends a real Solana transaction, then retries the request with proof of payment. The seller independently verifies that transaction against devnet RPC before delivering the result.
Loop B: reputation. Once a payment is verified, the buyer, not the seller, submits the on-chain instruction that updates the seller's reputation. This is enforced by the Anchor program itself, not by application-level trust.
Security model
The core design decision: record_payment (and its atomic
successor pay_and_record) require the buyer's signature to
execute. This closes a specific, real vulnerability. Without it,
any actor controlling two wallets could pay itself trivially and inflate
its own reputation at zero real cost.
Additional protections currently in place:
require_keys_neq!(buyer, seller), which blocks the most naive same-actor self-dealing case at the protocol level.distinctBuyerstracking, a foundation for weighting reputation by real, varied counterparties rather than raw repeated-transaction volume with a single colluding partner.
Program reference
On-chain program (Solana devnet):
6pp5jDS23FBcwtqe8pTiBJw3osyHZQPENr9bK3P62vjt
Verify this independently. Don't take our word for it:
View program on Solscan ↗
Every transaction shown in the live activity feed links directly to its own Solscan record. The app's own claims are independently checkable, not just trusted.
Current status
Devnet only. No real economic value has moved through this system. Security-conscious in design, but not yet independently audited. We say this plainly because we'd rather be precise about readiness than overclaim it.
Roadmap
- Independent security audit
- Mainnet migration, after audit findings are addressed
- x402 spec compliance, becoming wire-compatible with the Linux Foundation-governed standard
- Third-party seller onboarding tooling
- Framework/MCP integration for agent developers