canonical: https://jentic.com/apis/bond.tech/bond

# Bond Tech Bond API

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.

## For AI agents

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

## Scope

Does not handle merchant acquiring, payroll, or consumer-facing UI flows - use for embedded banking, card issuance, and identity verification only.

## Capabilities

- 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
- Stream transactions and produce monthly statements for a connected account
- Subscribe to webhook events to react to card and transaction activity in real time
- Submit a credit application and track its status through to approval

## Use cases

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

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

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

## Key resources

- **Customers** — Create, retrieve, update, and delete customer records
- **Businesses** — Manage business entities for B2B card and account programs
- **Verification (KYC/KYB)** — Start and check identity and business verification flows
- **Cards** — Issue, activate, reissue, and close virtual or physical cards
- **Accounts** — Open, retrieve, update, and close deposit accounts
- **Transactions and Transfers** — List transactions and move money between accounts
- **Statements** — Retrieve all statements or a specific month's statement
- **Webhooks** — Subscribe to and manage real-time event notifications
- **Credit Applications** — Submit and track credit underwriting requests

## Why Jentic

- **Setup:** Wiring Bond by hand means sending its API key in the Authorization header and mapping the embedded banking, card, and KYC endpoints yourself. Through Jentic you install once, import Bond from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Bond's endpoints carry the customer, card, or account data in the request body (/customers, /cards, /transfer), not a fixed URL path segment, so limit the agent to the operations it needs, such as creating a customer or starting KYC verification. You choose that set, so issuing a card or moving funds with a transfer is not included unless you add it.
- **Credential handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Boleto Cloud API** — Bond issues cards while Boleto Cloud handles Brazilian receivables.
- **Bokio API** — Sync Bond transactions into Bokio's accounting ledger for Swedish operations.
- **BoldSign API** — Sign cardholder agreements in BoldSign before issuing the card via Bond.

## FAQ

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