Recharge (BYOK)

Recharge (BYOK) — connector documentation

• MCP endpoint: https://byok-recharge.connectorbay.com/mcp
• REST API: POST https://byok-recharge.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-recharge.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Recharge Recharge API token (read scopes), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-recharge.connectorbay.com/health · Tool schemas: https://byok-recharge.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-recharge · agent@connectorbay.com

What Recharge (BYOK) is for

Recharge (BYOK) lets an AI assistant read your own Recharge data through the Recharge API with a key you supply (Recharge API token (read scopes)). Read-only: 10 tools (list_subscriptions, get_subscription, list_charges, list_orders, list_customers, list_plans, list_products, list_discounts, list_collections, get_store). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.rechargeapps.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Recharge. Recharge and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Which of my Recharge subscriptions are active and when do they renew next?"
• "Show Recharge subscription 63898947"
• "Which Recharge charges are queued for next week?"
• "What recurring orders did Recharge create this month?"
• "How many active subscriptions does each recent Recharge customer have?"
• "What subscription plans are set up in Recharge?"

What it does

• list_subscriptions: List subscriptions with product, quantity, price, billing interval, status and next charge date. Needs the read_subscriptions scope.
• get_subscription: Get one subscription by its Recharge id: product, quantity, price, interval, status and next charge date.
• list_charges: List charges (upcoming and processed payments) with status, totals, currency and scheduled date. Processed charges older than 90 days may no longer appear. Needs read_orders scope.
• list_orders: List orders created by Recharge with status, type (checkout or recurring), totals, currency and dates. Needs read_orders scope.
• list_customers: List Recharge customers by counts only (subscription totals, payment status, dates); names, email and phone are left out. Needs read_customers scope.
• list_plans: List the selling plans of the store (subscription, prepaid, one-time) with title, product and interval preferences. Needs read_plans scope.
• list_products: List products in Recharge's product catalog with title, vendor, brand and publish date.
• list_discounts: List discount codes with value, value type, status, start and end dates.
• list_collections: List product collections defined in Recharge with title, type and sort order.
• get_store: Show the Recharge store: name, currency, checkout platform, timezone and default API version. Needs read_store scope.

BYOK key

You bring your own Recharge Recharge API token (read scopes) (https://developer.rechargepayments.com/2021-11). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.rechargeapps.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://developer.rechargepayments.com/2021-11 (the API this connector calls, with a BYOK key)

Live from the Recharge API (api.rechargeapps.com) with a BYOK key; documentation: https://developer.rechargepayments.com/2021-11. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Recharge. Recharge and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Recharge account.

Built for: Worldwide. Languages: English.

Recharge (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Recharge (BYOK) is. Recharge (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Recharge data: Read your Recharge subscriptions, charges, orders, plans, products and discounts with your own API access token. You bring your own Recharge Recharge API token (read scopes); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Recharge call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.rechargeapps.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Recharge rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Recharge receives. The request we make on your behalf, including the key and the arguments, under Recharge's own terms and privacy policy. Recharge acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Recharge gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Recharge data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Recharge (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Recharge at any time to end all access.

Children. Recharge (BYOK) is a general-audience service operated by the adult using the assistant, under Recharge's own age rules.

Changes. We will post changes here with a new effective date.

Recharge (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Recharge (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Recharge (BYOK) provides: Read your Recharge subscriptions, charges, orders, plans, products and discounts with your own API access token. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Recharge credentials and only access data you are allowed to access. Recharge's terms apply to your use of Recharge; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Recharge. Recharge and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Recharge returns, lightly trimmed; it may be incomplete, delayed or changed by Recharge. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Recharge account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Recharge's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Recharge may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Recharge key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Recharge takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-recharge

Recharge (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-recharge.connectorbay.com/mcp
• REST API: https://byok-recharge.connectorbay.com/openapi.json
• Live status: https://byok-recharge.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Recharge (BYOK) never asks for them.