Skip to main content
The fastest way to a working integration is one of four onboarding wizards in the dashboard at app.getsly.ai/dashboard/onboarding. Each is purpose-built around a use case — you pick the closest match, the wizard sets up the right primitives, and you’re testing in minutes.

API Monetization

~10 min · Monetize your APIs with pay-per-call pricing using x402. Perfect for SaaS companies, AI APIs, and data providers who want agents to pay per request.

E-Commerce

~12 min · Accept customer payments via hosted checkout using UCP. For online stores, marketplaces, and anywhere human buyers complete purchases.

Agent Commerce

~15 min · Let AI agents buy things on behalf of users using ACP. For shopping assistants, procurement bots, and autonomous task runners.

Recurring Payments

~12 min · Set up subscription and mandate-based payments using AP2. For SaaS subscriptions, retainers, and any pre-authorized recurring flow.

​
How the wizards work

Every template is a sequence of steps. Each step:
  • Explains what it does in plain language
  • Saves progress automatically — close the tab and come back; you’ll resume where you left off
  • Can be skipped where safe (skippable steps are marked; Sly warns you about the consequences)
  • Calls the same APIs documented here — you’re not locked into the UI
When a wizard completes, you have working credentials, a funded test wallet, and a verified end-to-end test. You’re ready to ship.

​
Picking the right template

→ API Monetization Uses x402 (HTTP 402 Payment Required). Agents call your endpoint, you respond 402 with a price, they pay, retry with proof, get the response. No sign-up flow for consumers — they just start paying.
→ E-Commerce Uses UCP (Unified Commerce Protocol) with hosted checkout. Cart → checkout URL → customer pays → settlement. Works with cards, stablecoin, bank rails.
→ Agent Commerce Uses ACP (Agentic Commerce Protocol). Your agent discovers merchants, opens checkouts, completes payment — all under spending policies you control. Includes kill-switch + approval workflows.
→ Recurring Payments Uses AP2 mandates. Issue a mandate defining what an agent can spend and when; the agent executes within those bounds. Revocable anytime.
Pick the closest match and run that wizard first. Then run additional wizards — each adds the primitives it needs without disrupting what’s already set up. Many tenants end up with multiple templates enabled.
All four protocols are exposed via the API and SDKs directly. See the quickstart for the raw API path, or reach out on support — we’re probably building for your case.

​
What every wizard sets up

Regardless of template, by the end you’ll have:
  • A tenant (your organization) — already done at signup
  • At least one account (person or business that holds funds)
  • At least one wallet (with test funds in sandbox)
  • Protocol-specific primitives (endpoints, checkouts, agents, mandates — per template)
  • A test run confirming the flow works end-to-end
  • API credentials + sample code to carry over to your backend

​
Starting over

Mid-wizard you can:
  • Pause — your progress is saved, close the tab anytime
  • Switch templates — restart from the template picker; progress on the current one is preserved
  • Reset — clear progress and start fresh (dashboard → Onboarding → ⋯ menu)
After completion you can run additional templates whenever your use case expands.

​
Skip the wizard?

If you’d rather code directly, the 5-minute quickstart does the same setup in a handful of cURL commands. The wizards are just an ergonomic wrapper over the same API endpoints.