Model Context Protocol

Your checkout data,
inside your AI.

Connect Swipefast to Claude, ChatGPT, or any MCP client and ask about your sales in plain language. No dashboard, no SQL, no export. Sign in to Swipefast from the app, or paste the API key you already have.

Things you can just ask
  • “How much did I make last month, and how does that compare to the month before?”
  • “Which checkout converts best, and where is that traffic coming from?”
  • “Who are my top 10 customers and what have they spent?”
  • “Make me a 25% off code for Black Friday, capped at 100 uses.”

Connect it

The server is version 1.35.0 (see what changed) and speaks MCP 2025-06-18 over HTTP at https://swipefast.io/api/mcp. Connect by signing in (OAuth), or with your API key from Settings.

Claude, ChatGPT and other connectors

Add a custom connector with the address https://swipefast.io/api/mcp and no key. The app opens Swipefast, you sign in and press Allow, and it’s connected. In Claude it’s under Customize → Connectors; in ChatGPT it’s Plugins → Add custom MCP server (paid plans, Plus included). Setup for every app we’ve checked is on /agents. On the Allow screen you can untick building and changing checkouts to give the app read-only access. Connected apps are listed in Settings, each with its own Disconnect button.

Claude Code
claude mcp add --scope user --transport http swipefast https://swipefast.io/api/mcp \
  --header "Authorization: Bearer sf_live_your_key_here"
Cursor and other config-file clients
{
  "mcpServers": {
    "swipefast": {
      "type": "http",
      "url": "https://swipefast.io/api/mcp",
      "headers": {
        "Authorization": "Bearer sf_live_your_key_here"
      }
    }
  }
}
For client developers

OAuth 2.1 as the MCP spec describes it. An unauthenticated request gets a 401 whose WWW-Authenticate header points at /.well-known/oauth-protected-resource, which names this site as the authorization server (/.well-known/oauth-authorization-server). Clients register themselves (RFC 7591), and PKCE with S256 is required. Scopes are read and write. Access tokens last an hour; refresh tokens rotate, and reusing an old one disconnects the app. Tokens only open this endpoint, never the REST API.

To check the endpoint is reachable before wiring up a client, a plain GET returns the server card:

curl https://swipefast.io/api/mcp

What it can do

37 read-only tools and 27 that write. Every tool is scoped to your account by construction — none of them takes a user id, so there is no way to point one at somebody else’s data.

list_productsread
Every product/checkout on the seller's Swipefast account, with price, status and public URL. Start here when you need a product id or slug for another tool.
get_productread
One product plus the order bumps, upsells, price tiers and payment plans attached to it, and offerChain: the upsells buyers see after paying, in order, with where each yes and no leads (an offer id or thank_you). Accepts either the product id or its slug.
checkout_qr_coderead
A QR code for one checkout's buyer link, for a flyer, a slide or a table at an event. Pass a tag (e.g. qr, event, workshop) to add ?ref= to the link, so sales from the code show that tag in the seller's Sales and Reports. Returns the link and the code as an SVG file's text, with a quiet zone so it scans. A PNG is one click away on the checkout's page in Swipefast (editUrl). Pro only: on Starter it returns an upgrade message.
list_ordersread
Recent real orders (test orders excluded), each with how it was paid (card, PayPal, Klarna, Afterpay, Affirm, USDC and so on) and the buyer's answers to the checkout's questions, if it asks any. Use `days` to scope to a window and `productSlug` to scope to one checkout.
revenue_summaryread
Gross revenue, refunds, affiliate commission and net for a trailing window, with the previous window of the same length for comparison. This is the same maths the dashboard shows, so the numbers will always agree.
revenue_by_monthread
Revenue per calendar month, oldest first — for spotting trends and seasonality.
top_customersread
The seller's customers ranked by lifetime spend, with order counts.
list_accountsread
The accounts this person can work in: their own, and every client account whose team they're on, with their role in each. To work in a client's account, pass its id as `account` on the tool you call. Leave `account` out for their own.
account_summaryread
All-time revenue and order count, plus active subscriptions and the MRR they represent, and which extra ways to pay the seller has switched on (buy now, pay later; stablecoins on Pro). The fastest single call for "how is my business doing".
traffic_sourcesread
Revenue and orders grouped by UTM source/medium/campaign, with conversion rate. Sales with no attribution roll up as "Direct" rather than being dropped. Also visitorSources: people (not page loads) by channel (Search, Social, AI assistants like ChatGPT and Claude, Email, Paid, Referral, Direct) and by source, each with the revenue its visits brought and revenue per visitor, from visitor tracking on the seller's checkouts and tracked websites (since).
subscription_healthread
Subscriber churn, revenue churn, net revenue retention, average lifetime and expected lifetime value per subscriber, with active subscribers and MRR. The averages are monthly, over the full months in the window. Also a month-by-month series: paying subscribers on the 1st, cancellations, the MRR they took, and who ended them (the buyer's cancel link, a card that failed every retry, or other, like a refund or the seller). To answer why churn moved, compare the months and their reasons. Payment plans aren't counted here; see revenue_forecast.
revenue_forecastread
An estimate of the revenue already on the way: subscriptions that renew, their MRR shrunk each month by the revenue churn seen over the last N months, plus every payment-plan instalment still to come, on its due date. New sales, trials and failed payments aren't in it, and yearly subscriptions count as a twelfth a month. Say it's an estimate when you quote it. If a part can't be worked out, it's null and note says why.
compare_checkoutsread
Two to four checkouts side by side over the last N days (default 30): visits, orders, conversion, order bump and upsell take rates, average order, revenue and refunds. Real orders only. Use it to see which offer converts or earns more before suggesting a change to the weaker one.
affiliate_dashboard_linkread
The private link to one affiliate's own dashboard: their referral links, clicks, sales and commission (on hold, cleared to pay and paid), with no buyer details. Find the affiliate by id, code, email or name. Also says whether affiliates get an email each time they earn a commission. Anyone with the link sees that affiliate's numbers, so give it to the seller to pass on to that affiliate only. Never post it anywhere public.
list_couponsread
Every discount code on the account, with how many times each has been redeemed.
coupon_statsread
Each discount code's paid orders over the last N days: how many times it was used, the revenue from those orders, the discount it gave away and the average order. Codes nobody used are listed too. Real orders only.
create_couponwrites
Create a new discount code. Codes are stored uppercase and matched case-insensitively at checkout. Buyers can only type a code on checkouts that show a code box: this switches it on for the draft checkouts the code covers, and lists live ones still without it (codeBox.stillOff) for the seller to turn on.
get_sales_page_guideread
The rules and design brief for the HTML sales page that sits above a Swipefast checkout. Call this before writing salesPageHtml or calling set_sales_page, and follow it: it keeps the page on-brand, phone-friendly and from breaking the payment section. Pass `product` to fill the brief with that checkout's details, and `style` for a look (modern, classy, jacob, bold, minimal, playful): offer the seller the styles first if they haven't picked one.
get_brand_guideread
The seller's brand guide: colours, fonts, tone of voice, words to use and avoid, logo notes and audience, saved once on their account. Read it before you draft any copy or design a page, and follow it. Empty means they haven't written one: offer to write it with them (set_brand_guide). Never shown to buyers.
set_brand_guidewrites
Save the seller's brand guide on their account, replacing the one there (an empty string clears it). Plain text or Markdown, up to 20,000 characters. If they have a brand.md, a style guide or brand notes in their repo or files, you can import it: read it and pass it here as it is. Otherwise write it with them: colours as hex, fonts, tone of voice, words to use and avoid, logo notes, audience; never invent facts. Lines like "Primary colour: #fc176f", "Heading font: Fraunces" and "Theme: dark" set the colour, font and theme of their NEW checkouts; existing checkouts don't change. It's an account setting, never shown to buyers, so it applies straight away. Show the seller what you're saving first.
get_link_pageread
The seller's link in bio page at their store address /links: photo, name, bio, social profiles, links and the checkouts it shows, whether it's published, and whether it shows their revenue. Also lists the checkouts they could show. Read it before set_link_page.
set_link_pagewrites
Build or change the seller's link in bio page (their store address /links). Each field you pass replaces what's there; fields you leave out stay as they are. links is the whole list, in order (title and an https:// or mailto: address each, up to 20); checkouts is the whole list of checkouts to show, in order (ids or slugs from list_products, up to 12; only live ones appear). socials takes full profile addresses: instagram, tiktok, youtube, x, threads, linkedin, facebook, bluesky, substack, github, website, email (email takes an address). Never invent links or handles: ask the seller. This can't publish, unpublish or turn on the revenue display: the seller does that in Swipefast. If the page is already published, changes show straight away, so show the seller what you're saving first.
setup_checkoutwrites
Create a complete checkout in one call: the product, its delivery, the cart copy, an optional order bump, an optional one-click upsell, optional payment plans (weekly or monthly instalments), optional booking (buyers pick a call time), optional questions buyers answer before paying and an optional sales page above the cart. It is always saved as a DRAFT: nobody can buy until the seller previews it and presses Publish in the dashboard. Before calling, make sure you have the name, price, currency, one-time or subscription, and where buyers get it (a https:// link, or manual delivery). Ask the seller for anything missing; never invent a delivery link or a price. Returns the dashboard link to preview and publish.
add_order_bumpwrites
Add an order bump (a small add-on buyers tick in the cart) to one of the seller's checkouts, draft or live. On a draft this applies straight away. On a LIVE checkout nothing changes yet: it creates an approval request (status pending_approval) that the seller approves in Swipefast; tell them, give them the approvalUrl, and check later with approval_status. Never invent a price or a link.
add_upsellwrites
Add a one-click upsell buyers see after paying to one of the seller's checkouts, draft or live. On a checkout with no offer after payment yet, it's the first. Otherwise say where it goes in the chain: after (an offer id from get_product's offerChain) and when ("yes" or "no"): it's shown when the buyer answers that offer that way, and leads on to wherever that answer went before. A downsell is an offer after the upsell, when "no". Up to 5 offers in a chain, on every plan. Optionally pass html for a custom upsell page. On a draft this applies straight away. On a LIVE checkout nothing changes yet: it creates an approval request (status pending_approval) that the seller approves in Swipefast; tell them, give them the approvalUrl, and check later with approval_status. Never invent a price or a link.
set_sales_pagewrites
Put the seller's sales page HTML above the cart on one of their checkouts, draft or live, replacing any page already there. To change part of an existing page, use get_sales_page and edit_sales_page instead. Pass an empty string to remove it so the cart stands on its own. On a draft this applies straight away. On a LIVE checkout it applies straight away too (status applied; the seller can roll it back on their Approvals page), unless it touches money: a price, currency, billing, the delivery link, payment plans, an early-bird price or campaign, or a retention discount or pause. Those create an approval request instead (status pending_approval): tell the seller, give them the approvalUrl, and check later with approval_status. To change other things straight away, don't send money fields in the same call. Never invent a price or a link. The answer includes slop: { score, flags }, Swipefast's plain-rules check of the page's words (0-100, no AI): if score is 20 or more, fix the flagged phrases with edit_sales_page, keep the facts, and save again.
get_sales_pageread
The HTML of the sales page above one of the seller's checkouts, or of an upsell's own page (pass upsell). Read it before changing a page, so you change what's there instead of rewriting it from memory. To change part of it, use edit_sales_page; to replace all of it, set_sales_page. The answer includes slop: { score, flags }, Swipefast's plain-rules check of the page's words (0-100, no AI): if score is 20 or more, fix the flagged phrases with edit_sales_page, keep the facts, and save again.
edit_sales_pagewrites
Change part of the sales page above one of the seller's checkouts, or of an upsell's own page (pass upsell), without rewriting the rest. Call get_sales_page first, then pass edits: each find is text copied exactly from the current HTML (enough of it to appear only once) and replace is what goes there instead. Edits apply in order; if any find isn't there, or is there more than once without all: true, nothing changes. On a draft this applies straight away. On a LIVE checkout it applies straight away too (status applied; the seller can roll it back on their Approvals page), unless it touches money: a price, currency, billing, the delivery link, payment plans, an early-bird price or campaign, or a retention discount or pause. Those create an approval request instead (status pending_approval): tell the seller, give them the approvalUrl, and check later with approval_status. To change other things straight away, don't send money fields in the same call. Never invent a price or a link. The answer includes slop: { score, flags }, Swipefast's plain-rules check of the page's words (0-100, no AI): if score is 20 or more, fix the flagged phrases with edit_sales_page, keep the facts, and save again.
roast_sales_pageread
A sassy, specific review of the sales page above one of the seller's checkouts, from Pip, Swipefast's penguin. Returns the page's HTML, the checkout's facts, the seller's brand guide and a roast brief: follow the brief. It changes nothing: after the roast, ask the seller which fixes they want, and apply those with edit_sales_page. It also returns slop: { score, flags }, Swipefast's plain-rules check of the page's words (0-100, no AI): if score is 20 or more, make fixing the flagged phrases one of Pip's points, keep the facts, and once they're fixed save again.
check_postread
Score a LinkedIn, X, Threads or Substack post the seller is about to publish to promote a checkout, the way Post check in Swipefast does: plain rules, no AI, nothing stored. Returns a slop score (0-100, higher means more filler that reads machine-written: reframes like "it's not X, it's Y", em dashes, buzzwords, engagement bait), each flag with the exact words that set it off. The sell score (0-100: a hook up top, a clear offer, a reason to click, a link or a plain way to buy, a real result, the right length) is opt-in, because plenty of posts aren't selling anything: it comes back when you pass productId (then it also checks the post names that checkout and that any price it states is the checkout's price) or sell: true, and is null otherwise. "Link in the comments" doesn't count as a way to buy. The phrase rules read English. It's a writing check, not an AI detector: tell the seller what to change, quote the flags, and offer a rewrite only if they ask.
update_checkoutwrites
Change any part of one of the seller's checkouts, draft or live: name, description, price, currency, billing, delivery, the cart's wording, the guarantee, the button, the thank-you page, the language, early-bird pricing, a campaign (seats, opening and closing times), payment plans, booking (the times buyers can book a call at), intake questions (asked before paying) and the theme. Only the fields you pass change; the same rules as the dashboard editor apply. Call get_product first to see what's there now. It never publishes or unpublishes. On a draft this applies straight away. On a LIVE checkout it applies straight away too (status applied; the seller can roll it back on their Approvals page), unless it touches money: a price, currency, billing, the delivery link, payment plans, an early-bird price or campaign, or a retention discount or pause. Those create an approval request instead (status pending_approval): tell the seller, give them the approvalUrl, and check later with approval_status. To change other things straight away, don't send money fields in the same call. Never invent a price or a link. Tell the seller exactly what changed, using the changes list this returns.
update_order_bumpwrites
Change an order bump on one of the seller's checkouts, draft or live: headline, wording, price, delivery link, or turn it off (active: false). Get its id from get_product. On a draft this applies straight away. On a LIVE checkout it applies straight away too (status applied; the seller can roll it back on their Approvals page), unless it touches money: a price, currency, billing, the delivery link, payment plans, an early-bird price or campaign, or a retention discount or pause. Those create an approval request instead (status pending_approval): tell the seller, give them the approvalUrl, and check later with approval_status. To change other things straight away, don't send money fields in the same call. Never invent a price or a link.
update_upsellwrites
Change a one-click upsell on one of the seller's checkouts, draft or live: headline, wording, price, delivery link, its own page (html; empty removes it), or turn it off (active: false; in a chain, buyers then pass it along its no). Get its id from get_product. To change the order or the yes and no paths, use set_offer_chain. On a draft this applies straight away. On a LIVE checkout it applies straight away too (status applied; the seller can roll it back on their Approvals page), unless it touches money: a price, currency, billing, the delivery link, payment plans, an early-bird price or campaign, or a retention discount or pause. Those create an approval request instead (status pending_approval): tell the seller, give them the approvalUrl, and check later with approval_status. To change other things straight away, don't send money fields in the same call. Never invent a price or a link.
update_price_optionwrites
Change one of a checkout's price options (the levels buyers pick between, like Standard and VIP), draft or live: its name, the line under it (description), its price, or take it off the checkout (active: false). Get the option's id or name from get_product (tiers). Subscribers already on it keep the price they signed up at. On a draft this applies straight away. On a LIVE checkout it applies straight away too (status applied; the seller can roll it back on their Approvals page), unless it touches money: a price, currency, billing, the delivery link, payment plans, an early-bird price or campaign, or a retention discount or pause. Those create an approval request instead (status pending_approval): tell the seller, give them the approvalUrl, and check later with approval_status. To change other things straight away, don't send money fields in the same call. Never invent a price or a link.
remove_order_bumpwrites
Delete an order bump from one of the seller's checkouts, draft or live. To hide it but keep it, use update_order_bump with active: false. On a draft this applies straight away. On a LIVE checkout it applies straight away too (status applied; the seller can roll it back on their Approvals page), unless it touches money: a price, currency, billing, the delivery link, payment plans, an early-bird price or campaign, or a retention discount or pause. Those create an approval request instead (status pending_approval): tell the seller, give them the approvalUrl, and check later with approval_status. To change other things straight away, don't send money fields in the same call. Never invent a price or a link.
remove_upsellwrites
Delete an upsell from one of the seller's checkouts, draft or live. If it's in the chain, whatever led to it now leads on to where its own yes went (else its no). To hide it but keep it, use update_upsell with active: false. On a draft this applies straight away. On a LIVE checkout it applies straight away too (status applied; the seller can roll it back on their Approvals page), unless it touches money: a price, currency, billing, the delivery link, payment plans, an early-bird price or campaign, or a retention discount or pause. Those create an approval request instead (status pending_approval): tell the seller, give them the approvalUrl, and check later with approval_status. To change other things straight away, don't send money fields in the same call. Never invent a price or a link.
set_offer_chainwrites
Arrange the one-click upsells buyers see after paying as a chain: which offer comes first, and where each yes and each no leads, another offer or the thank-you page (thank_you). Use offer ids from get_product (upsells and offerChain); create an offer with add_upsell first. Up to 5 offers, no loops, every offer reachable from the first, on every plan; a downsell is the offer a no leads to. This replaces the chain; offers left out stay on the checkout but aren't shown. Each offer a buyer takes is charged the way their first payment allows, and only when they say yes. On a draft this applies straight away. On a LIVE checkout it applies straight away too (status applied; the seller can roll it back on their Approvals page), unless it touches money: a price, currency, billing, the delivery link, payment plans, an early-bird price or campaign, or a retention discount or pause. Those create an approval request instead (status pending_approval): tell the seller, give them the approvalUrl, and check later with approval_status. To change other things straight away, don't send money fields in the same call. Never invent a price or a link.
approval_statusread
Check what happened to a change you asked for on a live checkout: pending (the seller hasn't decided), approved (it's live; the result is included), applied (it went live straight away, no approval needed), rejected, expired (7 days passed), failed (with the error) or rolled_back. Use the request id a write tool returned. Don't ask again while it's pending.
publish_checkoutwrites
Ask the seller to publish one of their draft checkouts, so buyers can pay. This never publishes by itself: it files a request (status pending_approval) and emails the seller, who confirms it with one tap in Swipefast. A yes in this chat doesn't count as their approval, so always tell them to confirm in Swipefast. Before asking, make sure they've looked at the preview. If something would stop it going live (no store name, a missing delivery link, no payment account), you get that reason instead; tell the seller. Check later with approval_status.
list_coursesread
The seller's courses in their Hub: title, status (draft or live), how many students, and the outline, meaning each module with its id and its lessons' titles. Call this before add_lesson to find the course and module.
add_lessonwrites
Add a lesson to one of the seller's courses: a title, the lesson text and, optionally, a video link. It goes at the end of the module you name (an id from list_courses), at the end of a new module if you pass newModule, or at the end of the last module. The text is simple Markdown: # and ## headings, paragraphs, - and 1. lists, **bold**, *italic*, [links](https://...) and ![images](https://...); a video link on a line of its own plays in place. Write the lesson from what the seller gave you; never invent facts, links or results. It applies straight away, on a LIVE course too (status applied; the seller can roll it back on their Approvals page).
list_coaching_clientsread
The clients of a coaching package (a call checkout whose booking has a package): each one's email, name, how they joined (an order or added by the seller), whether their package still counts, calls booked so far, calls left (null means no limit) and their calls to come. Also the Hub address where clients book.
add_coaching_clientswrites
Add people to a coaching package by email, so they can book their calls in the seller's Hub: clients who pay the seller some other way, or not at all. Only add emails the seller gave you. With invite (default true) each new client gets an email with a link that signs them in to book. People already on the package are skipped. Up to 200 at a time.
list_findingsread
Problems the seller's performance rules flagged for you to look at, newest first: which checkout, which number (conversion, order bump or upsell take rate, refund rate), its value and the line the seller set. When the seller asks what their rules found, call this, check the checkout with offer_stats and get_product, then propose one change with update_checkout, update_order_bump or update_upsell (on a live checkout it goes to their Approvals page). Then call resolve_finding. Also returns nextSteps: Pip's one recommended change for each of the seller's busiest live checkouts (the same one their dashboard shows), with the numbers behind it. When the seller asks what to improve, start there.
resolve_findingwrites
Close a finding from list_findings once you've proposed a change for it (status done) or decided it needs none (dismissed). Say what you did in the note.
list_rulesread
The seller's performance rules: what each watches on which checkout, the line it fires at, what it does (switch an offer on or off, set a price, change wording, or flag it for you), whether it's on, and its last check.
create_rulewrites
Watch one checkout's number every day and act when it crosses a line, e.g. "if the order bump is taken by fewer than 10% of buyers over 14 days, with at least 50 orders, switch it off". metric: conversion, bump_rate, upsell_rate or refund_rate. action: offer_active (config {target: bump|upsell, offerId, active}), set_price ({target: checkout|bump|upsell, offerId?, price}), set_copy ({target, offerId?, field: name|ctaLabel for the checkout or headline for an offer, text}) or ask_ai ({}), which flags it for you in list_findings. A fixed action never changes a live checkout directly: it files a request on the seller's Approvals page, then the rule pauses. Get offer ids from get_product. Confirm the rule with the seller before creating it.
list_email_optionsread
The seller's connected email tools (Kit, Mailchimp, ActiveCampaign, beehiiv, MailerLite, Kajabi, HighLevel, MailCheap) and what a rule can add buyers to in each: tags, sequences, automations (HighLevel workflows), publications (a MailCheap newsletter) or groups, with their ids and names. Call this before add_email_rule so you use names that exist. Read-only.
list_email_rulesread
The seller's automation rules: when something happens (a sale, an order bump, an upsell, a refund, a cancelled subscription, or someone who typed their email and didn't pay within waitHours) on which checkout, and what happens (add to a tag or sequence in their email tool, send to a webhook, or email them). Optionally for one checkout.
add_email_rulewrites
When something happens on one of the seller's checkouts, add the buyer to a tag or sequence (or automation, publication or group) in their connected email tool. when: sale (someone buys the checkout), order_bump (they add the order bump in the cart), upsell (they take the one-click upsell after paying), refund, subscription_cancelled, or checkout_abandoned (they typed their email on the checkout but hadn't paid wait_hours later; runs once per person and checkout, never for anyone who bought by then, never in test mode or on the seller's free trial, and only for emails typed after the rule was made). For example "order bump buyers → sequence X, upsell buyers → sequence Y, every sale → sequence Z" is three calls. With several order bumps or upsells, pass offer to pick one (its id from get_product, or its headline). Call list_email_options first for the exact tag and sequence names. Joining a sequence can start sending the buyer emails, so confirm the plan with the seller first. Applies straight away, also on a live checkout; the seller can pause or remove it under Automations, or with remove_email_rule.
remove_email_rulewrites
Delete one of the seller's automation rules, by its id from list_email_rules. Confirm with the seller first.
offer_statsread
One checkout's numbers over the last N days (default 30): visits, checkout starts, orders, conversion, order bump and upsell take rates, average order, refunds and revenue, and afterPayment: each offer in the upsell chain (shown, taken, take rate, revenue) and the paths buyers took through it ("took offer 1 then offer 2"). Real orders only. Call this before suggesting a change to price, bump, upsell or chain, and again after a change to see if it helped.
buyer_journeyread
One buyer's whole path, oldest first: each visit (where it came from: the post, search, AI assistant or email, with its campaign or ?ref= tag), the pages they read and buttons they clicked, when they started checking out, what they paid, the order bump, and every upsell they took or turned down. Give an order id (from list_orders) or the buyer's email. Sales from before visitor tracking show the order only.
top_pagesread
The pages people read over the last N days (default 30), on the seller's checkouts and tracked websites: visitors per page and the revenue those visitors went on to spend, plus the pages visits started on (entry pages) and the goals they hit (buttons marked data-goal). Use it to say which blog post or page is worth more traffic.
funnel_statsread
A funnel over the last N days (default 30). For a checkout: people who opened it, typed their email, paid, took the order bump and took an upsell, each step with how many dropped off. Or one of the seller's own funnels by id (pages and goals on their website, counted in order per visitor). Pass product or funnel_id.
tracking_statusread
Whether visitor tracking is reporting: when it started, the last visit to the seller's Swipefast checkouts, and each tracked website with its last visit and visits this week. Websites with no visit yet need the tag installed (install_tracking gives it).
install_trackingwrites
Adds the seller's own website (their sales page, blog or link-in-bio) to visitor tracking and returns the one-line tag for its <head>, plus a prompt their coding AI can follow to install it. After that, a buyer who reads a post there and pays on Swipefast is one journey. Swipefast's own checkout pages are tracked already. Starter tracks 1 website, Pro up to 10. If the website is already tracked, returns its tag again.
set_retention_offerswrites
Choose what a subscriber is offered when they open their cancel link, before the cancel goes through: a discount (a percentage off their next few payments) and/or a pause (no charges for a few months once their paid time ends, then it starts again on its own). They take one or still cancel, and each subscriber sees it once. Subscription checkouts billed through Stripe only, not Lemon Squeezy. Only the fields you pass change: discount: null or pause: null removes that offer, and enabled: false switches them off. Passing an offer switches them on. Ask the seller for the numbers; never invent a discount. On a draft this applies straight away. On a LIVE checkout it applies straight away too (status applied; the seller can roll it back on their Approvals page), unless it touches money: a price, currency, billing, the delivery link, payment plans, an early-bird price or campaign, or a retention discount or pause. Those create an approval request instead (status pending_approval): tell the seller, give them the approvalUrl, and check later with approval_status. To change other things straight away, don't send money fields in the same call. Never invent a price or a link.
retention_offer_statsread
One subscription checkout's retention offers and their results: how many subscribers saw the offer at their cancel link, how many stayed (by discount or pause), how many cancelled anyway, the save rate, and the monthly revenue kept at full price. All time, or the last N days. Real orders only.
change_subscription_planwrites
Move one subscriber of a subscription checkout to another of its price tiers (Pro). A plan that costs the same or more starts now and charges the difference for the rest of their current period, on the card they pay with: days left / days in the period x the price difference, and nothing under 50 cents is charged. Their renewal date doesn't move. A cheaper plan starts at their next payment, with nothing refunded. cancelPendingDowngrade: true calls off a downgrade that's waiting instead. Name the subscriber by subscription id or email, and the plan by tier id or name (get_product lists the tiers). Payment plans and Lemon Squeezy subscriptions can't change. Only change a plan the seller asked for. On a LIVE checkout, or whenever it would charge real money, nothing changes yet: it creates an approval request (status pending_approval) the seller approves in Swipefast, and the amount is worked out again then; tell them and give them the approvalUrl. It never charges without the seller's approval.
affiliate_payoutsread
What the seller owes their affiliates and JV partners. For each: what's cleared to pay (past the refund hold), on hold, on its way in a PayPal payout, and paid, with their payout method and whether one-click PayPal can send it. Also the payouts already sent and how each is doing (sending, unclaimed, paid, returned), and the program's commission tiers, recurring commission and auto-pay. It changes nothing. To pay, use create_payout_run.
jv_statementread
A JV partner's revenue split for one calendar month (UTC): each payment it came from (revenue net of tax), the rate, their share, refunds taken out, and the month's totals, with their balance. Without a partner, lists every JV partner with their split, status and balance. Find the partner by id, email or name. It changes nothing.
create_payout_runwrites
Ask the seller to pay what's cleared to their affiliates and JV partners. method "paypal" sends one PayPal payout from the seller's own PayPal to everyone whose payout method is PayPal, with their PayPal email (Pro; the seller's PayPal app must have Payouts turned on). method "mark_paid" records that the seller already paid them another way, with their reference. Pass payees (ids, codes or emails) to pay only some. It never pays by itself: it always creates an approval request (status pending_approval) the seller approves in Swipefast, and on approval it pays only what had cleared when you asked, never more than the total in the request. A PayPal payment counts as paid only once PayPal confirms it. Tell the seller and give them the approvalUrl. A yes in this chat isn't their approval.
set_commission_tierswrites
Set the seller's affiliate commission tiers (Pro): rates that lift an affiliate once they reach a number of sales or an amount of revenue (net of tax) in a calendar month (UTC), like 40% after 10 sales or 50% after 5000 in revenue. A tier never lowers an affiliate's own higher rate. Pass tiers: [] to remove them. Optionally set recurring commission on subscription renewals and payment plan instalments: "first" (first payment only), "all" (every renewal), or a number of months. Optionally switch on the affiliates' leaderboard (first names only). Applies to commissions written from then on; past ones don't change. While the program has an approved affiliate, nothing changes yet: it creates an approval request (status pending_approval) the seller approves in Swipefast; tell them and give them the approvalUrl.

Worth knowing

Money comes back twice. Every amount is returned as cents and as a formatted string, because a model reading a bare 9900 will cheerfully tell you that you made ninety-nine hundred dollars.

The numbers match your dashboard. Test orders are excluded and refunds are handled the same way the dashboard handles them — the tools call the same functions the dashboard does, so the two can never disagree.

What the writing tools can do. create_coupon makes a discount code. set_brand_guide saves the seller’s brand guide, an account setting buyers never see, so it applies straight away and changes no existing checkout. setup_checkout creates a checkout as a draft, and update_checkout and the tools beside it change any checkout through the same rules as the dashboard editor. Drafts change straight away. On a live checkout, words, design, pages and switching, removing or reordering offers change straight away too and appear in Dashboard → Approvals, where the seller can roll them back. Anything that touches money (a price, a delivery link, a new offer, a plan) changes nothing: the call returns status: "pending_approval", a request id and an approval link, and the seller is emailed. Only a signed-in seller can approve, in Dashboard → Approvals; no key or tool can. A snapshot is taken before any change on a live checkout, so it can be rolled back. Requests expire after 7 days, and approval_status tells the model what happened. offer_stats gives one checkout’s visits, conversion, bump and upsell take rates, average order and refunds. Errors come back as {code, message, hint}. Nothing here can publish by itself, unpublish, refund or move money: publish_checkout only files a request, which the seller confirms in Swipefast, and a yes in the chat doesn’t count. Everything else is annotated read-only so clients can auto-approve it.

Courses go through the same door. list_courses reads the seller’s Hub courses and their outline, and add_lesson adds a lesson (a title, Markdown text and an optional video link) to a module. On a draft course it applies straight away. On a live course it applies straight away too and appears in Approvals, and rolling it back removes just that lesson.

Rules watch the numbers for you. create_rule sets a performance rule on a checkout: when its conversion, order bump or upsell take rate, or refund rate crosses a line, Swipefast either files an approval request (switch an offer, change a price or wording) or leaves a finding. list_findings reads those, so the model can look at the checkout, propose one change and mark the finding done with resolve_finding.

Set up a checkout in one go. In Claude Code, type /mcp__swipefast__setup_checkout and say what you sell. Claude asks for the price and delivery link, builds the checkout (with an order bump, upsell and sales page if you want them) as a draft, and gives you the link to preview and publish.

Pages follow the same rules as the blog prompt. Before writing a sales page, the agent calls get_sales_page_guide, the same brief as our Claude and Codex guide, so the page stays scoped, phone-friendly and points every button at the checkout. For an existing checkout, type /mcp__swipefast__design_sales_page.

From the terminal, or as an agent skill. The open-source swipefast CLI calls these same tools with your key (swipefast products, swipefast stats, swipefast call <tool>), and its agent skill teaches Claude Code and other agents the rules: never invent a price, money changes on a live checkout wait for approval, publishing is the seller’s call.

Your key is your key. It is the same one the REST API uses. Rotating it in Settings disconnects every client that uses the key. Apps you signed in to are separate: disconnect them under Connected apps.

What changed

You approve this server once, and from then on your AI trusts what its tools say they do. So the tools never change quietly: every change to what your AI can see or do gets a new version number (clients see it as serverInfo.version) and an entry here. When a change lets your AI do something it couldn’t before, we email everyone who has connected one. Don’t want it? Disconnect the app or rotate your key in Settings and it loses access at once.

1.35.010 November 2026
Countdown banners and an offer-ended message for campaigns.
  • update_checkout's campaign takes countdownBanner: a bar across the top of the checkout counting down to closesAt, with the seller's text before the time left ("" for the default "This offer ends in"). It needs closesAt. Every buyer sees the same real deadline.
  • campaign also takes endedTitle and endedMessage: what the checkout says once it has closed, instead of the default.
  • get_product's campaign shows countdownBanner, endedTitle and endedMessage.
1.34.09 November 2026
Email rules for people who start a checkout and don't pay.
  • add_email_rule takes when: checkout_abandoned, with wait_hours (1, 3, 12, 24 or 48, default 24): someone typed their email on the checkout and still hadn't paid that many hours later, so add them to a tag or sequence in the seller's email tool. It runs once per person and checkout, skips anyone who bought in the meantime, and never runs in test mode or on the free trial.
  • list_email_rules shows those rules with their waitHours.
1.33.05 November 2026
Coaching packages: clients book their own calls in the Hub.
  • setup_checkout and update_checkout take booking.package: how many calls each client gets (in total, each month, or no limit), how many they can book ahead, until when they can move or cancel, and whether buyers pick their first call at checkout. A subscription can now sell a monthly package; leaving package out keeps the one set.
  • list_coaching_clients: a package's clients, with calls booked, calls left and calls to come, plus the Hub address.
  • add_coaching_clients: add clients by email (people who pay another way, or not at all), optionally emailing each one a link to book.
1.32.04 November 2026
Intake questions: ask buyers a few things before they pay.
  • setup_checkout and update_checkout take intake: up to 5 questions buyers answer in the checkout before paying (short answer, long answer, link, checkboxes or one choice), each optional or required. On update_checkout the list replaces the questions, and null or [] removes them. Any checkout, every plan.
  • Questions change no prices, so on a live checkout they apply straight away (status applied; the seller can roll it back). get_product shows them, and list_orders shows each order's answers.
1.31.04 November 2026
Sell a call with its time: buyers pick a slot in the checkout.
  • setup_checkout and update_checkout take booking: call length, how often a call can start, a buffer, minimum notice, how far ahead people can book, the seller's time zone, their weekly hours and whether to show spots left. On update_checkout it replaces the rules and null turns booking off. One-time prices and payment plans only.
  • Booking changes no prices, so on a live checkout it applies straight away (status applied; the seller can roll it back). get_product shows the booking rules. Only for sellers who have calendar booking.
1.30.04 November 2026
Your AI builds your link in bio page: photo, bio, socials, links and the checkouts it shows.
  • get_link_page reads your link in bio page (your store address /links): what's on it, whether it's published, and the checkouts you could show.
  • set_link_page changes it: name, bio, photo, social profiles, links and which checkouts it shows, in order. Links must be https:// or mailto:. It can't publish or unpublish the page, or show your revenue on it: you switch those in Swipefast. On a published page, changes show straight away.
1.29.030 October 2026
Work in a client's account from the same connection, when you're on their team.
  • list_accounts lists your own account and every client account whose team you're on, with your role in each. It's only offered to people on more than one account.
  • For them, every tool takes an optional `account` (an id from list_accounts). Left out, the call is in your own account as before; nothing carries over from one call to the next. Your role on that team decides what the call can do, checked on every call, and live checkouts follow that account's approvals.
  • Each answer then starts with the name of the account it came from.
1.28.029 October 2026
MailCheap as an email tool: add buyers to your MailCheap newsletter or tag them from the chat.
  • list_email_options, add_email_rule and remove_email_rule work with a connected MailCheap newsletter: a rule adds the buyer to the newsletter (kind publication), or to it with one of its tags, when they buy, add an order bump or take an upsell.
1.27.028 October 2026
Fewer approvals: switching, removing and reordering offers on a live checkout apply straight away.
  • On a live checkout, update_order_bump, update_upsell and update_price_option with active (switching it on or off), remove_order_bump, remove_upsell and set_offer_chain apply straight away (status applied), listed on your Approvals page with a roll back. Rolling back a removed offer brings it back with its place in the chain.
  • set_retention_offers applies straight away when it only switches the offers on or off or changes their message; a discount or a pause still waits for your approval.
  • Still waiting for your approval: prices, currency, billing, delivery links, payment plans, early-bird prices and campaigns, a new order bump or upsell, retention discounts and pauses, plan changes, publishing and payouts.
1.26.028 October 2026
Your AI changes words, design and pages on a live checkout straight away; only money waits for your approval.
  • On a live checkout, set_sales_page, edit_sales_page, and the words and design in update_checkout, update_order_bump, update_upsell and update_price_option apply straight away (status applied). Each one is listed on your Approvals page, where you can roll it back.
  • Anything about money still waits for your approval: prices, currency, billing, delivery links, payment plans, early-bird prices and campaigns, switching an offer or price option on or off, adding, removing or reordering offers, retention offers, plan changes, publishing and affiliate payouts.
  • add_lesson puts a lesson into a live course straight away too, with a roll back.
1.25.028 October 2026
HighLevel (GoHighLevel) as an email tool: tag buyers or start a HighLevel workflow from the chat.
  • list_email_options, add_email_rule and remove_email_rule work with a connected HighLevel sub-account: a rule adds the buyer to one of its tags, or starts one of its published workflows (kind automation), when they buy, add an order bump or take an upsell.
1.24.028 October 2026
Your AI can now change a checkout's price options, like the wording under VIP.
  • New tool update_price_option changes one price option (Standard, VIP and so on): its name, the line under it, its price, or takes it off the checkout. On a live checkout it waits for your approval, like every other change, and you can roll it back. Subscribers already on an option keep the price they signed up at.
  • get_product now shows each price option's description.
1.23.228 October 2026
A new discount code now shows buyers a box to type it in.
  • create_coupon switches on the code box (Accept discount codes) on the draft checkouts the code covers, and returns codeBox: the checkouts switched on, and any live ones still without a box for you to turn on in Swipefast (Discounts lists them with a Turn on button). Live checkouts are never changed without you.
1.23.125 October 2026
"What should I improve?" now starts from Pip's next step for each checkout.
  • list_findings also returns nextSteps: the one change Pip recommends for each of your busiest live checkouts (add or rewrite a bump or upsell, fix the sales page, a payment-step drop, a phone-only problem), with the numbers behind it. Read-only; nothing else changed.
1.23.025 October 2026
Ask which post made you money: visitor tracking, buyers' journeys and funnels for your AI.
  • traffic_sources also returns visitorSources: people by channel (search, social, AI assistants, email, paid, referral, direct) and by source, with the revenue each brought and revenue per visitor.
  • New read-only tools: buyer_journey (one buyer's path from the post that found them to the upsell they took), top_pages (pages people read and what those readers spent), funnel_stats (where buyers drop off on a checkout or one of your funnels) and tracking_status (whether tracking is reporting).
  • New tool install_tracking adds your own website to visitor tracking (Starter 1, Pro up to 10) and returns the tag and a prompt your coding AI can use to install it. It changes nothing on your checkouts.
1.22.321 October 2026
Ask Pip, or "swipe fast" in two words, and your AI knows you mean Swipefast.
  • The server instructions say sellers may call Swipefast "swipe fast" or "Pip", its penguin mascot, so "ask Pip what sold this week" reaches these tools. No tool changed.
1.22.221 October 2026
Tools that replace what's already there now say so too, so your AI app can ask you first.
  • set_brand_guide, set_sales_page, edit_sales_page, update_checkout, update_order_bump, update_upsell, set_offer_chain, set_retention_offers and set_commission_tiers are annotated destructiveHint: true, since each overwrites what was there. They run, or ask for your approval, exactly as before.
1.22.121 October 2026
Tools that delete something or move money now say so, so your AI app can ask you before it runs them.
  • remove_order_bump, remove_upsell, remove_email_rule, change_subscription_plan and create_payout_run are annotated destructiveHint: true. Nothing else changed: they run, or ask for your approval, exactly as before.
1.22.020 October 2026
Post check's sell score is now opt-in, and "link in the comments" no longer counts as a way to buy.
  • check_post returns the sell score only when you pass productId or sell: true (it's null otherwise), so a story or tips post isn't marked down for not selling. The slop score always comes back.
  • A link in the post or a plain way to buy (DM me, link in my profile, book a call) passes the sell check; "link in the comments" or "in the replies" doesn't, since LinkedIn holds those posts back too.
1.21.020 October 2026
Sales pages come with a slop score, so your AI can fix the words that read like filler.
  • get_sales_page, set_sales_page, edit_sales_page and roast_sales_page now answer with slop: a 0-100 score for the page's words and up to 8 flags, each with the exact phrase. Same plain rules as Post check: no AI, nothing stored. When the score is 20 or more, your AI fixes the flagged phrases, keeps the facts, and saves again. On a live checkout the score is of the page waiting for your approval, and fixes still wait for your approval.
  • get_sales_page_guide has a "Write like a person" section built from the same rules (no reframes, buzzwords, dead openings, engagement bait or em dashes; plain words, specifics, contractions), so the page comes out clean the first time.
1.20.020 October 2026
Post check: your AI can check a launch post before you publish it.
  • check_post: your AI scores a LinkedIn, X, Threads or Substack post you're about to publish: a slop score with the exact words that read like filler, and a sell score (a hook, the offer, a reason to click, a link, a real result, the length). Name the checkout and it also checks the post mentions it and states its real price. Plain rules, no AI and nothing stored. It only reads.
1.19.016 October 2026
Upsell chains: your AI arranges the offers after payment, with a yes and a no path for each.
  • set_offer_chain: your AI sets the order of the one-click offers buyers see after paying, and where each yes and each no leads: another offer or the thank-you page. Up to 5 offers, on every plan (a downsell is the offer a no leads to). On a live checkout it waits for your approval, like any other change.
  • add_upsell can now put a new offer in the chain: after another offer, when the buyer says yes or no (a downsell is an offer after the upsell, on a no). On a checkout that already has an offer after payment it asks where, instead of adding one buyers never see.
  • get_product shows the chain (offerChain), and offer_stats shows each offer's views, takes, take rate and revenue, and the paths buyers took ("took offer 1 then offer 2").
  • Buyers are only ever charged for an offer they say yes to, the way their first payment allows: added to the same card, a fresh card payment after pay later or crypto, or a PayPal approval.
1.18.016 October 2026
The affiliate centre: balances and payouts, commission tiers, and JV partners' statements.
  • affiliate_payouts: what you owe each affiliate and JV partner (cleared to pay, on hold, on its way in a PayPal payout, and paid), how each one is paid, the payouts already sent and how they're doing, and your commission tiers and recurring commission. It only reads.
  • jv_statement: a JV partner's revenue split for a month (each payment, the rate, their share, refunds taken out), or every partner with their split and balance. It only reads.
  • create_payout_run: your AI asks you to pay what's cleared, with one PayPal payout from your own PayPal (Pro) or by recording that you paid another way. It never pays by itself: it always waits for your approval in Swipefast, and pays only what had cleared when it asked. A PayPal payment counts as paid only once PayPal confirms it.
  • set_commission_tiers: your AI sets commission tiers (a higher rate after a number of sales or an amount of revenue in a month), recurring commission on renewals, and the affiliates' leaderboard (Pro). Once your program has an approved affiliate, it waits for your approval like any other change.
1.17.016 October 2026
Team roles: an AI connected by a team member can only do what that member's role allows.
  • On an account with a team (Pro), each AI connection and API key belongs to the member who made it, and acts with their role: Owner, Admin, Editor, Support or Viewer. An Editor's AI builds and changes checkouts, coupons, courses and rules but can't change a subscriber's plan; a Support member's AI can change plans but not checkouts; a Viewer's AI only reads.
  • Your AI only sees the tools its role can use. A tool outside the role answers with a new error, insufficient_role, and the instructions now tell your AI to tell you rather than retry.
  • The role is checked on every call, so changing someone's role limits their AI straight away, and removing them disconnects it. Changes waiting on Approvals record which member asked and which member approved.
  • Nothing changes for an account without a team: its owner's AI can do everything it could before.
1.16.016 October 2026
Change a subscriber's plan with proration, and see how each order was paid.
  • change_subscription_plan: your AI moves one subscriber to another of a checkout's price tiers (Pro). An upgrade starts now and charges the difference for the rest of their period on the card they pay with; a downgrade starts at their next payment, with no refund. It can also call off a downgrade that's waiting. On a live checkout, and whenever it would charge real money, it waits for your approval: it never charges without it.
  • get_product now lists a checkout's price tiers, and for a subscription whether subscribers can change plans themselves.
  • list_orders: each order now says how the buyer paid: card, PayPal, Lemon Squeezy, or by name for buy now, pay later (Klarna, Afterpay, Affirm) and stablecoins (USDC).
  • account_summary: also says whether buy now, pay later and stablecoin payments are switched on for your checkouts. It only reads: you switch them in Integrations, Stripe.
1.15.016 October 2026
Churn and a revenue forecast, checkouts side by side, coupon results, QR codes, retention offers and affiliate dashboards.
  • subscription_health: subscriber churn, revenue churn, net revenue retention, average lifetime and lifetime value, with active subscribers and MRR, plus each month's cancellations and who ended them (the buyer, a failed card, or other). Your AI can answer why churn went up. It only reads.
  • revenue_forecast: an estimate of the revenue already on the way over the next 3, 6 and 12 months, from renewing subscriptions and payment plan instalments still to come. It says when a part can't be worked out.
  • compare_checkouts: two to four checkouts side by side over a window: visits, orders, conversion, order bump and upsell take rates, average order, revenue and refunds.
  • coupon_stats: each discount code's uses, revenue, discount given and average order over a window.
  • checkout_qr_code: your AI makes a QR code for a checkout's buyer link, as an SVG, for a flyer, a slide or an event. Give it a tag (qr, event, workshop) and sales from the code show that tag in Sales and Reports. It changes nothing. QR codes are part of Pro; on Starter your AI gets an upgrade message instead.
  • set_retention_offers: your AI sets what a subscriber is offered at their cancel link, before the cancel goes through: a percentage off their next few payments, a pause of a few months, or both, with your own message. Each subscriber sees it once. On a live checkout it waits for your approval, like any other change.
  • retention_offer_stats: how many subscribers saw the offer, how many stayed, by discount or pause, and the monthly revenue kept.
  • affiliate_dashboard_link: the private link to one affiliate's dashboard (their links, clicks, sales and commission, with no buyer details), found by id, code, email or name, and whether affiliates get an email when they earn a commission. It changes nothing.
1.14.014 October 2026
Your brand guide, and Pip's roast of your sales page.
  • get_brand_guide and set_brand_guide: your AI reads your brand guide (colours, fonts, tone of voice, words to use and avoid) before it drafts copy or a page, and can save one for you, including importing a brand.md from your files. It's an account setting buyers never see. New checkouts take their colour, font and theme from it; existing ones don't change.
  • get_sales_page_guide opens with your brand guide when you have one, and the setup and design prompts tell your AI to read it first.
  • roast_sales_page and the roast_my_page prompt: Pip reviews the page above a checkout, 5 to 8 specific points, each with its fix. It changes nothing; your AI asks which fixes you want and applies them with edit_sales_page, so a live checkout still waits for your approval.
1.13.014 October 2026
Six sales-page styles to pick from.
  • get_sales_page_guide takes a style (modern, classy, jacob, bold, minimal or playful) and lists them, so your AI can offer you a look before it designs the page.
  • Once your page is live, your AI may mention, once, that you can share it and tag @getswipefast for a reshare.
1.12.014 October 2026
Sales pages can be read and edited, not only replaced.
  • get_sales_page returns the HTML of a checkout's sales page, or of an upsell's own page, so you change what's there instead of rewriting it from memory.
  • edit_sales_page changes part of either page with find-and-replace edits, all or nothing. On a live checkout it waits for the seller's approval, like any other change.
1.11.013 October 2026
Free checkouts: a $0 product with a paid order bump or upsell.
  • setup_checkout and update_checkout take a price of 0 for a one-time checkout. Buyers get it with their name and email, no card. A paid order bump makes the order paid as usual; a paid upsell is offered after the free order and paid for on the offer screen. Subscriptions still need a price above zero.
1.10.013 October 2026
Campaigns from the chat: seats, an opening and closing time, and a cart that closes itself.
  • update_checkout takes campaign: how many seats, when the checkout opens and closes (with a time zone), and where a closed checkout sends people. Buyers see seats left and a countdown; the checkout closes on its own when it sells out or time runs out. On a live checkout it waits for the seller's approval, like any other change.
  • get_product shows the campaign: whether it's upcoming, open or closed, and the seats left.
1.9.011 October 2026
Kajabi as an email tool: tag buyers in Kajabi from the chat.
  • list_email_options, add_email_rule and remove_email_rule work with a connected Kajabi account: a rule adds the buyer to one of the seller's Kajabi tags when they buy, add an order bump or take an upsell. The tag can start a Kajabi sequence or automation.
1.8.010 October 2026
Email rules from the chat: order bump buyers to one sequence, upsell buyers to another.
  • add_email_rule: when someone buys a checkout, adds its order bump, takes its upsell, is refunded or cancels, add them to a tag or sequence (or automation, publication or group) in the seller's connected email tool. With several order bumps or upsells it can be for one. It applies straight away; the seller can pause or remove it.
  • list_email_options: the tags and sequences in each connected email tool. list_email_rules and remove_email_rule: read and remove the seller's automation rules.
1.7.010 October 2026
Payment plans, weekly or monthly, from the chat.
  • setup_checkout and update_checkout take paymentPlans: ways to pay in instalments beside paying in full, e.g. 4 weekly payments of $50. Each plan has a number of payments, the amount of each and how often (every week or every month). One-time card checkouts only. On update_checkout the list replaces the old one and [] removes them; on a live checkout it's an approval request, and rolling it back restores the old plans.
  • get_product lists the checkout's payment plans.
1.6.09 October 2026
Ask to publish a checkout; the seller confirms it in Swipefast.
  • publish_checkout: ask the seller to publish a draft checkout. It never publishes by itself: it files a request the seller confirms with one tap in Swipefast, and a yes in the chat doesn't count. Anything that would stop the checkout going live is reported first. Rolling an approved publish back makes it a draft again.
1.5.09 October 2026
Courses: read the outline and add lessons.
  • list_courses: the seller's Hub courses, each with its status, students and outline (module ids and lesson titles).
  • add_lesson: add a lesson (title, Markdown text, optional video link) to a module, a new module or the last one. On a draft course it applies straight away. On a live course it files a request on the seller's Approvals page, and rolling it back removes just that lesson.
1.4.09 October 2026
Performance rules, and findings for your AI to act on.
  • create_rule and list_rules: watch a checkout's conversion, order bump or upsell take rate, or refund rate every day, and act when it crosses a line. A fixed action (switch an offer on or off, set a price, change wording) files a request on the seller's Approvals page; it never changes a live checkout by itself.
  • list_findings and resolve_finding: rules set to "flag it for my AI" leave findings. Read them, propose one change through the edit tools, then mark them done.
1.3.08 October 2026
Checkouts in French and German.
  • update_checkout's language now takes fr (French) and de (German) as well as en and es. It sets the checkout, upsell, thank-you page, buyer emails and course Hub.
1.2.08 October 2026
Changes your AI makes to a live checkout now wait for your approval.
  • On a live checkout, update_checkout, set_sales_page and the order bump and upsell tools no longer change anything straight away. They send you an approval request (by email and in Swipefast), and nothing reaches buyers until you approve it.
  • Drafts still change straight away.
  • Every approved change can be rolled back in one click, back to exactly how the checkout was.
  • Requests you don't decide on expire after 7 days. Your AI can't approve them.
  • New approval_status tool: your AI can check whether you approved, rejected or rolled back a change.
  • New offer_stats tool: visits, conversion, order bump and upsell take rates, average order and refunds for one checkout.
  • Errors now come back with a code and a hint, so your AI knows what to do next.
1.1.04 October 2026
Your AI can now change any checkout, live ones included.
  • New update_checkout tool: change a checkout's name, price, billing, delivery, thank-you page and the rest, draft or live.
  • New update_order_bump, update_upsell, remove_order_bump and remove_upsell tools.
  • add_order_bump, add_upsell and set_sales_page now work on live checkouts, not only drafts.
  • get_product returns everything you can edit, so the AI changes what is there rather than guessing.
  • On a live checkout the AI is told to confirm any price, currency, billing or delivery change with you first, and every change comes back as a before-and-after list.
  • Still not possible: publishing, unpublishing, refunds or moving money.
1.0.05 September 2026
Ask about your sales from Claude, ChatGPT or any MCP client.
  • Read-only tools for checkouts, orders, revenue, customers and traffic.
  • create_coupon to make discount codes.
  • Added on 28 September under the same version number: setup_checkout, add_order_bump, add_upsell, set_sales_page, get_sales_page_guide and the two prompts, all limited to drafts. Changes like that now always get their own version.