Rechargepayments Recharge API

Name: Recharge API
Brand: Recharge API
Availability: InStock

✓ Official Vendor SpecPaymentsPayment ProcessingapiKey112 EndpointsREST

For Agents

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

Use for: I need to addresse, I want to addresses, Search for addresse, Find all addresse

Install Jentic One Beta

Connect the Recharge API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Recharge API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Recharge API.

Create addresse

List addresses

Retrieve addresse

Update addresse

GET STARTED

Start building with Recharge API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Recharge API for, with concrete tasks.

★ 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.

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.

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.

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

Key Endpoints

112 endpoints — recharge subscription payments api.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Recharge API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'create addresse') and Jentic returns the matching Recharge API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Recharge API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Recharge API through Jentic.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.

Rechargepayments Recharge API

Connect the Recharge API to your agent

Capabilities

Start building with Recharge API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs