Gemini REST API
✓ Official Vendor SpecFinanceBankingapiKey28 EndpointsREST
For Agents
Place and cancel cryptocurrency orders, read live order books, and pull account balances and trade history on Gemini.
Use for: Place a limit buy order for 0.5 BTC at $30,000, Cancel all open orders on Gemini, Get the current order book for ETHUSD, Retrieve my Gemini account balances
Not supported: Does not handle fiat banking, custody, or staking — use for cryptocurrency trading, market data, and account operations on Gemini only.
The Gemini REST API is the trading and account interface for Gemini, the regulated cryptocurrency exchange. It exposes 28 endpoints for public market data (order books, ticker, price feeds, trading symbols), authenticated trading (place new order, cancel single, cancel all, status), account state (balances, notional balances, transfers, deposit address creation), and historical activity (my trades, order history, fee promotions). Authentication uses HMAC-SHA384 with three headers — X-GEMINI-APIKEY, X-GEMINI-PAYLOAD, and X-GEMINI-SIGNATURE — over a base64-encoded JSON request payload.
Install Jentic One Beta
Connect the Gemini REST API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Gemini REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Gemini REST API.
Read real-time order book depth for any trading symbol via /v1/book/{symbol}
Place buy and sell orders, including limit, market, and stop variants, through /v1/order/new
Cancel a specific order with /v1/order/cancel or every open order at once with /v1/order/cancel/all
Pull account balances in native units and notional USD via /v1/balances and /v1/notionalbalances/{currency}
Generate a new deposit address for a supported currency through /v1/deposit/{currency}/newAddress
Retrieve historical fills with /v1/mytrades and order history with /v1/orders/history
Use Cases
Patterns agents use Gemini REST API for, with concrete tasks.
★ Algorithmic Trading Bot
Run a strategy that places, cancels, and manages orders on Gemini. The agent watches /v1/book/{symbol} for liquidity, posts orders to /v1/order/new, and reconciles fills via /v1/order/status. Replaces a UI trader for high-frequency or systematic strategies.
Watch /v1/book/BTCUSD for the best bid, POST /v1/order/new with type=exchange limit, side=buy, and the calculated price; on fill, refresh balances via /v1/balances
Portfolio Reporting Across Crypto Holdings
Pull account-wide balances and notional USD values into a portfolio dashboard. The agent calls /v1/balances and /v1/notionalbalances/USD on a schedule and posts the aggregate to a finance dashboard. Eliminates manual exchange-by-exchange exports.
GET /v1/balances and /v1/notionalbalances/USD on an hourly cron, store the snapshot, and surface the totals on a portfolio page
Tax And Audit Trade History Export
Export complete trade history for tax season or an audit. The agent walks /v1/mytrades and /v1/orders/history paginated by timestamp, normalises the records, and writes them to a spreadsheet or accounting tool. Spares the team from manual CSV downloads.
POST /v1/mytrades with a symbol and timestamp range, paginate until empty, and write each fill to the destination ledger
Agent-Led Crypto Operations Through Jentic
AI agents discover Gemini through Jentic's intent search and execute trading or balance reads without implementing the HMAC-SHA384 signing flow themselves. Jentic isolates the API key and secret in its vault and produces the X-GEMINI-SIGNATURE header at execution time. Critical for an API where credential leakage is financially material.
Use Jentic search query 'place a crypto order on Gemini' to load the gemini_place_order tool and execute with symbol, side, type, and amount
Key Endpoints
28 endpoints — the gemini rest api is the trading and account interface for gemini, the regulated cryptocurrency exchange.
METHOD
PATH
DESCRIPTION
POST
/v1/order/new
Place a new trading order
POST
/v1/order/cancel
Cancel a specific order
POST
/v1/order/cancel/all
Cancel all open orders
POST
/v1/order/status
Get the status of an order
GET
/v1/book/{symbol}
Read the order book for a symbol
POST
/v1/balances
Retrieve account balances
POST
/v1/mytrades
Retrieve my trade history
POST
/v1/order/new
Place a new trading order
POST
/v1/order/cancel
Cancel a specific order
POST
/v1/order/cancel/all
Cancel all open orders
POST
/v1/order/status
Get the status of an order
GET
/v1/book/{symbol}
Read the order book for a symbol
POST
/v1/balances
Retrieve account balances
POST
/v1/mytrades
Retrieve my trade history
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Gemini API key and secret are stored encrypted in the Jentic vault. Jentic computes the X-GEMINI-SIGNATURE HMAC at execution time from the vaulted secret, so the agent never handles the signing key — material for an API that can move funds.
Intent-based discovery
Agents search by intent (e.g. 'place a crypto order on Gemini') and Jentic returns the matching operation among the 28 endpoints with its input schema, distinguishing /v1/order/new from /v1/order/status without manual disambiguation.
Time to first call
Direct Gemini integration: 1-2 days to wire HMAC-SHA384 signing, base64 payload encoding, and nonce handling. Through Jentic: under 30 minutes — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Gemini REST API through Jentic.
What authentication does the Gemini REST API use?
Gemini uses HMAC-SHA384 signing. Each authenticated request needs three headers — X-GEMINI-APIKEY, X-GEMINI-PAYLOAD (base64-encoded JSON request body), and X-GEMINI-SIGNATURE. Through Jentic the key and secret are stored encrypted in the vault and the signature is computed at execution time.
Can I place a limit order with the Gemini API?
Yes. POST /v1/order/new with type=exchange limit and the symbol, side, amount, and price fields. The response includes the assigned order_id which you can later pass to /v1/order/status or /v1/order/cancel.
How do I cancel all open orders at once?
Call POST /v1/order/cancel/all. Gemini cancels every open order under the API key's scope and returns a result list. Use /v1/order/cancel for cancelling a single order id instead.
What are the rate limits for the Gemini REST API?
Gemini's documented limits are 600 public requests per minute and 600 private requests per minute, with stricter caps on order placement bursts. Back off on HTTP 429 and consult docs.gemini.com for the current ceilings before scaling.
Can I generate a deposit address through the API?
Yes. POST /v1/deposit/{currency}/newAddress generates a new deposit address for that currency and returns the address string. Suitable for systems that rotate addresses per deposit for audit reasons.
How do I trade on Gemini through Jentic?
Install with pip install jentic, search 'place a crypto order on Gemini', load the gemini_place_order operation schema, and execute with symbol, side, type, amount, and price. Jentic computes the X-GEMINI-SIGNATURE header from the vaulted secret.
GET STARTED