Become a Paddle partner
Join the Paddle partner program to read this content. You'll also get access to our partner API and agent tooling. Let us know a few details about your business to get started. Already a partner? Log in to view this page.
Building a partner integration is optimized for AI-assisted development. Paddle publishes agent skills, plugins, and MCP servers so your coding agent can scaffold and operate a Paddle integration with you.
There are two families of agent skills, one for each layer of an embedded billing integration:
- Partner skills: the platform layer
For the one-time integration you build against the partner API: onboarding, verification, go-live, and metrics. - Public skills: the agent layer
For the seller integration your agent scaffolds inside each seller's app: catalog, checkout, webhooks, and subscriptions.
We evaluate LLMs based on their ability to generate working Paddle integration code from simple, real-world prompts. See our LLM benchmark for the latest results.
Agent skills for the platform layer
These skills cover building an integration between your platform and Paddle, working with our partner API. They help you build workflows to create and configure sellers, verify sellers, register domains, set up payouts, and surface metrics.
Grab them, then point your AI agent at them while you build your platform integration. Start with integrate-partner-platform for the end-to-end roadmap, and partner-api-basics for the auth and environment model.
Available skills
Don't publish these skills publicly. They're only for use by Paddle partners. They're separate from the skills we make available to Paddle users.
| Skill | What it covers |
|---|---|
access-paddle-dashboard | Drop a seller into the Paddle dashboard without a password — mint a magic session with the `user_api_key` (`POST /magic-sessions/authorize`) and redirect to `/magic-sessions/login` with a target (overview, payout_settings, retain_settings, onboarding). |
author-agent-skills | Turn Paddle's public builder skills into your platform's own agent skills — wrap Paddle access behind your helpers/gateway, centralize environment handling, use the seller's credentials, and provision from webhooks — so your agent builds seller integrations consistently. |
configure-seller-account | Configure a seller's account settings with the seller `api_key` — the default payment link (`PATCH /settings/account`), tax mode, brand color, saved payment methods, the bank statement descriptor, and enabling payment methods. |
create-seller-account | Create a Paddle seller account for a user on your platform via the partner API — eligibility screening, `POST /accounts/validate`, `POST /accounts`, and storing the returned `id`, `user.id`, `api_key`, and `user_api_key` in both sandbox and live. |
draft-seller-policies | Draft the three legal pages a seller needs to sell through Paddle — terms and conditions, a refund policy (14–90 day window), and a privacy notice — meeting Paddle's minimum requirements, including the Merchant of Record disclosure, so domain review passes. |
fetch-seller-metrics | Build a seller dashboard from the partner API with the seller `api_key` — revenue and MRR metrics as timeseries, transactions (`include=customer`), adjustments and refunds, and the products your integration created (filtered by `external_id`). |
integrate-partner-platform | The start-here roadmap for building an embedded-billing partner platform — the order to onboard, verify, and take sellers live, which skill owns each step, and the async approval gates (verification, domain review) to start early. Read this first. |
partner-api-basics | Partner API foundations — authentication (the `psk_` partner key + `Paddle-PartnerID` header vs. per-seller `api_key` and `user_api_key`), the sandbox and live base URLs, conventions, and error handling. Read before calling any partner endpoint. |
register-checkout-domain | Register the domain a seller's checkout is served from so Paddle opens live checkout on it — host the Apple Pay association file, `POST /checkout-domains`, poll to `approved` (resubmit if rejected), verify Apple Pay, and set the live default payment link. |
set-up-payouts | Get a seller paid — send them to the Paddle dashboard via a magic link to add bank or Payoneer payout details, and optionally poll `GET /payout-accounts/{currency}` for status (`draft` → `submitted_for_review` → `active`). |
verify-seller | Run a seller through Paddle's KYB/KYC verification with the `@paddle/partner-embeds` SDK and partner API — mint a magic-session token, open the embed, poll `automated_review`, handle next steps, and take the seller live when it completes. |
Install partner skills
The fastest way to install them is the Skills CLI, which fetches every skill into your agent's skills directory:
pnpm dlx skills add https://developer.paddle.com/embedded-billing-partner-skillsyarn dlx skills add https://developer.paddle.com/embedded-billing-partner-skillsnpx skills add https://developer.paddle.com/embedded-billing-partner-skillsThese skills aren't listed in the public skills directory, but they're installable from the URL above. Agents that support the agent skills discovery RFC can discover them from the index at:
https://developer.paddle.com/embedded-billing-partner-skills/.well-known/agent-skills/index.jsonTo install a single skill manually, fetch its SKILL.md into your agent's skills directory:
mkdir -p .agents/skills/create-seller-accountcurl -fsSL https://developer.paddle.com/embedded-billing-partner-skills/.well-known/skills/create-seller-account/SKILL.md \ -o .agents/skills/create-seller-account/SKILL.mdTo install all skills manually at once, run:
for slug in integrate-partner-platform partner-api-basics create-seller-account \ configure-seller-account verify-seller register-checkout-domain \ set-up-payouts access-paddle-dashboard fetch-seller-metrics \ draft-seller-policies author-agent-skills; do mkdir -p .agents/skills/$slug # if not created curl -fsSL https://developer.paddle.com/embedded-billing-partner-skills/.well-known/skills/$slug/SKILL.md \ -o .agents/skills/$slug/SKILL.mddoneYour agent loads a skill on demand when its description matches the task you're working on.
Build seller integrations with agent skills
The integration your agent builds inside each seller's app is essentially a standard Paddle integration. Building an integration is largely a matter of authoring skills for your agent so that it can consistently scaffold a working Paddle integration for every seller.
You can use our public agent skills as a starting point, but you'll need to fork them to include specifics about how your platform interacts with Paddle. For example, it's not likely that you'll call the Paddle API directly, but use a proxy or helper function to do so.
The author-agent-skills skill in our partner skills walks through how to wrap our public agent skills around your platform's helper functions, proxies, and business logic, so your agent builds against your backend the same way for every seller.
Available skills
| Skill | What it covers |
|---|---|
paddle-billing-history | Render the authenticated user's billing history in Next.js — listing transactions via the Paddle Node SDK, the mandatory customer-id filter, pagination via `.next()`/`.hasMore`, status filtering, and formatting raw transaction totals (lowest-unit conversion + Intl.NumberFormat, with the zero-decimal currency special case for JPY/KRW/CLP). |
paddle-catalog-setup | Create the Paddle products and prices that other Paddle skills depend on — try MCP tools first, fall back to a Node SDK seed script, or dictate dashboard steps as a last resort. |
paddle-checkout-web | Add a Paddle Checkout to a Next.js web app — overlay or inline, with event handling, customer pre-fill, and dynamic line item updates. |
paddle-customer-portal | Mint a Paddle customer portal session URL from a Next.js Server Action — the portal-vs-custom-billing-screen trade-off, auth, ownership, URL structure (overview vs deep links), and the security model. |
paddle-pricing-pages | Render country-localized prices on a Next.js pricing page using Paddle.js PricePreview — country detection, billing frequency toggle, and currency formatting. |
paddle-sandbox-testing | Test a Paddle integration end-to-end using the sandbox environment, test cards, the webhook simulator, and local tunnels — without taking real money. |
paddle-subscription-cancel | Cancel a Paddle subscription from a Next.js Server Action — auth, ownership check, safe `effectiveFrom` default, revalidation, and the `canceled` vs `scheduledChange` distinction. |
paddle-subscription-sync | Mirror Paddle subscription and customer state into your database via webhooks — schema, upsert pattern, status semantics, scheduled changes, and access gating. |
paddle-subscription-update | Change a Paddle subscription's plan from a Next.js Server Action — auth, ownership check, `prorationBillingMode`, items-array replace semantics, preview-before-commit, and `on_payment_failure` handling. |
paddle-webhooks | Receive and verify Paddle webhooks in a Next.js Route Handler — signature verification, idempotency, retry semantics, and local testing. |
Install agent skills
To learn how to install agent skills, see the agent skills documentation.
Agent plugins
If you use an agentic coding tool, we recommend using the Paddle plugin. Plugins bundle the builder skills with the Paddle MCP server and the docs MCP server.
We also have standalone MCP servers for the public API and Paddle docs, if you don't use plugins.