Install Jentic One Beta

Connect the Checkout.com Payment Platform API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Checkout.com Payment 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%2Fcheckout.com%2Fcheckout" | 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%2Fcheckout.com%2Fcheckout" | 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 Checkout.com Payment Platform API.

Tokenise card details

Create and retrieve payments

Capture, refund, and void a payment

List the actions taken on a payment

Create and manage customers

GET STARTED

Start building with Checkout.com Payment Platform API

Explore with Jentic One

View OpenAPI Document

Settle and reverse payments

Complete or unwind a charge after authorisation. The agent captures an authorised payment, refunds a settled one, or voids one that should not go through.

Call POST /payments/{id}/captures, /refunds, or /voids as needed

Manage customers

Keep buyer records tied to payments. The agent creates customers and reads them back so repeat charges can reference a stored customer.

Call POST /customers to create a customer, GET /customers/{id} to read it

Key Endpoints

42 endpoints — the checkout.

METHOD

PATH

DESCRIPTION

POST

/tokens

Tokenise card details

POST

/payments

Create a payment

GET

/payments/{id}

Retrieve a payment

POST

/payments/{id}/captures

Capture an authorised payment

POST

/payments/{id}/refunds

Refund a payment

POST

/payments/{id}/voids

Void a payment

POST

/customers

Create a customer

GET

/customers/{id}

Retrieve a customer

POST

/tokens

Tokenise card details

POST

/payments

Create a payment

GET

/payments/{id}

Retrieve a payment

POST

/payments/{id}/captures

Capture an authorised payment

POST

/payments/{id}/refunds

Refund a payment

POST

/payments/{id}/voids

Void a payment

POST

/customers

Create a customer

GET

/customers/{id}

Retrieve a customer

Why Jentic?

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

Setup

Wiring the Checkout.com Payment Platform API by hand means managing a secret key, pointing at the api.checkout.com host, and shaping the payment requests yourself. Through Jentic you install once, import the Checkout.com Payment Platform API from the Jentic API Directory, store the key once, and your agent calls it.

Permission scoping

You decide which operations your agent may call, so it can read payments without being able to refund or void them. Because the payment id sits in the URL path (/payments/{id}), a rule can pin the agent to a single payment rather than the whole account.

Credential isolation

Your Checkout.com secret key, sent as a bearer token, along with any OAuth2 credentials, 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.

Intent-based discovery

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

FAQs

Specific to using Checkout.com Payment Platform API through Jentic.

What authentication does the Checkout.com Payment Platform API use?

It authenticates requests with a secret key sent as a bearer token, and supports OAuth2 for applicable flows. Through Jentic, those credentials are stored encrypted in your Jentic One instance and injected at execution time, so they never enter the agent context.

What can an agent do with the Checkout.com Payment Platform API?

It can tokenise card details, create and retrieve payments, capture, refund, and void a payment, list the actions taken on a payment, and create and manage customers. The API is built for accepting card payments online.

How does an agent connect to the Checkout.com Payment Platform API through Jentic?

Install Jentic One, import the Checkout.com Payment Platform API from the Jentic API Directory, and store the secret key once. Your agent then calls the operations you have allowed without handling the raw key.

What are the rate limits for the Checkout.com Payment Platform API?

Rate limits are not specified in the OpenAPI spec. Check the Checkout.com documentation for current limits. Through Jentic, retries are handled in the execution layer.

How many endpoints does the Checkout.com Payment Platform API have?

The Checkout.com Payment Platform API exposes 42 endpoints covering payments, customers, tokens, and related operations.

Can I limit what my agent is allowed to do with the Checkout.com Payment Platform API?

Yes. Jentic One is self-hosted by you, so your own rules decide which operations your agent may call. You can let it read payments without being able to refund or void them, and because the payment id sits in the URL path, such as /payments/{id}, a rule can pin the agent to a single payment.

Checkout.com Payment Platform API

AI ReadinessAI-Aware (B)66/100

See full scorecard

Official vendor OpenAPI document · agent-readyPaymentsPayment Processingbearer, oauth242 EndpointsREST

For Agents

Accept and manage card payments through the Checkout.com Payment Platform API. Tokenise cards, create payments, capture, refund, and void them, and manage customers. Secured with a secret key sent as a bearer token, with OAuth2 for applicable flows.

Use for: Create a payment, Capture an authorised payment, Refund a payment, Void a payment

Not supported: Does not handle payouts or dispute management - use it to accept, capture, refund, and void card payments and manage the customers behind them.

The Checkout.com Payment Platform API lets an agent accept and manage card payments end to end. It can tokenise card details, create and retrieve payments, capture, refund, and void a payment, list the actions taken on a payment, and create and manage customers. It is a payment processing service for online businesses.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

97%

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

100%

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

93%

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: DSignals: 4

29%

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.

55%

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: B+Signals: 1

68%

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: B+Signals: 1

68%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Checkout.com Payment Platform API to your agent

Capabilities

Start building with Checkout.com Payment Platform API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Checkout.com Payment Platform API

Jentic AI Readiness Score

Checkout.com Payment 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