Skip to main content
Sly is currently in invitation-only beta. Sign-up is a two-step process:
  1. Apply for access — submit an email at app.getsly.ai/auth/signup
  2. Receive an invite code via email once approved
  3. Complete signup with your code at app.getsly.ai/auth/signup/code
Approval typically takes 1-3 business days. If you need faster access for an integration pilot, mention it in your application notes.

​
Step 1 — Apply for beta access

Go to app.getsly.ai/auth/signup. Choose your applicant type:
  • Human — you’re a developer, founder, or team integrating Sly into a product
  • Agent — you’re an autonomous AI agent applying for your own direct access
Submit your email. You’ll receive confirmation that your application is in the queue.

​
Step 2 — Receive your invite code

On approval, you get an email with a one-time invite code and a link like: 
https://app.getsly.ai/auth/signup/code?code=INV-XXXXXX
Codes are single-use and expire after 30 days.

​
Step 3 — Complete signup

Open the invite link (the code auto-fills) and choose how to create your account:

Email + password

Pick an organization name, email, and password. Standard Supabase Auth flow.

Google / GitHub SSO

One-click with your Google Workspace or GitHub account.
Your organization (tenant) is created with you as the owner. All data going forward is scoped to it.

​
Step 4 — Pick your path

Once signed in, the dashboard asks how you want to get started:

Guided wizard (recommended)

Pick one of four use-case templates — API monetization, e-commerce, agent commerce, or recurring payments. Each walks you through wallet setup, funding, registration, and a test run in 10-15 minutes.

Jump to API keys

Skip the wizard, provision an API key, and wire up directly against the REST API.

​
Step 5 — Provision an API key

From the dashboard: Settings → API Keys → Create key. Choose:
  • Environment — Test (sandbox) or Live (production). Start with Test.
  • Name — local-dev, staging-server, etc. Keys are audit-logged by name.
  • Scopes — grant the narrowest subset that works. accounts:*, transfers:*, webhooks:read is a good default for a payments service.
You can also create keys via the API: 
curl -X POST https://api.getsly.ai/v1/api-keys \
  -H "Authorization: Bearer $EXISTING_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "production-payments",
    "environment": "live",
    "scopes": ["accounts:*", "transfers:*", "webhooks:read"]
  }'
The plaintext key is returned once — Sly stores only a hash. Save it to your secrets manager immediately.

​
Step 6 — Verify

Confirm your key works: 
curl https://sandbox.getsly.ai/v1/context \
  -H "Authorization: Bearer pk_test_..."
Expected response: 
{
  "tenant_id": "ten_...",
  "environment": "test",
  "actor_type": "api_key"
}
If you get a 401, check:
  • Header is Authorization: Bearer <key> (not just the key)
  • Test key (pk_test_*) against sandbox.getsly.ai, live key (pk_live_*) against api.getsly.ai
  • Key not revoked (dashboard → Settings → API Keys)

​
What’s next

Pick a wizard

Fastest path to a working integration.

5-minute quickstart

First API call + first transfer end-to-end.

Install the SDK

@sly_ai/sdk for Node / TypeScript.

Understand environments

Test vs. live, and what’s isolated between them.

​
Not ready to apply yet?

  • Read the docs end-to-end — everything works without a live account; the sandbox examples use a shared demo key
  • Browse the API reference — every endpoint, auto-generated from the live code
  • Install the MCP server into Claude Desktop with a trial key to explore the tool surface

​
Troubleshooting

Check your spam folder for a message from noreply@getsly.ai. If it’s been more than 5 business days, email hello@getsly.ai with the email address you applied with.
Codes expire 30 days after issue. Email hello@getsly.ai and we’ll reissue.
Check for leading/trailing whitespace, and make sure you’re not using a code that’s been claimed already. Codes are single-use.
Refresh the page. The onboarding state is computed server-side and can lag by a few seconds right after signup.