Bond Tech Bond API

Name: Bond API
Brand: Bond API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceBankingapiKey38 EndpointsREST

For Agents

Onboard customers, run KYC and KYB, issue and manage cards, open accounts, move money, and subscribe to transaction webhooks through Bond.

Install Jentic One Beta

Connect the Bond API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Bond 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: 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 Bond API.

Onboard a new customer or business and run the matching KYC or KYB verification

Issue a virtual or physical card, activate it, and close or reissue it on demand

Open and manage deposit accounts including transfer-out and account closure

GET STARTED

Start building with Bond API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Bond API, keeping it validated and agent-ready. Bond is a financial infrastructure platform that lets companies issue cards, open accounts, run KYC and KYB verification, move money, and run their own embedded banking products. The API exposes 38 endpoints covering customers, businesses, cards, accounts, transactions, transfers, statements, webhooks, credit applications, and verification flows. Use it to onboard a customer, verify their identity, issue a debit or credit card, fund an account, and stream transaction events into your ledger.

Use Cases

Patterns agents use Bond API for, with concrete tasks.

★ Embedded Card Issuance for a Fintech Product

Issue branded virtual or physical cards directly from a fintech product without becoming a card issuer. POST /customers creates the cardholder, POST /verification/kyc clears them, and POST /cards issues the card. Lets product teams ship a card in days rather than negotiating with a sponsor bank.

POST /cards with customer_id cust_8821 and card_type 'virtual' to issue a USD debit card

KYC and KYB Onboarding for Regulated Products

Run regulated identity checks on individuals and businesses before opening accounts or issuing cards. POST /verification/kyc and POST /kyb start the checks, and the corresponding GET endpoints return status. Gates compliance for fintech, marketplace, and B2B SaaS products that need verified counterparties.

POST /verification/kyc for customer_id cust_8821 with their date of birth and SSN-last-4

Real-Time Transaction Pipeline

Stream transaction events into a ledger or fraud system as they happen by registering webhooks rather than polling /transactions. POST /webhooks subscribes to event types, and the registered URL receives the payload moments after each transaction. Enables real-time fraud and balance reconciliation for embedded banking products.

POST /webhooks with url https://example.com/webhooks/bond and events ['transaction.created']

Credit Application and Decisioning

Accept a credit application from a customer, track it through underwriting, and issue a credit-backed card on approval. POST /credit-applications creates the request, GET /credit-applications/{id} returns the decision, and the customer's existing card record can be upgraded or reissued. Useful for products that bundle credit lines with their core offering.

POST /credit-applications for customer_id cust_8821 requesting a 5000 USD credit line

AI Agent Banking Operations

An AI agent uses Jentic to discover Bond operations, onboards customers, issues cards, and reconciles transactions on behalf of a fintech operations team. The Bond API key lives in your Jentic One instance so it never enters the agent's prompt. Replaces a multi-week sponsor-bank integration with a single search-load-execute cycle.

Search Jentic for 'issue a virtual card', load the operation, and execute it for the verified customer

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/customers

Create a customer

POST

/verification/kyc

Start KYC verification

POST

/cards

Issue a card

POST

/cards/activate

Activate a physical card

POST

/accounts

Open a deposit account

POST

/transfer

Move money between accounts

POST

/webhooks

Subscribe to webhook events

POST

/credit-applications

Submit a credit application

POST

/customers

Create a customer

POST

/verification/kyc

Start KYC verification

POST

/cards

Issue a card

POST

/cards/activate

Activate a physical card

POST

/accounts

Open a deposit account

POST

/transfer

Why Jentic?

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

Credential isolation

Your Bond API key is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'start KYC verification' or 'issue a virtual card', and Jentic returns the matching Bond operation with its input schema so the agent calls the right endpoint without browsing the Bond reference docs.

Time to first call

FAQs

Specific to using Bond API through Jentic.

Why is there no official OpenAPI spec for Bond API?

Bond does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Bond API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Bond API use?

Bond uses an API key sent in the Authorization header. Through Jentic the key is stored encrypted in the vault and the agent never sees the raw value - only a scoped, short-lived token at execution time.

Can I issue both virtual and physical cards with the Bond API?

Yes. POST /cards creates either type depending on the card_type field. Physical cards must be activated via POST /cards/activate when they reach the cardholder, and any card can be closed with POST /cards/close or reissued via POST /cards/reissue.

How do I run KYC and KYB through Jentic?

Search Jentic for 'start KYC verification', load the POST /verification/kyc operation, then execute it with the customer's identifying details. For businesses, use 'start KYB verification' which loads POST /kyb.

What are the rate limits for the Bond API?

Formal rate limits are not declared in this OpenAPI specification. For high-volume transaction processing, prefer subscribing to /webhooks rather than polling /transactions to avoid unnecessary requests.

Can I get monthly account statements?

Yes. GET /statements returns all statements for the connected accounts and GET /statements/{yyyy-mm} returns the statement for a specific month, formatted as YYYY-MM.

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

Yes. Because Bond carries the customer, card, or account data in the request body of operations like /customers, /cards, and /transfer rather than in a fixed URL path, your self-hosted Jentic One instance lets you decide which of these operations the agent may call and which credentials it may use. You can allow only what the agent needs, such as creating a customer with POST /customers or starting checks with POST /verification/kyc, while issuing a card or moving funds through POST /transfer stays off limits unless you add it. Your own rules on your Jentic One instance set that boundary, so the agent cannot call an operation you did not grant.

Bond Tech Bond API

Connect the Bond API to your agent

Capabilities

Start building with Bond API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs