canonical: https://jentic.com/apis/cryptomkt.com/cryptomkt

# Cryptomkt CryptoMarket API

Jentic publishes the only available OpenAPI specification for CryptoMarket API, keeping it validated and agent-ready. CryptoMarket (CryptoMKT) is a Latin American cryptocurrency exchange whose REST API covers public market data, authenticated trading, and wallet operations. The catalogued slice exposes 65 endpoints split across public price and order book feeds, spot trading order management, and wallet transfers and balances. Both HTTP Basic and Bearer authentication are accepted on private endpoints.

## For AI agents

Read CryptoMarket prices and order books, place and cancel spot trading orders, and move balances between trading and wallet accounts.

## Scope

Does not provide fiat on-ramp KYC, custody insurance, or derivatives trading - use for spot trading, market data, and wallet transfers on CryptoMarket only.

## Capabilities

- Look up the live ticker, last price, and 24-hour stats for a trading pair
- Read the order book at a specified depth for any supported symbol
- Place a limit or market order on a trading pair and receive the resulting order ID
- Cancel a specific open order or cancel every open order on a symbol at once
- List historical trades for an account filtered by symbol and time range
- Transfer balance between the trading account and the spot wallet account
- Withdraw a cryptocurrency to an external address with optional payment ID for chains that require it

## Use cases

### Algorithmic Spot Trading

Run an automated trading strategy on CryptoMarket by polling the public price feed for signals and placing limit orders through the trading endpoints. The API exposes order placement, cancellation, and trade history endpoints needed to manage open positions, and the same Bearer token works for both reads and writes. This replaces hand-rolled HMAC signing for teams that prefer token-based auth.

Example prompt: Call POST `/spot/order` with symbol=BTCUSDT, type=limit, side=buy, quantity=0.01, and price=60000 to place a buy.

### Wallet Transfer Automation

Move funds between the spot wallet and trading account ahead of campaign trades or scheduled withdrawals. The agent calls the wallet transfer endpoint with a currency and amount, and follows up with a withdrawal endpoint when funds need to leave CryptoMarket. This avoids manual treasury work for trading desks that rebalance frequently.

Example prompt: Call the wallet transfer endpoint with source=spot, destination=trading, currency=USDT, and amount=500 to fund a strategy.

### Market Data Aggregator

Feed CryptoMarket prices into a multi-exchange dashboard or analytics product without authentication. The /public/* endpoints return tickers, order books, and historical price data over HTTPS without keys, so an aggregator can pull CryptoMarket alongside other exchanges. Combined with rate-limited polling, this powers Latin America-focused price comparison sites and arbitrage screens.

Example prompt: Call GET `/public/price/ticker` to retrieve the latest ticker for every supported symbol and persist into the time-series store.

### AI Agent Trading Assistant

An AI agent acting as a trading copilot can read prices, propose trades, and execute them on CryptoMarket through Jentic. The agent searches for the right `/spot/order` or /public/* operation, loads its schema, and executes against the auth credentials in the vault. Both Basic and Bearer credentials are scoped at the Jentic layer, so the same agent flow works for either auth model.

Example prompt: Search Jentic for 'place a spot trading order', load the CryptoMarket order operation, and execute it with the user's symbol, side, and quantity.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/public/symbol` | List all tradable symbols |
| GET | `/public/price/ticker` | Get the latest ticker for every symbol |
| GET | `/public/price/ticker/{symbol}` | Get the latest ticker for a single symbol |
| GET | `/public/price/history` | Retrieve historical price data |
| GET | `/public/currency` | List all supported currencies |

## Key resources

- **Public Market Data** — Tickers, order books, and historical prices accessible without authentication
- **Spot Trading** — Place, cancel, and inspect spot orders and trades
- **Wallet** — Transfer balances between accounts and withdraw to external addresses

## Why Jentic

- **Setup:** Wiring the CryptoMarket API by hand means managing separate Basic and Bearer credentials for wallet and trading, pointing at the api.exchange.cryptomkt.com/api/3 host, and handling retries across dozens of endpoints. Through Jentic you install once, import the CryptoMarket API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** CryptoMarket takes trading and wallet targets such as the symbol or transfer detail in the request body, so limit the agent to the operations it needs, such as reading market prices or symbols. You choose which operations are in scope, so trading and wallet-transfer operations are not included unless you add them.
- **Credential handling:** Your CryptoMarket Basic and Bearer credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get the ticker price for a symbol' or 'place a spot order', and Jentic returns the matching CryptoMarket operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Binance API** — Global cryptocurrency exchange with deeper liquidity and a broader product surface
- **Kraken API** — US/EU-focused cryptocurrency exchange with margin and staking
- **CoinGecko API** — Cross-exchange market data and pricing aggregator

## FAQ

### Why is there no official OpenAPI spec for CryptoMarket API?

CryptoMarket does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call CryptoMarket 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 CryptoMarket API use?

CryptoMarket private endpoints accept either HTTP Basic or HTTP Bearer authentication, with separate schemes for the wallet and trading sub-systems. Public endpoints under /public/* require no authentication. Through Jentic the credentials live in the vault and never enter the agent context.

### Can I place spot trading orders with the CryptoMarket API?

Yes. Authenticate against the trading scheme and call POST `/spot/order` with symbol, type, side, quantity, and price for limit orders. The response returns the order ID, which can be used with the cancel endpoint.

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

CryptoMarket applies per-IP and per-key request limits that vary by endpoint group; trading endpoints are tighter than public market data. The exchange's documentation lists current per-endpoint allowances; treat 429 responses as a signal to back off.

### How do I cancel all open orders on a symbol through Jentic?

Search Jentic for 'cancel all open spot orders' and execute the loaded CryptoMarket operation with the symbol parameter. Jentic supplies the trading credentials from the vault and returns the cancellation summary.

### Is the CryptoMarket API free?

API access is free; CryptoMarket charges trading fees per filled order and standard withdrawal fees. Fee schedules are published at https://www.cryptomkt.com/fees.

### How do I move balance between the spot wallet and trading account?

Use the wallet transfer endpoint with source=spot, destination=trading, the currency code, and the amount. The transfer is atomic and the trading endpoints reflect the new balance on the next call.

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

Yes. Because you run your own self-hosted Jentic One instance, your rules decide which CryptoMarket operations the agent may call, so you can grant read-only access to public market data such as GET `/public/price/ticker` and GET `/public/symbol` while keeping the trading and wallet endpoints out of scope. The spot order operations like POST `/spot/order` and the wallet transfer and withdrawal operations are only available to the agent if you explicitly add them. Your Basic and Bearer credentials are stored by your own instance and injected only for the operations you have allowed, so the agent can never reach an endpoint you have not approved.