canonical: https://jentic.com/apis/staging-biz.coinprofile.co/staging-biz-coinprofile

# Staging Biz Coinprofile Coinprofile business API

Coinprofile business API. The API exposes 33 endpoints secured with apiKey authentication.

## For AI agents

Programmatically retrieve user's transaction records, retrieve merchant account balance. Covers 33 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for social media only.

## Capabilities

- Retrieve user's transaction records
- Update merchant record
- Make a mock payment
- Query and filter Coinprofile business API records by parameters
- Monitor Coinprofile business API operational status and events

## Use cases

### Social Media Operations

Use the Coinprofile business API to perform social media operations programmatically. The API provides 33 endpoints covering core functionality including retrieve user's transaction records, retrieve merchant account balance, retrieve merchant record.

Example prompt: Call GET /transaction to retrieve user's transaction records

### Automated Voucher Management

Automate voucher operations by combining multiple Coinprofile business API endpoints. Agents can retrieve merchant account balance and then retrieve merchant record in a single workflow.

Example prompt: Call GET `/v1/balance` to retrieve merchant account balance, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Coinprofile business API 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 apiKey tokens manually.

Example prompt: Search Jentic for 'retrieve user's transaction records', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/transaction` | Retrieve user's transaction records |
| GET | `/v1/balance` | Retrieve merchant account balance |
| GET | `/v1/merchants` | Retrieve merchant record |
| PATCH | `/v1/merchants` | Update merchant record |
| POST | `/v1/mock/payment` | Make a mock payment |
| GET | `/v1/currency/rates` | Retrieves conversion rates |
| GET | `/v1/transactions/summary` | Retrieve merchant transaction summary |
| POST | `/v1/vouchers` | Create a new voucher payment |

## Key resources

- **Voucher** — Operations related to Voucher
- **Balance** — Operations related to Balance
- **Transaction** — Operations related to Transaction
- **Payment** — Operations related to Payment
- **Wallet** — Operations related to Wallet

## Why Jentic

- **Setup:** Wiring the Coinprofile business API by hand means carrying its API key into staging-biz.coinprofile.co/v2 and building the transaction, balance, and voucher calls yourself. Through Jentic you install once, import the Coinprofile business API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** You can limit the agent to the operations it needs, such as reading transactions, checking balance, or fetching currency rates, so it stays on reads and never patches a merchant or creates a voucher unless you add those operations.
- **Credential handling:** Your Coinprofile API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list my transactions' or 'get the current currency rates', and Jentic returns the matching Coinprofile business API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Facebook** — Alternative social media API
- **Twitter** — Alternative social media API
- **Linkedin** — Complementary social media API

## FAQ

### What authentication does the Coinprofile business API use?

The Coinprofile business API uses an API key passed in the `X-Api-Key` header. 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 retrieve user's transaction records with the Coinprofile business API?

Yes. Use the GET /transaction endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Coinprofile business API?

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 retrieve user's transaction records through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'retrieve user's transaction records'. Jentic returns the matching Coinprofile business API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Coinprofile business API have?

The Coinprofile business API exposes 33 endpoints covering voucher, balance, transaction operations.

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

Yes. Because Jentic One is self-hosted, you decide which Coinprofile operations your agent may call, so you can grant read-only access to GET /transaction, GET `/v1/balance`, and GET `/v1/currency/rates` while withholding everything else. The agent can never patch a merchant record via PATCH `/v1/merchants` or create a voucher via POST `/v1/vouchers` unless you explicitly add those operations. Your API key stays under your own rules and is injected only for the calls you have allowed.