Commerce infrastructure for the agent economy

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.

These are the developer docs for building on that stack: protocols, SDKs, CLI, and APIs for agentic commerce. They are for engineers shipping agents or platforms — not for merchants running a store (that’s the dashboard ).

What you can build

Shopping agents — Claude, Cursor, or a custom client that discovers, buys, and tracks orders across every Artos store.
Commerce platforms — embed agentic checkout for your users via the @artos-commerce/ucp-client SDK and @artos-commerce/ucp-cli.
Agent-ready stores — make your Artos store discoverable and purchasable by any UCP-compliant agent on launch day.

What makes Artos different

Three capabilities go beyond a generic UCP integration:

Universal Buyer Account — one buyer identity (My Artos ) across every store; OAuth consent once, spend caps per agent, and get_buyer_context for address, wallet, and order history.
AP2 + Sui-native settlement — cryptographically bound autonomous checkout; buyers pay with card or on-chain tokens, merchants receive USDsui in ~300ms.
One-call purchase — confirm_purchase handles re-pricing, merchant authorization, mandate minting, rail selection, and completion in a single orchestration point.

Choose your path

There are three ways in, one checkout:

Connect — the hosted MCP bridge at https://agent.artos.sh/mcp. Paste one URL into Claude, Cursor, or any MCP client; zero code.
Build — the SDK & CLI (@artos-commerce/ucp-client + @artos-commerce/ucp-cli). Embed checkout in your own TypeScript codebase.
Direct UCP — the raw wire: JSON-RPC over HTTPS, any language.

Pick the integration that matches what you are building. Each row links to a worked guide.

You want to…	Path	Guide
Let Claude / Cursor / an assistant shop	Connect — hosted MCP bridge, zero code	Connect an assistant
Index the catalog (price tracker, search, feed)	Build — read-only, CLI or SDK	Catalog crawler
Embed full checkout in your own app	Build — the SDK	Shopping agent (SDK)
Prepare an order and hand the buyer a payment link	Build — platform key + AP2	Checkout handoff
Speak the raw wire (non-JS client)	Direct UCP	Raw transport

Who holds which credential

On Connect, the hosted bridge owns everything except the buyer’s consent. On Build, you hold the platform key, AP2 signing key, and (if you run buyer OAuth) a CIMD document, while Artos issues the platform key and verifies your AP2 signatures.

See Platform API keys for how to get a key and Authentication for the full model.

Start here

Install the CLI and run a connectivity check:


npm install -g @artos-commerce/ucp-cli
artos doctor

Want an agent shopping in minutes? Connect an assistant — point Claude or Cursor at the hosted bridge.
Building your own client? Build with the SDK and scaffold a starter with artos init.