canonical: https://jentic.com/apis/coinremitter.com/coinremitter-main

# Coinremitter

Coinremitter is a cryptocurrency payment gateway covering wallet management, address generation, withdrawals, transaction lookups, payment invoices, and live fiat/crypto conversion rates. The API exposes 11 POST endpoints authenticated with paired x-api-key and x-api-password headers tied to a specific wallet, supporting Bitcoin and additional cryptocurrencies. Merchants can quote in fiat, accept payment in crypto, and reconcile by deposit address without standing up their own wallet infrastructure.

## For AI agents

Run a crypto payment gateway: generate addresses, send withdrawals, issue invoices, look up transactions, and fetch live fiat-crypto conversion rates through 11 wallet-scoped endpoints.

## Scope

Does not handle card processing, bank transfers, or crypto exchange trading - use for crypto wallet payments, invoicing, and live rate lookups only.

## Capabilities

- Generate per-customer deposit addresses via POST `/wallet/address/create`
- Validate any address before payout via POST `/wallet/address/validate`
- Estimate and execute crypto withdrawals via `/wallet/withdraw/estimate` and `/wallet/withdraw`
- Create hosted payment invoices and resolve them later via `/invoice/create` and `/invoice/get`
- Read wallet balance and pending amounts via POST `/wallet/balance`
- Fetch live fiat-to-crypto and crypto-to-fiat rates via /fiat-to-crypto-rate and /crypto-to-fiat-rate
- Look up transactions by Coinremitter ID or by deposit address

## Use cases

### Crypto Checkout with Live Pricing

Quote a customer in their local fiat currency by calling POST /fiat-to-crypto-rate, then issue the invoice in crypto via POST `/invoice/create.` Coinremitter returns a hosted invoice URL and a fresh deposit address; polling POST `/invoice/get` confirms settlement before fulfilment. The single-API merchant flow combines pricing and invoicing without a separate market-data feed.

Example prompt: Call POST /fiat-to-crypto-rate with from=USD, to=BTC, amount=49.99, then POST `/invoice/create` with the resulting BTC amount and currency=BTC, returning the invoice URL

### Per-Customer Deposit Addresses

Allocate a unique address to each user by calling POST `/wallet/address/create` with a label that maps back to internal customer IDs. Coinremitter manages key rotation under the hood. Incoming funds can later be attributed by querying POST `/wallet/address/transactions` with the address.

Example prompt: Call POST `/wallet/address/create` with label='customer-12345' and persist the returned address against the customer record

### Automated Crypto Payouts

Disburse winnings, refunds, or affiliate commissions in crypto by calling POST `/wallet/withdraw/estimate` to preview the network fee, then POST `/wallet/withdraw` with destination and amount. The transaction ID returned is resolvable via POST `/wallet/transaction` for downstream reconciliation.

Example prompt: Call POST `/wallet/withdraw/estimate` then POST `/wallet/withdraw` with to_address and amount=0.05, returning the Coinremitter transaction ID

### Reconciliation and Reporting

Reconcile incoming crypto deposits by polling POST `/wallet/address/transactions` for each customer-tagged address, or look up a specific Coinremitter transaction via POST `/wallet/transaction.` Combine with POST `/wallet/balance` for the running total. This supports finance reporting workflows without scraping a block explorer.

Example prompt: Call POST `/wallet/address/transactions` with address='bc1q...' and aggregate confirmed transactions for end-of-day reporting

### AI Agent Crypto Workflows via Jentic

Build LLM-driven payment agents that issue crypto invoices, send payouts, or check rates by searching Jentic for the operation and executing it with the returned schema. Coinremitter's paired-header credentials live in your Jentic One instance; the agent never sees the wallet API key or password.

Example prompt: Use Jentic to search 'create a crypto payment invoice', load the POST `/invoice/create` schema, and execute it for amount=100 USD

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/invoice/create` | Create a payment invoice |
| POST | `/invoice/get` | Get invoice details by ID |
| POST | `/wallet/address/create` | Generate a new wallet address |
| POST | `/wallet/withdraw` | Send cryptocurrency from the wallet |
| POST | `/wallet/balance` | Get wallet balance |
| POST | `/fiat-to-crypto-rate` | Get fiat-to-crypto conversion rate |
| POST | `/crypto-to-fiat-rate` | Get crypto-to-fiat conversion rate |

## Key resources

- **Wallet Addresses** — Generate and validate deposit addresses
- **Withdrawals** — Estimate fees and send crypto from the wallet
- **Transactions** — Look up by Coinremitter ID or deposit address
- **Invoices** — Create hosted payment invoices and check status
- **Balance** — Read wallet balance and pending amounts
- **Conversion Rates** — Fetch live fiat-to-crypto and crypto-to-fiat rates

## Why Jentic

- **Setup:** Wiring Coinremitter by hand means sending both its x-api-key and x-api-password headers on the api.coinremitter.com host and handling its POST-based invoice, wallet, and rate endpoints yourself. Through Jentic you install once, import Coinremitter from the API Directory, store the key and password once, and your agent calls it.
- **Permission scoping:** Coinremitter takes the wallet and invoice target in the request body, so you scope by operations: limit the agent to the calls it needs, such as creating an invoice or reading a rate, so operations like withdrawing from a wallet are not included unless you add them.
- **Credential handling:** Your Coinremitter x-api-key and x-api-password are stored once, encrypted, by your own Jentic One instance and injected as headers at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a crypto payment invoice' or 'check a wallet balance', and Jentic returns the matching Coinremitter operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **NOWPayments API** — Crypto gateway with broader coin coverage and fiat off-ramp options
- **Blockchain.com API** — Direct on-chain Bitcoin data for independent transaction verification
- **Stripe API** — Card and bank rails for buyers who do not pay in crypto
- **Coinpaprika API** — Independent crypto market data to cross-check rates

## FAQ

### What authentication does the Coinremitter API use?

Two paired headers are required on every call: x-api-key and x-api-password, both scoped to a specific wallet created in the Coinremitter dashboard. Through Jentic both values live in the encrypted vault and are injected at execution so they never enter the agent's prompt.

### Can I get live fiat-to-crypto conversion rates with Coinremitter?

Yes. POST /fiat-to-crypto-rate returns the rate to convert a fiat amount into the wallet's coin, and POST /crypto-to-fiat-rate goes the other way. This avoids the need for a separate market-data API at checkout.

### What are the rate limits for the Coinremitter API?

The OpenAPI spec does not enumerate rate limits. Limits are enforced per wallet and per account; consult your Coinremitter dashboard. HTTP errors indicate when limits or wallet permissions block a call.

### How do I issue a crypto invoice with Coinremitter through Jentic?

Search Jentic for 'create a crypto payment invoice', load the POST `/invoice/create` schema, and execute it with amount, currency, and notify_url. Jentic returns the invoice URL and ID so the agent can redirect the buyer and poll POST `/invoice/get` for status.

### Which cryptocurrencies does Coinremitter support?

Coinremitter supports Bitcoin and additional altcoins. Each wallet is scoped to one coin and has its own x-api-key and x-api-password - create separate wallets in the dashboard to support multiple coins in parallel.

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

Yes. Coinremitter takes the target wallet and invoice details in the request body rather than in the credential, so with your self-hosted Jentic One you scope the agent by operation: your own rules decide which of the 11 endpoints it may call. You can allow only what a workflow needs, such as POST `/invoice/create` and POST /fiat-to-crypto-rate for a checkout agent, while excluding sensitive operations like POST `/wallet/withdraw` and POST `/wallet/address/create` unless you explicitly add them. The paired x-api-key and x-api-password stay stored in your instance and are injected at execution, so the agent operates only within the calls and credentials you permit.