SohoPay is a credit rail for AI agents. A person (the borrower) holds a revolving facility. An agent they authorize spends that credit at merchants over x402. Merchants are paid in USDC on Base from a batched on-chain settlement. SohoPay never holds the borrower’s wallet key or the agent’s workload key.
Staging is the supported integration environment (Base Sepolia). Hosts and contracts are in Environment setup.

Quickstart

Connect an agent over MCP, or accept your first x402 payment as a merchant.

Integration paths

Agent, merchant, or both — pick the surface you actually call.

Pay with an agent

From HTTP 402 to a signed voucher and a confirmed settlement.

Accept a payment

Verify, capture, and poll until the batch is confirmed.

​
How a payment moves

SohoPay system architecture showing the borrower, agent, hosted MCP, control plane, merchant, facilitator, and Base settlement contracts SohoPay system architecture showing the borrower, agent, hosted MCP, control plane, merchant, facilitator, and Base settlement contracts

​
What this is not

Agents do not get a custodial wallet, and you do not co-sign payments with a threshold scheme. The ERC-4626 vault is lender liquidity behind settlement. It is not a balance you deposit in order to give an agent a credit limit. Credit is a facility on the borrower, drawn down when a batch settles and restored when the borrower repays.

​
Next steps

Quickstart

Start on staging.

Authentication

OAuth for agents, API keys for merchants.