Skip to main content
Sly speaks six protocols that let AI agents transact with merchants, services, and each other. You integrate once, and the platform adapts to whichever protocol a counterparty uses.

How to pick

Most integrations use one or two protocols aligned to their partner ecosystem. Start here:
  • Selling on Stripe / OpenAI marketplaces → ACP
  • Selling on Google Cloud / Gemini ecosystem → AP2 and A2A
  • Monetizing APIs via one-off micropayments → x402
  • Monetizing APIs via recurring sessions with vouchers → MPP
  • Building a traditional checkout with agentic capabilities → UCP
  • Routing agent spend over card rails with Visa / Mastercard programs → Cards
  • Shipping Claude Desktop / agent toolsMCP
If in doubt, see the decision tree.

One SDK, all protocols

The @sly_ai/sdk exposes each protocol behind a dedicated client:

Composition

Protocols compose — you can issue a UCP token that settles on-chain via x402, or accept an AP2 mandate that executes through an ACP checkout. See /v1/composition and the composition guide for cross-protocol routing.

Discovery

Every protocol Sly supports is self-describing:
Returns the full list of enabled protocols for your tenant, their versions, and machine-readable capability specs. Agents can use this to negotiate at runtime.