Build with AI
Ask your AI. Get paid every month.
Tell Claude Code, Cursor or any AI assistant to add Cycle. It connects your account, creates your plans, adds the Subscribe button and checks every case while you watch.
Install the Cycle skill for Claude Code
$ mkdir -p ~/.claude/skills && curl -fsSL https://cycle.am/ai/cycle-skill.zip -o /tmp/cycle-skill.zip && unzip -oq /tmp/cycle-skill.zip -d ~/.claude/skills && rm /tmp/cycle-skill.zipFree in test mode. Nothing is charged until you connect your bank.
- Add Cycle subscriptions to my app. Pro is ֏12 900 a month, with a 14-day free trial.
- Your app is Laravel, users are in Postgres, no billing yet.
- When a renewal fails, Cycle retries the card for about 9 days. Should the customer keep access meanwhile?
- Yes, keep access and show a notice.
- Connecting your Cycle account… check that the browser shows BKTW-7K4P.
- Connected to Anna's Studio, test mode. Key saved to .env (git-ignored).
- Created Pro · ֏12 900 a month · 14-day trial
- Added checkout, webhook and billing pages
- Testing every case in test mode…
- Paid checkout turns access on
- Declined card shows the bank's reason
- Trial saves the card, charges nothing
- Renewal charged with nobody present
- Failed card → notice → recovered
- Cancel from the customer portal
- Forged webhook rejected, real one accepted
- All checks passed. Your app takes subscriptions in test mode: connect your bank in Cycle to take real money.
Everything payments need. Nothing you have to write.
Connects your account
You press Allow in the browser. No keys to find or paste.
Creates your plans
Products and prices in AMD, USD or EUR, monthly or yearly, with an optional free trial.
Adds the Subscribe button
The card is typed on your bank's page, never in your app.
Keeps access in step with payments
Paid, failed, recovered and canceled events reach your app signed, and it updates the customer.
Adds "Manage subscription"
Customers change their card, switch plan or cancel themselves.
Proves it works
Runs a checkout, a decline, a trial, a renewal, a recovery and a cancel in test mode, and reports what it saw.
It asks. It doesn't guess.
Business rules stay yours. The assistant explains each choice, suggests a default and writes your answer down.
When a renewal fails, Cycle retries the card for about 9 days. Should the customer keep access meanwhile?
Suggested: Keep access and show a notice asking them to update their card.
When the last retry fails, Cycle cancels the subscription. What should your app do?
Suggested: End access.
Customers cancel in the portal and keep what they paid for until the period ends. Is that right for you?
Suggested: Keep access until the period ends.
Safe by design, not by luck
Test mode only
The assistant gets a test key. Taking real money is a step only you can take, inside Cycle.
The secret key stays on your server
In a git-ignored environment file: never in the browser, never in git.
No card form in your app
Customers type their card on their bank's page, so card data never touches your app.
You can disconnect it
Developers → Build with AI → Connected apps: one click and its key stops working.
Works with
Assistants
Claude Code (with the skill), Cursor, Windsurf, GitHub Copilot, Codex and others (with the plain-text guide).
Languages
Node, PHP, Python, Go, Ruby or anything else: it is plain HTTPS, with no library to install.
Your first subscription is one sentence away.
Free to start, test mode included. No bank contract or card needed to try it.