Agents transact. ArcPay settles.
ARCPAY AGENT is a concept build: a complete, honest interface for what agent-native payment infrastructure should feel like — before a single cent moves on-chain.
Payment rails were not designed for software
HUMAN RAILS ASSUME A HUMAN
Card networks, invoices and checkout flows are built around a person approving a purchase. An agent making 4,000 sub-cent calls an hour has no place in that model.
MINIMUM TICKET SIZES
Traditional fees make a $0.001 request economically impossible. Machine commerce needs pricing granularity below one cent.
NO NATIVE ACCOUNTABILITY
When software spends money, the question is not 'did it pay' but 'was it allowed to'. Policy has to live next to the wallet.
Four primitives, one loop
Isolated balances per agent, so a compromised or looping agent cannot drain the treasury.
Per-transaction, per-day and per-session limits evaluated before value moves.
Services quote a price in a machine-readable challenge. Agents compare before committing.
USDC keeps pricing legible; ARC targets the throughput profile machine traffic requires.
Where this goes
Stated plainly, with no promised dates.
INTERFACE
Agent terminal, service marketplace and simulated 402 payment lifecycle.
POLICY ENGINE
Declarative spending policies with signed operator approval and audit export.
LIVE RAILS
Wire the interface to real ARC endpoints and USDC settlement.
AGENT ECONOMY
Provider onboarding, reputation and revenue share for service operators.
- → Every number, agent and transaction in this build is demo data.
- → No token contract is deployed. APA contract status: COMING SOON.
- → ArcPay Agent is not affiliated with, endorsed by, or partnered with Circle or ARC.
- → Nothing here is financial advice or an offer of any instrument.