Mastercard rePower
Developer ToolsSource Controlnone2 Endpoints
For Agents
Programmatically repowerpost2, repowerreversalpost2. Covers 2 operations.
Use for: I need to repowerpost2, I want to repowerreversalpost2, Get the current status of rePower resources, List all records from rePower
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
rePower provides programmatic access to developer tools functionality. The API exposes 2 endpoints.
Install Jentic One Beta
Connect the rePower to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the rePower, 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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmastercard.com%2Fmastercard" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmastercard.com%2Fmastercard" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 rePower API.
repowerPost2
repowerReversalPost2
Integrate rePower into automated workflows
Query and filter rePower records by parameters
Monitor rePower operational status and events
Use Cases
Patterns agents use rePower API for, with concrete tasks.
★ Developer Tools Operations
Use the rePower to perform developer tools operations programmatically. The API provides 2 endpoints covering core functionality including repowerpost2, repowerreversalpost2.
Call POST /repower/v2/repower to repowerpost2
Data Retrieval and Monitoring
Query rePower resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.
Poll the primary rePower endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call rePower 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 none tokens manually.
Search Jentic for 'repowerpost2', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
2 endpoints — repower provides programmatic access to developer tools functionality.
METHOD
PATH
DESCRIPTION
POST
/repower/v2/repower
repowerPost2
POST
/repower/v2/repowerreversal
repowerReversalPost2
POST
/repower/v2/repower
repowerPost2
POST
/repower/v2/repowerreversal
repowerReversalPost2
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring rePower by hand means integrating its two POST operations and handling the request payloads for repower and reversal yourself. Through Jentic you install once, import rePower from the API Directory, configure it once, and your agent calls it.
Permission scoping
The rePower target travels in the request body rather than the URL path, so you limit the agent to the operations it needs, such as submitting a repower request. It calls only the operations you allow, so the reversal operation is not included unless you add it.
Credential isolation
rePower's connection settings are stored once, encrypted, by your own Jentic One instance and applied at execution time. No secret enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'submit a repower request', and Jentic returns the matching rePower operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
FAQs
Specific to using rePower API through Jentic.
What authentication does the rePower use?
The rePower uses no authentication. 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 repowerpost2 with the rePower?
Yes. Use the POST /repower/v2/repower endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the rePower?
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 repowerpost2 through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'repowerpost2'. Jentic returns the matching rePower operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the rePower have?
The rePower exposes 2 endpoints covering repower transfer, repower transfer reversal operations.
Can I limit what my agent is allowed to do with the rePower API?
Yes. Because you run Jentic One yourself, your own rules decide which of the two rePower POST operations the agent may call and which credentials it may use. You can allow only the repower request submission (POST /repower/v2/repower) and withhold the reversal operation (POST /repower/v2/repowerreversal) unless you explicitly add it. Since the target travels in the request body rather than the URL path, the agent calls only the operations you permit.
GET STARTED