canonical: https://jentic.com/apis/swaggerhub.bringin-a9e/bringin-apis

# Bringin A9e Bringin APIs

This is Bringin APIs that you can use to make a Bitcoin on and off-ramp available for your European customers. We intend to provide a simple yet best crypto on and off-ramp solution with SEPA instant support at the best rates in the market. Authentication While the APIs are available to the public to build, we provide an 'api-key' and 'api-secret' for each company to make secure API calls. Request. The API exposes 25 endpoints.

## For AI agents

Programmatically bringin onboarding link, get kyc status. Covers 25 operations.

## Scope

Does not handle payments, communications, or developer tools - use for crm only.

## Capabilities

- Bringin Onboarding link
- Get KYC status
- Deposit Details
- Query and filter Bringin APIs records by parameters
- Monitor Bringin APIs operational status and events

## Use cases

### CRM Operations

Use the Bringin APIs to perform crm operations programmatically. The API provides 25 endpoints covering core functionality including bringin onboarding link, get kyc status, get offramp rate.

Example prompt: Call POST `/api/v0/application/connect` to bringin onboarding link

### Automated User Onboarding Management

Automate user onboarding operations by combining multiple Bringin APIs endpoints. Agents can get kyc status and then get offramp rate in a single workflow.

Example prompt: Call GET `/api/v0/user/kyc-status/{userId}` to get kyc status, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Bringin APIs endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'bringin onboarding link', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/v0/application/connect` | Bringin Onboarding link |
| GET | `/api/v0/user/kyc-status/{userId}` | Get KYC status |
| POST | `/api/v0/offramp/rates` | Get offramp rate |
| POST | `/api/v0/offramp/address` | Get Offramp address |
| POST | `/api/v0/account/get-balance` | Get user balance |
| POST | `/api/v0/account/get-details` | Deposit Details |
| POST | `/api/v0/account/transactions` | Get Transactions |
| POST | `/api/v0/account/send/initiate/onchain/fee-estimate` | Get Estimated Onchain Fee |

## Key resources

- **User Onboarding** — The user needs to accept Bringin's terms and conditions, and onboarding is done on the Bringin inter
- **Offramp** — ## Offramp Bitcoin to Bringin IBAN

A set of APIs to create an offramp order to convert incoming Bit
- **Account** — APIs to deposit Bitcoin / Euros. Withdraw Bitcoin / Euros.

Bitcoin custody is enabled for Businesse
- **Manage Bank Beneficiary** — APIs to add new Bank beneficiaries to the Euro account withdrawals.
- **Onramp** — APIs for buying Bitcoin with Euros through various payment methods including Lightning and on-chain

## Why Jentic

- **Setup:** Wiring the Bringin APIs by hand means mapping its application, user, account, and offramp endpoints, choosing between the dev and api.bringin.xyz hosts, and handling retries yourself. Through Jentic you install once, import the Bringin APIs from the API Directory, and your agent calls it without you writing that plumbing.
- **Permission scoping:** The API puts the user id in the URL path (`/api/v0/user/kyc-status/{userId}`), so a rule can pin your agent to reading one user's KYC status. You choose the operations it may call, so account transactions with POST `/api/v0/account/transactions` are not included unless you add them.
- **Credential handling:** This spec defines no authentication, so there is no credential to store. If you point it at a host that adds a key later, that key is stored once, encrypted, by your own Jentic One instance and injected at execution time, never entering the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'check a user's KYC status' or 'get an account balance', and Jentic returns the matching Bringin operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the Bringin APIs use?

The Bringin APIs uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I bringin onboarding link with the Bringin APIs?

Yes. Use the POST `/api/v0/application/connect` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Bringin APIs?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I bringin onboarding link through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'bringin onboarding link'. Jentic returns the matching Bringin APIs operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Bringin APIs have?

The Bringin APIs exposes 25 endpoints covering user onboarding, offramp, account operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which Bringin operations the agent may call and which credentials it may use. Because the API carries the user id in the path, you can pin the agent to reading a single user's KYC status via GET `/api/v0/user/kyc-status/{userId}` while leaving account operations off the list. Sensitive calls such as POST `/api/v0/account/transactions` or POST `/api/v0/account/get-balance` are only reachable if you explicitly add them to what the agent is allowed to run.