Copperx API

Name: Copperx API API
Brand: Copperx API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayment Processingbearer92 EndpointsREST

For Agents

Create crypto checkout sessions, payment links, invoices and subscriptions on Copperx, plus manage customers, products and organisation branding.

Connect the Copperx API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Copperx 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.

Install Jentic One Beta (Self-Hosted)

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

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 Copperx API API.

Create a checkout session for a stablecoin payment from a customer wallet

Generate a reusable payment link tied to a product or amount

Issue an invoice to a customer with crypto payment instructions

Set up a recurring subscription against a product price

GET STARTED

Start building with Copperx API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Copperx API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Copperx API, keeping it validated and agent-ready. Copperx is a stablecoin and crypto payments platform exposing 92 REST endpoints across organizations, users, checkout sessions, payment links, invoices, subscriptions, products, customers and withdrawal addresses. The API supports brand customisation, role-based user management and creation of crypto payment flows that work across multiple chains. Authentication is bearer-token based, and operations are grouped by resource path under /api/v1, with dedicated endpoints for organization branding, withdrawal address management and points tokens.

Use Cases

Patterns agents use Copperx API API for, with concrete tasks.

★ Stablecoin Checkout for Online Stores

Online stores accepting stablecoin payments can create a checkout session per cart, redirect the buyer to Copperx's hosted page, and receive a webhook when payment completes. Checkout sessions encode the amount, currency and product references, and return a session URL that the storefront serves to the customer.

Create a Copperx checkout session for 100 USDC tied to product ID 'prod_abc' and return the hosted session URL to redirect the customer.

Recurring Crypto Subscriptions

SaaS businesses with crypto-native users can charge monthly USDC subscriptions through Copperx by linking a customer to a product price and starting a subscription. The subscriptions and invoices endpoints work together: each billing cycle generates an invoice that the customer settles from their wallet.

Create a customer record from an email, attach product ID 'prod_pro_monthly', and start a monthly subscription billing in USDC.

Crypto Invoicing for B2B Services

B2B service providers invoicing in crypto can issue Copperx invoices with line items, due dates and customer references, then track payment status through the API. The invoice resource stores the amount, currency and the wallet address the customer used to settle, supporting reconciliation against on-chain transactions.

Create an invoice for customer 'cust_123' with line item description 'Consulting June 2026', amount 5000 USDC, due in 14 days.

AI Agent Crypto Payment Flow

An AI agent acting on behalf of a finance team can create payment links and invoices on demand by calling Copperx through Jentic. The agent never holds the bearer token and uses Jentic's intent search to pick between checkout sessions, payment links and invoices based on the use case described in natural language.

Use Jentic to create a Copperx payment link for 250 USDC and return the URL to share with the buyer.

Key Endpoints

92 endpoints — jentic publishes the only available openapi specification for copperx api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/api/v1/auth/me

Get the authenticated user

GET

/api/v1/organization

Get organisation info

PUT

/api/v1/organization/brand

Update organisation branding

GET

/api/v1/users

List users in the organisation

GET

/api/v1/organization/withdrawal-addresses

List withdrawal addresses

POST

/api/v1/organization/withdrawal-addresses

Create a withdrawal address

PUT

/api/v1/users/{id}/role

Update a user's role

GET

/api/v1/auth/me

Get the authenticated user

GET

/api/v1/organization

Get organisation info

PUT

/api/v1/organization/brand

Update organisation branding

GET

/api/v1/users

List users in the organisation

GET

/api/v1/organization/withdrawal-addresses

List withdrawal addresses

Why though Jentic?

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

Credential isolation

The Copperx bearer token sits in the Jentic credential vault. Agents creating checkout sessions, payment links or invoices through Jentic never see the token in their reasoning context, and per-organisation tokens stay isolated.

Intent-based discovery

Agents search Jentic with intents like 'create Copperx payment link' or 'issue stablecoin invoice' and Jentic returns the matching operation under /api/v1, including the request body schema for amounts, currencies and product references.

Time to first call

Direct integration: 2-4 days to wire up checkout, invoicing, webhooks and withdrawal address management. Through Jentic: under an hour from signup to first checkout session.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Stripe API

Fiat-first payment processor with optional crypto support, far broader market coverage

Choose Stripe when the merchant primarily accepts cards and bank transfers and treats crypto as a secondary rail.

Alternative

PayPal Invoicing API

Established fiat invoicing platform without native stablecoin settlement

Pick PayPal Invoicing when the customer base prefers fiat rails and existing PayPal balances over wallet payments.

Complementary

Binance API

Spot exchange for moving received stablecoins into other crypto assets

Pair Binance with Copperx when treasury teams want to convert received USDC into BTC or fiat after settlement.

FAQs

Specific to using Copperx API API through Jentic.

Why is there no official OpenAPI spec for Copperx API?

Copperx does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Copperx API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Copperx API use?

Copperx uses bearer token authentication. Through Jentic the bearer token is held in the credential vault and attached to the Authorization header on every Copperx call, so the secret never enters agent context.

Can I create a recurring crypto subscription with the Copperx API?

Yes. Create a product with a recurring price, attach a customer, and POST against the subscription endpoints. Each cycle generates a new invoice that the customer settles from their wallet, with statuses surfaced through the invoice resource.

How do I manage withdrawal addresses on the Copperx API?

GET /api/v1/organization/withdrawal-addresses lists configured addresses, POST creates a new one, and DELETE /api/v1/organization/brand-logo and similar endpoints handle related organisation assets. Treat address creation as security-sensitive and gate it behind admin-only roles.

What rate limits apply to the Copperx API?

The OpenAPI spec does not declare formal rate limits. Implement exponential backoff on HTTP 429 responses and avoid polling status endpoints when webhooks are available for the same event.

How do I create a Copperx checkout session through Jentic?

Run pip install jentic, search Jentic with 'create Copperx checkout session', load the operation schema and execute it with the amount, currency and product reference to receive a hosted session URL.