Install Jentic One Beta

Connect the Rapyd Payments Platform API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Rapyd Payments Platform 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Frapyd.net%2Frapyd" | sh

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%2Frapyd.net%2Frapyd" | 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 Rapyd Payments Platform API.

Create a payment with amount and currency, optionally against a customer, payment_method, or ewallet

Cancel a payment while its status is ACT and the payment method is cancelable

Refund a payment in full or in part with a reason and merchant_reference_id

Generate a hosted checkout page for a country and currency with complete and error redirect URLs

GET STARTED

Start building with Rapyd Payments Platform API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Rapyd Payments Platform API for, with concrete tasks.

★ Agent-issued refunds through Jentic

A support agent handling a complaint can resolve it with a refund instead of a ticket hand-off. Through Jentic the agent searches for 'refund a payment', receives the Rapyd createRefund operation with its input schema, and sends the payment id with an amount and reason, while Jentic signs the request with the access_key, salt, timestamp, and signature headers at execution time. The agent can list recent refunds afterwards to confirm it went through.

Look up the payment with GET /v1/payments/{paymentId}, then call POST /v1/refunds with payment set to that id, amount 20, currency 'USD', and reason 'damaged item'

Hosted checkout for cross-border sales

Merchants selling into many countries want local payment methods without building a payment form for each. Rapyd's POST /v1/checkout creates a hosted checkout page from a required country and currency, with an amount, cart_items, payment_method_types_include to narrow the methods offered, and complete_payment_url and error_payment_url for redirects.

Create a checkout page with POST /v1/checkout using amount 49.99, currency 'EUR', country 'DE', and complete_payment_url and error_payment_url set to the shop's pages

Marketplace e-wallets

Marketplaces and platforms often hold funds for sellers before payout. Rapyd e-wallets are created with first_name, last_name, and type, can sit under a parent_ewallet, and are listed by currency or min_balance with page_number and page_size, while payments can be directed into one or more ewallets.

Create an e-wallet with POST /v1/ewallets for first_name 'Ana', last_name 'Silva', and type 'person', then list wallets with GET /v1/ewallets filtered by currency 'USD'

Payment reporting

Finance teams reconcile payments by date range and customer. Rapyd's GET /v1/payments filters by created_after, created_before, customer, ewallet, group, and invoice, and GET /v1/refunds pages refunds with limit, starting_after, and ending_before.

List payments with GET /v1/payments using created_after and created_before for last week, then list refunds with GET /v1/refunds and match them to the payments

Key Endpoints

12 endpoints — jentic publishes the only available openapi specification for rapyd payments platform api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v1/payments

Create a payment

GET

/v1/payments

List payments

DELETE

/v1/payments/{paymentId}

Cancel a payment

POST

/v1/refunds

Create a refund

POST

/v1/checkout

Create a checkout page

POST

/v1/customers

Create a customer

POST

/v1/ewallets

Create an e-wallet

POST

/v1/payments

Create a payment

GET

/v1/payments

List payments

DELETE

/v1/payments/{paymentId}

Cancel a payment

POST

/v1/refunds

Create a refund

POST

/v1/checkout

Create a checkout page

POST

/v1/customers

Create a customer

POST

/v1/ewallets

Create an e-wallet

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Rapyd by hand means computing a request signature from your access_key, secret_key, a random salt, a timestamp, the HTTP method, URL path, and body, then sending the access_key, salt, timestamp, and signature headers with an idempotency header on writes. Through Jentic you install once, import Rapyd from the API Directory, store the keys once, and your agent calls it.

Permission scoping

Rapyd puts payment and wallet ids in the URL path for reads and cancels, but carries the target payment for a refund inside the request body, so rules bound which operations your agent may call. Limit it to the operations it needs, such as payment and refund reads, so createPayment, cancelPayment, and createRefund are not included unless you add them.

Credential isolation

Your Rapyd access_key and secret_key are stored once, encrypted, by your own Jentic One instance and used to sign each request at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'refund a payment' or 'create a checkout page', and Jentic returns the matching Rapyd operation with its input schema so the agent calls the right endpoint without reading the reference.

FAQs

Specific to using Rapyd Payments Platform API through Jentic.

Why is there no official OpenAPI spec for Rapyd Payments Platform API?

Rapyd does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Rapyd Payments Platform API via structured tooling. It is validated against the live API and kept up to date. To run it on your own infrastructure, install Jentic One from its GitHub repo.

What authentication does the Rapyd Payments Platform API use?

Per its OpenAPI spec, Rapyd uses a request signature scheme: each request carries access_key, salt, timestamp, and signature headers, where the signature is calculated from the access_key, secret_key, salt, timestamp, HTTP method, URL path, and request body. Through Jentic the keys are stored by your own instance and the signed headers are built at call time, so the secret_key never enters the agent's context.

Can I cancel a Rapyd payment through the API?

Yes. DELETE /v1/payments/{paymentId} cancels a payment, but only while its status is ACT and the payment method has is_cancelable set to true. For a completed payment, use POST /v1/refunds instead.

What are the rate limits for the Rapyd Payments Platform API?

The OpenAPI spec does not specify rate limits. Check the Rapyd documentation at https://docs.rapyd.net for current limits, and test against https://sandboxapi.rapyd.net first.

Is there a Rapyd MCP server?

You don't need an MCP server to give your agent Rapyd. Jentic connects it directly from the API Directory: import it, store your access_key and secret_key once, and your agent calls the payment, refund, and checkout operations it needs, discovered on demand.

Can I limit what my agent is allowed to do with the Rapyd Payments Platform API?

Yes. For example, write a rule that allows only GET /v1/payments, GET /v1/payments/{paymentId}, and GET /v1/refunds, so the agent can report on payments and refunds but cannot create payments, cancel them, or issue refunds, and its calls are logged.

Rapyd Payments Platform API

AI ReadinessAI-Aware (B)64/100

See full scorecard

Agent-ready OpenAPI document · curated by JenticPaymentsPayment ProcessingapiKey12 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Create and cancel Rapyd payments, issue refunds, generate hosted checkout pages, and create customers and e-wallets on the Rapyd platform.

Use for: Create a hosted checkout page for 49.99 EUR in Germany, Refund 20 USD on a Rapyd payment, List all payments created this week, Cancel a pending payment before it completes

Not supported: Does not handle accounting, tax calculation, or subscription billing. Use for Rapyd payments, refunds, checkout pages, customers, and e-wallets only.

Jentic publishes the only available OpenAPI specification for Rapyd Payments Platform API, keeping it validated and agent-ready. The Rapyd Payments Platform API creates and lists payments, issues refunds, and generates hosted checkout pages for a currency and country, with Rapyd's description citing 900+ payment methods across 100+ countries. It also creates and retrieves customers and Rapyd e-wallets, and lists e-wallets filtered by currency or minimum balance. Write operations accept an idempotency header, and a sandbox host is available for testing.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C-Signals: 4

43%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

60%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

76%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Rapyd Payments Platform API to your agent

Capabilities

Start building with Rapyd Payments Platform API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Rapyd Payments Platform API

Jentic AI Readiness Score

Rapyd Payments Platform API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness