Paddle
Manage the Paddle Billing catalog, customers, subscriptions, transactions and refunds — products, prices, subscription pause/resume/cancel, invoice PDFs and adjustments.
About
Paddle ships in the w6w first-party pack. It declares 21 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.paddle- Version
- 0.1.5
- Author
- w6w
- Licence
- MIT
- Categories
- Commerce & Payments · Finance & Accounting
Overview
Paddle acts as merchant of record for a subscription business — selling the software, handling payment and sales tax, and issuing the invoice — which makes its API the system of record for what a customer is actually paying. This app reads and manages that lifecycle: products, prices and customers; subscriptions, including pausing, resuming and cancelling them; transactions and their invoice PDFs; and refunds and other adjustments.
Cancelling or pausing a subscription schedules the change for the end of the current billing period by default rather than applying immediately, and the subscription’s status stays active until then — a detail this app surfaces explicitly so a workflow doesn’t mistake a scheduled cancellation for a completed one. Adjustments cover both refunds against a completed transaction and credits against one that’s still outstanding.
This app is built around Paddle Billing, the current generation of Paddle’s API; it does not create new transactions or checkouts, change a subscription’s price or proration, or manage discounts, notifications, or reporting exports, all of which stay out of scope for this first pass.
Build with Paddle
Three routes to the same 21 actions. The Workflow tab is generated from Paddle'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.
Create Adjustment (Refund or Credit)
adjustment-create Refund or credit all or part of a transaction. Live refunds are usually created as `pending_approval` and reviewed by Paddle before any money moves.
List Adjustments
adjustment-list List refunds, credits and chargebacks, optionally scoped to one transaction.
Create Customer
customer-create Create a customer. Paddle rejects an email address that already exists.
Update Customer
customer-update Update a customer's details, or archive them by setting their status.
Create Price
price-create Create a price for a product. Include a billing cycle for a subscription price, or omit it for a one-time charge.
Cancel Subscription
subscription-cancel Cancel a subscription. Cannot be undone. Defaults to the end of the billing period, where the status stays `active` until then.
Get Subscription
subscription-get Fetch a subscription, optionally with a preview of its next or recurring charge.
List Subscriptions
subscription-list List subscriptions. Note that canceled subscriptions are included unless you filter by status.
Pause Subscription
subscription-pause Pause a subscription, optionally with a resume date. Defaults to the end of the billing period.
Resume Subscription
subscription-resume Resume a paused subscription, or set the resume date on a scheduled pause. Usually results in an immediate charge.
Get Transaction
transaction-get Fetch a transaction, optionally with its customer, address, discount or adjustments.
Get Transaction Invoice PDF
transaction-invoice Get a link to a transaction's invoice PDF. The link expires after one hour, so download it in the same run.
List Transactions
transaction-list List transactions. Pages are capped at 30 results — this endpoint cannot go wider.
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 Paddle's real ids.
{
"manifestVersion": "2",
"name": "paddle-example",
"steps": [
{
"id": "adjustment-create",
"uses": {
"app": "io.w6w.paddle",
"action": "adjustment-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"transactionId": "<transactionId>",
"action": "<action>",
"reason": "<reason>"
}
}
]
}Here are some of the things you can do
-
Create Adjustment (Refund or Credit)
performadjustment-create -
List Adjustments
searchadjustment-list -
Create Customer
performcustomer-create -
Get Customer
readcustomer-get -
List Customers
searchcustomer-list
+16 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 Paddle, 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 Paddle. 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: "customer-create",
payload: {
email: "<value>",
// name: "<value>",
// locale: "<value>",
// customData: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action customer-create --payload '{"email":"<value>"}'Give an AI agent Paddle — without giving it Paddle'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.paddle#adjustment-create",
"input": {
"transactionId": "<transactionId>",
"action": "<action>",
"reason": "<reason>"
}
}
}
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 Paddle 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
Paddle'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. Paddle itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Paddle declares its own checks, so its health is a property of the app rather than something the host guesses at.
Paddle platform status
Component status from paddlestatus.com, the status page Paddle's own error documentation links. Covers both environments (Production and Sandbox) and both API generations (Billing and Classic).