ThriveCart
Read ThriveCart's products, transactions, customers and affiliates, and manage subscriptions, affiliates, students and webhook subscriptions.
About
ThriveCart ships in the w6w first-party pack. It declares 33 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.thrivecart- Version
- 0.1.2
- Author
- w6w
- Licence
- MIT
- Categories
- Commerce & Payments · Marketing
Overview
ThriveCart reads products, bump/upsell/downsell offers, transactions, customers and affiliates, and manages subscriptions, affiliates, Learn students and webhook subscriptions, against ThriveCart’s own external API. Products and their pricing options, along with every bump, upsell and downsell offer attached to them, can be listed and read individually, and transactions can be searched and refunded.
Subscription lifecycle actions — cancel, pause, resume — and affiliate state changes — approve, reject, favorite, set custom commissions — are all idempotent, since each sets a target to the same end state no matter how many times it runs. Creating a resource or moving money is treated differently: refunds, new affiliates, new students and new webhook subscriptions are all non-repeatable, since retrying any of them creates a duplicate or double-charges rather than converging on the same result.
A customer’s email can be updated with an explicit opt-in required before two customers’ order histories are merged, and webhook subscriptions can be registered and removed — though only against a target URL already registered in ThriveCart’s own settings first.
Build with ThriveCart
Three routes to the same 33 actions. The Workflow tab is generated from ThriveCart's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Approve Affiliate
affiliate-approve Approve an affiliate's pending application to one or more products.
Set Affiliate Custom Commissions
affiliate-custom-commissions-set Override an affiliate's commission rules for one product, or clear the override.
Register Affiliate For Product
affiliate-register Register an existing affiliate for one or more products.
Reject Affiliate
affiliate-reject Reject an affiliate's pending application to one or more products.
Search Affiliates
affiliate-search Search for affiliates by the product they're approved for, or by name/email/ID.
Update Customer Email
customer-email-update Change a customer's email address across their orders and customer-hub access.
Pause Subscription
subscription-pause Pause a customer's recurring subscription, indefinitely or until a given date.
Refund Transaction
transaction-refund Refund a specific charge, identified by order ID and item reference.
Search Transactions
transaction-search Search transaction activity: charges, rebills, refunds and cancellations.
Unsubscribe From Event
webhook-unsubscribe Remove a webhook subscription by its registered target URL.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying ThriveCart's real ids.
{
"manifestVersion": "2",
"name": "thrivecart-example",
"steps": [
{
"id": "affiliate-approve",
"uses": {
"app": "io.w6w.thrivecart",
"action": "affiliate-approve",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"affiliateId": "<affiliateId>",
"productIds": "<productIds>"
}
}
]
}Here are some of the things you can do
-
Approve Affiliate
performaffiliate-approve -
Get Account
readaccount-get -
Create Affiliate
performaffiliate-create -
Set Affiliate Custom Commissions
performaffiliate-custom-commissions-set -
Favorite Affiliate
performaffiliate-favorite
+28 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for ThriveCart, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to ThriveCart. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "affiliate-approve",
payload: {
affiliateId: "<value>",
productIds: "<value>",
// triggerEmails: "<value>",
// mode: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action affiliate-approve --payload '{"affiliateId":"<value>","productIds":"<value>"}'Give an AI agent ThriveCart — without giving it ThriveCart's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.thrivecart#affiliate-approve",
"input": {
"affiliateId": "<affiliateId>",
"productIds": "<productIds>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's ThriveCart connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
ThriveCart's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. ThriveCart itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
ThriveCart declares its own checks, so its health is a property of the app rather than something the host guesses at.
ThriveCart platform status
No machine-readable status surface: status.thrivecart.com/api/v2/summary.json returns 404, and no status page is linked from thrivecart.com or developers.thrivecart.com.
API headroom
Not exposed: ThriveCart documents no rate limit, quota endpoint, or X-RateLimit-* response headers anywhere in its published API reference.