Your checkout knows what sold.
Now your agent does too.
Ask about revenue, buyers, traffic, products, or coupons without hunting through a dashboard, or have it set up a whole checkout as a draft for you to publish.
Which checkout made the most money this month, and where did its buyers come from?
The Offer Maker made $12,640 from 118 paid orders. Newsletter traffic brought $7,980, followed by partner links at $3,110. Its order bump was taken 27% of the time.
Skip the export. Ask for the answer.
The agent can read the same account numbers you see inside Swipefast.
Get the morning number
“What did I make in the last 30 days, after refunds and partner commission?”
Find what brought the sale
“Which checkout converted best, and where did those buyers come from?”
Make the campaign code
“Create a 20% launch coupon, cap it at 50 uses, and expire it on Friday.”
Build the checkout
“Set up a £97 checkout for The Offer Maker, with the £27 Email Cash Campaign Vault as an order bump.”
One endpoint. One account key.
- 1. Get your key. In Swipefast, go to Settings → Your connection key and press Copy Claude Code command. Your key is already in it.
- 2. Add Swipefast to Claude Code, once. Open Terminal, paste the command and press Enter. (Not inside Claude Code: in the normal Terminal prompt.) Using the command on the right instead? Replace
sf_live_your_key_herewith your key first. - 3. Check it’s connected. Start Claude Code by typing
claude, then type/mcp. You should see swipefast listed as connected. - 4. Just ask. “List my Swipefast checkouts”, “How much did I sell this week?”. You don’t need to type “swipefast” to start it; Claude uses it when your question needs it.
- 5. Or have it build a checkout. Type
/mcp__swipefast__setup_checkoutand say what you sell. Claude asks for the price and delivery link, then creates the checkout, order bump, upsell and sales page as a draft. You preview it and press Publish. Already have a checkout?/mcp__swipefast__design_sales_pagedesigns the page above it.
claude mcp add --scope user --transport http swipefast https://swipefast.io/api/mcp \
--header "Authorization: Bearer sf_live_your_key_here"{
"mcpServers": {
"swipefast": {
"type": "http",
"url": "https://swipefast.io/api/mcp",
"headers": {
"Authorization": "Bearer sf_live_your_key_here"
}
}
}
}Your agent gets your account. Nobody else’s.
Every request is tied to the seller behind the key. The tools cannot accept a different user ID, so a prompt cannot point them at another account.
Revenue, orders, customers, traffic, products, and coupons.
They create coupons and draft checkouts. Only you can publish; live checkouts and refunds stay in the dashboard.
Rotate it in Settings and every old agent connection stops.
Agent answers use the same reporting functions as the dashboard.
Ask Swipefast what sold while the coffee is still hot.
Your existing Swipefast plan includes the API and MCP server.
Create my checkout