canonical: https://jentic.com/apis/rechargepayments.com/rechargepayments

# Rechargepayments Recharge API

Recharge subscription payments API. The API exposes 112 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create addresse, list addresses. Covers 112 operations with apiKey authentication.

## Scope

Does not handle communications, crm, or developer tools - use for payments only.

## Capabilities

- Create addresse
- List addresses
- Retrieve addresse
- Update addresse
- Delete addresse

## Use cases

### Payments Operations

Use the Recharge API to perform payments operations programmatically. The API provides 112 endpoints covering core functionality including create addresse, list addresses, retrieve addresse.

Example prompt: Call POST /addresses to create addresse

### Automated Accounts Management

Automate accounts operations by combining multiple Recharge API endpoints. Agents can list addresses and then retrieve addresse in a single workflow.

Example prompt: Call GET /addresses to list addresses, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Recharge API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'create addresse', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/addresses` | Create addresse |
| GET | `/addresses` | List addresses |
| GET | `/addresses/{id}` | Retrieve addresse |
| PUT | `/addresses/{id}` | Update addresse |
| DELETE | `/addresses/{id}` | Delete addresse |
| POST | `/bundle_selections` | Create bundle_selection |
| GET | `/bundle_selections` | List bundle_selections |
| GET | `/bundle_selections/{id}` | Retrieve bundle_selection |

## Key resources

- **Accounts** — Operations for accounts
- **Addresses** — Operations for addresses
- **Batch_Tasks** — Operations for batch_tasks
- **Batches** — Operations for batches
- **Bundle_Selections** — Operations for bundle_selections

## Why Jentic

- **Setup:** Wiring the Recharge API by hand means learning its X-Recharge-Access-Token header auth, pointing at the rechargeapps.com host, and handling requests yourself. Through Jentic you install once, import the Recharge API from the API Directory, store the access token once, and your agent calls it.
- **Permission scoping:** Recharge puts resource ids in the URL path (for example `/addresses/{id}` and `/bundle_selections/{id}`), so a rule can pin your agent to specific addresses or bundle selections. You choose the operations it may call, so writes like updating or deleting an address are only included if you add them.
- **Credential handling:** Your Recharge access token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a customer address' or 'list bundle selections', and Jentic returns the matching Recharge operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### What authentication does the Recharge API use?

The Recharge API uses an API key passed in the `X-Recharge-Access-Token` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create addresse with the Recharge API?

Yes. Use the POST /addresses endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Recharge API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create addresse through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create addresse'. Jentic returns the matching Recharge API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Recharge API have?

The Recharge API exposes 112 endpoints covering accounts, addresses, batch_tasks operations.

### Can I limit what my agent is allowed to do with the Recharge API?

Yes. Because you run Jentic One yourself, your own rules decide which Recharge operations and credentials the agent may use. Recharge puts resource ids in the URL path, such as `/addresses/{id}` and `/bundle_selections/{id}`, so you can pin the agent to specific addresses or bundle selections. You also choose which operations it may call, so writes like updating or deleting an address (PUT and DELETE `/addresses/{id}`) are included only if you add them.