Recharge MCP integration for AI agents.
Connect AI agents to Recharge through 10 structured actions, including get customer, get charge, and get order. Review authentication, inputs, workflows, and…
- ACTION CONTRACTS
- 10
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Recharge integration exposes
The Recharge Agent App exposes 10 provider-backed actions for finance and marketing work. Its current contract lets an authorized agent retrieve one recharge customer by id, retrieve one recharge charge by id, and retrieve one recharge order by id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Recharge account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Recharge capabilities.
Showing 10 of 10 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_customerREADRetrieve one Recharge customer by ID.
INPUTS: id / include
get_chargeHIGH IMPACTRetrieve one Recharge charge by ID.
INPUTS: id / include
get_orderREADRetrieve one Recharge order by ID.
INPUTS: id / include
get_productREADRetrieve one Recharge product by ID.
INPUTS: id / include
get_subscriptionREADRetrieve one Recharge subscription by ID.
INPUTS: id / include
list_chargesREADList Recharge charges with cursor pagination and common filters.
INPUTS: limit / cursor / include / ids / sortBy
list_customersREADList Recharge customers with cursor pagination and common filters.
INPUTS: limit / cursor / include / ids / sortBy
list_ordersREADList Recharge orders with cursor pagination and common filters.
INPUTS: limit / cursor / include / ids / sortBy
list_productsREADList Recharge products with cursor pagination and common filters.
INPUTS: limit / cursor / include / ids / sortBy
list_subscriptionsREADList Recharge subscriptions with cursor pagination and common filters.
INPUTS: limit / cursor / include / ids / sortBy
INPUT CONTRACTS
Know what the action needs before it runs.
get_customer
idREQUIRED- The Recharge resource ID.
includeOPTIONAL- Related Recharge resources to include, joined as a comma-separated include query parameter.
get_charge
idREQUIRED- The Recharge resource ID.
includeOPTIONAL- Related Recharge resources to include, joined as a comma-separated include query parameter.
get_order
idREQUIRED- The Recharge resource ID.
includeOPTIONAL- Related Recharge resources to include, joined as a comma-separated include query parameter.
get_product
idREQUIRED- The Recharge resource ID.
includeOPTIONAL- Related Recharge resources to include, joined as a comma-separated include query parameter.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Customer
Retrieve one Recharge customer by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_customerControl Get Charge
Retrieve one Recharge charge by ID. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
get_chargeVerify with Get Order
Retrieve one Recharge order by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_orderSAFETY BOUNDARY
Operate Recharge with explicit limits
- Authorize Recharge with API key and grant only the provider access required by the selected actions.
- 1 action is change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `get_charge` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Recharge rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Recharge task completed successfully.
CONNECTION MODEL
API key
Recharge API token used with the X-Recharge-Access-Token header. Create it in the Recharge merchant portal under Tools & apps > API tokens: https://docs.getrecharge.com/docs/recharge-api-key.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 9
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Recharge.