When to use this skill
When the user asks what a specific crypto pair is trading at on Blockchain.com — current price, 24-hour movement, or recent volume — reach for /tickers/{symbol}. The data reflects Blockchain.com's own order books exclusively, not a cross-exchange aggregate, and volume is thin on most pairs. For consensus market prices or high-volume data, this is the wrong skill — use a multi-venue aggregator like CoinGecko instead.
Your best first call
curl "https://api.blockchain.com/v3/exchange/tickers/ETH-USD"
No auth. No key. Symbols follow BASE-COUNTER convention: BTC-USD, ETH-EUR, XLM-BTC.
{
"symbol": "BTC-USD",
"price_24h": 72000.0,
"volume_24h": 0.07018205,
"last_trade_price": 70544.63
}
Use last_trade_price when the user asks what a pair is "trading at" — that's the most recent executed trade. price_24h is the reference price at the start of the 24-hour window (not a high, not an average), so the gap between the two tells you the direction of the day's move. volume_24h is in base-currency units — 0.07 BTC is roughly $5,000, illustrating how shallow these books are.
Fallbacks (when the best call isn't enough)
- Need to verify a pair is actually tradeable before quoting a price →
curl "https://api.blockchain.com/v3/exchange/symbols/ETH-USD" and check status. Many listed pairs return all-zero tickers because their status is "close", not "open".
- Need spread or liquidity depth, not just last price →
/l2/{symbol} returns bids and asks aggregated by price level. The px, qty, num fields give price, quantity, and order count at each level — useful for answering "how tight is the spread?" or "how much can I fill at this price?"
Pitfalls
price_24h is not "the current price" — it's the 24h window's opening reference. Always use last_trade_price when answering "what's X trading at?"./tickers without a symbol returns the full list — over a hundred entries, most with all-zero values for inactive pairs. Always append the symbol: /tickers/{symbol}.- This is a low-volume venue. A BTC
volume_24h of 0.07 (~$5k) is typical here; on Binance, that same pair does billions daily. Quote the source explicitly so the user doesn't mistake these prices for consensus market data.
One-line summary for the user
I can fetch the current trading price and 24-hour stats for a crypto pair on Blockchain.com — but this is a low-volume venue, so prices reflect their own order books, not the broader market.
SKILL.md source (frontmatter + body)
---
name: get-blockchain-com-trading-pair-price
description: When the user asks what a crypto pair is trading at on Blockchain.com — current price, 24-hour movement, volume, or spread — reach for the Blockchain.com Exchange API. Unauthenticated. Reflects Blockchain.com's own order books, not a market-wide aggregate.
---
## When to use this skill
When the user asks what a specific crypto pair is trading at on Blockchain.com — current price, 24-hour movement, or recent volume — reach for `/tickers/{symbol}`. The data reflects Blockchain.com's own order books exclusively, not a cross-exchange aggregate, and volume is thin on most pairs. For consensus market prices or high-volume data, this is the wrong skill — use a multi-venue aggregator like CoinGecko instead.
## Your best first call
```bash
curl "https://api.blockchain.com/v3/exchange/tickers/ETH-USD"
```
No auth. No key. Symbols follow `BASE-COUNTER` convention: `BTC-USD`, `ETH-EUR`, `XLM-BTC`.
```json
{
"symbol": "BTC-USD",
"price_24h": 72000.0,
"volume_24h": 0.07018205,
"last_trade_price": 70544.63
}
```
Use `last_trade_price` when the user asks what a pair is "trading at" — that's the most recent executed trade. `price_24h` is the reference price at the start of the 24-hour window (not a high, not an average), so the gap between the two tells you the direction of the day's move. `volume_24h` is in base-currency units — 0.07 BTC is roughly $5,000, illustrating how shallow these books are.
## Fallbacks (when the best call isn't enough)
- **Need to verify a pair is actually tradeable before quoting a price** → `curl "https://api.blockchain.com/v3/exchange/symbols/ETH-USD"` and check `status`. Many listed pairs return all-zero tickers because their `status` is `"close"`, not `"open"`.
- **Need spread or liquidity depth, not just last price** → `/l2/{symbol}` returns bids and asks aggregated by price level. The `px`, `qty`, `num` fields give price, quantity, and order count at each level — useful for answering "how tight is the spread?" or "how much can I fill at this price?"
## Pitfalls
- `price_24h` is not "the current price" — it's the 24h window's opening reference. Always use `last_trade_price` when answering "what's X trading at?".
- `/tickers` without a symbol returns the full list — over a hundred entries, most with all-zero values for inactive pairs. Always append the symbol: `/tickers/{symbol}`.
- This is a low-volume venue. A BTC `volume_24h` of 0.07 (~$5k) is typical here; on Binance, that same pair does billions daily. Quote the source explicitly so the user doesn't mistake these prices for consensus market data.
## One-line summary for the user
I can fetch the current trading price and 24-hour stats for a crypto pair on Blockchain.com — but this is a low-volume venue, so prices reflect their own order books, not the broader market.