Install Jentic One Beta

Connect the Clearpay API to your agent

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

Create a checkout for a Clearpay order

Authorize and capture payments

Refund or void a payment

Retrieve a single payment or list payments

Update the shipping details on an order

GET STARTED

Start building with Clearpay API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Clearpay API for, with concrete tasks.

★ Agent-Managed Checkout and Payment

An AI agent takes an approved order through Clearpay by creating a checkout, then authorizing and capturing the payment once the customer confirms. It reads the checkout by token and follows the payment through to capture. This lets an agent run the pay-later flow end to end as part of an order workflow.

Create a checkout for an approved order, then authorize and capture the payment once the customer confirms

Refunds and Payment Adjustments

Teams handle post-sale changes by refunding or voiding a payment and updating an order's shipping details. The API exposes refund, void, and shipping-update operations addressed by the order identifier. This lets an agent process a return or correct an order without manual dashboard work.

Refund a payment for a returned order and update the order's shipping details where they changed

Payment Status Reconciliation

An agent reconciles orders by retrieving a payment by order identifier or listing payments and comparing their status with an internal system. The API returns individual payments and a payment list for this purpose. This suits a scheduled reconciliation that flags mismatches between Clearpay and the order system.

List recent payments, retrieve each by order identifier, and flag any whose status differs from the internal record

Key Endpoints

12 endpoints — the clearpay api creates buy-now-pay-later checkouts and authorizes, captures, refunds, and voids the resulting payments.

METHOD

PATH

DESCRIPTION

GET

/v2/configuration

Read the merchant configuration

POST

/v2/checkouts

Create a checkout

GET

/v2/checkouts/{token}

Retrieve a checkout by token

POST

/v2/payments/auth

Authorize a payment

POST

/v2/payments/capture

Capture a payment

POST

/v2/payments/{orderId}/refund

Refund a payment

GET

/v2/payments/{orderId}

Retrieve a payment by order

GET

/v2/payments

List payments

GET

/v2/configuration

Read the merchant configuration

POST

/v2/checkouts

Create a checkout

GET

/v2/checkouts/{token}

Retrieve a checkout by token

POST

/v2/payments/auth

Authorize a payment

POST

/v2/payments/capture

Capture a payment

POST

/v2/payments/{orderId}/refund

Refund a payment

GET

/v2/payments/{orderId}

Retrieve a payment by order

GET

/v2/payments

List payments

Why Jentic?

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

Setup

Wiring the Clearpay API by hand means handling HTTP Basic auth with a Merchant ID and Secret Key and sequencing checkout, authorization, and capture yourself. Through Jentic you install once, import Clearpay from the API Directory, store the keys once, and your agent creates checkouts and captures payments.

Permission scoping

Clearpay puts the order identifier in the URL path, so a rule can bound your agent to a single order. You can also scope by operation, allowing reads and captures while withholding refunds and voids, and every call the agent makes is logged.

Credential isolation

Your Clearpay Merchant ID and Secret Key are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

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

FAQs

Specific to using Clearpay API through Jentic.

What authentication does the Clearpay API use?

The Clearpay API uses HTTP Basic authentication per its OpenAPI spec, with your Merchant ID as the username and your Secret Key as the password. Through Jentic those values are held encrypted by your own Jentic One instance and attached at call time, so they never reach the agent's context.

Can I refund a payment with the Clearpay API?

Yes. The API exposes refund and void operations addressed by the order identifier, alongside capture and authorization. An agent can process a return by refunding the payment on the order.

What are the rate limits for the Clearpay API?

The OpenAPI spec does not specify rate limits. Check the Clearpay and Afterpay developer documentation at https://developers.afterpay.com for current limits and usage guidance.

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

Yes. Because the order identifier sits in the URL path, a rule can bound your agent to a single order, and you can scope by operation to allow reads and captures while withholding refunds and voids. Every call the agent makes is logged.

How do I run a Clearpay checkout through Jentic?

Search Jentic for 'create a checkout' or 'capture a payment', add the Clearpay API from the directory, and store your Merchant ID and Secret Key once. Your agent then creates the checkout and captures the payment. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a Clearpay MCP server?

You don't need an MCP server to give your agent the Clearpay API. Jentic connects it directly from the API Directory: import it, store your keys once, and your agent creates checkouts and captures payments. Operations are discovered on demand, so no extra server's tool definitions sit in the agent's context.

Clearpay API

Name: Clearpay API
Brand: Clearpay API
Availability: InStock

Official vendor OpenAPI document · agent-readyPaymentsPayment Processingbasic12 EndpointsREST

For Agents

Create Clearpay checkouts and authorize, capture, refund, and void payments, retrieve or list payments, and update order shipping. Returns checkout and payment records for an agent to act on.

Use for: Create a Clearpay checkout for an order, Authorize a payment for an approved order, Capture a previously authorized payment, Refund a payment on an order

Not supported: Does not handle card payments, settlement reporting, or dispute management. Use for Clearpay checkouts and payment authorization, capture, refund, and void only.

The Clearpay API creates buy-now-pay-later checkouts and authorizes, captures, refunds, and voids the resulting payments. It retrieves individual payments and lists them, updates order shipping details, and reads the merchant configuration. Agents can drive the full Clearpay payment lifecycle for an order without building against the dashboard.

Jentic One on Github View OpenAPI Document

Connect the Clearpay API to your agent

Capabilities

Start building with Clearpay API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Clearpay API