Build agents that shop on Artos
Artos is commerce infrastructure for the agent economy. Every Artos store is agent-purchasable from day one over the Universal Commerce Protocol (UCP) : an AI agent can discover products across stores, build a checkout, and complete a real purchase — card or crypto — with the merchant settled in stablecoin on Sui in ~300ms.
Two things make this different from bolting an API onto a webstore:
- A Universal Buyer Account. One buyer identity (My Artos ) works across every Artos store. The buyer consents once via OAuth, authorizes an agent with spend caps, and that agent can then shop anywhere — no per-store signup, no re-entering cards or addresses.
- Sui-native settlement. Buyers can pay with on-chain tokens or card; the merchant always receives USDsui (stablecoin). Autonomous crypto checkout is authorized by a cryptographically bound AP2 mandate, so an agent can pay human-not-present within limits the buyer signed.
How a purchase flows
Two ways to integrate
Most teams should start with Path A. Choose Path B only when you are building your own commerce-grade UCP client.
| Path A — Hosted bridge | Path B — Direct UCP | |
|---|---|---|
| Who it’s for | Claude, Cursor, consumer agents | Platforms building their own MCP/REST client |
| Endpoint | https://agent.artos.sh/mcp | https://api.artos.sh/mcp + /s/:slug/mcp (or REST) |
| Tool shapes | Flat, agent-friendly ({ query }, items: [{ id, quantity }]) | Raw UCP (args wrapped under catalog/cart/checkout + meta) |
| OAuth + consent | Handled for you (CIMD client) | You implement OAuth 2.1 + PKCE |
| AP2 mandate | Minted + signed by the bridge | You mint + sign (ES256 JWS) |
| Crypto rail signing | Bridge signs the Sui PTB | You sign/submit the PTB |
| Money in catalog filters | Major units (dollars) | Minor units (integer cents) |
Get started with Path A → · Build a Direct UCP client →
The human-vs-agent split
Artos tracks human and agent commerce separately end to end. Orders, revenue, and sessions carry their buyer type, so a merchant sees agent-attributed sales distinctly from human storefront traffic — and a buyer reviews exactly what each connected agent has spent against its caps.
Actors
| Component | Host | Role |
|---|---|---|
| AI agent | Claude / Cursor | Calls MCP tools, runs OAuth, renders widgets |
| Bridge | agent.artos.sh | Hosted MCP; one platform key + AP2 signing + crypto rail |
| API / Authorization Server | api.artos.sh | UCP commerce, OAuth AS, AP2 verify, Sui settlement |
| My Artos | my.artos.sh | Buyer OAuth consent, Connected apps, Agents spend caps |
| Profile / CIMD | profile-artos.vercel.app | Agent UCP profile + OAuth client metadata |
Next: Authentication for the credential model and the full OAuth sequence.