When to use this skill
When the user asks about a cryptocurrency's price in Turkish lira — spot price, 24-hour change, bid-ask spread, or volume — or wants market data from BtcTurk, Turkey's largest crypto exchange. Every pair on BtcTurk is denominated in TRY. If the user needs USD prices or global aggregates, this is the wrong skill; reach for CoinGecko or CoinMarketCap instead.
Your best first call
curl "https://api.btcturk.com/api/v2/ticker?pairSymbol=BTCTRY"
No auth. No key. The pairSymbol parameter narrows the response to one pair — omitting it returns every pair at once, which is a large payload you almost never want. Pair symbols follow the pattern {numerator}TRY (e.g. BTCTRY, ETHTRY, USDTTRY).
Key fields in the response object:
last — most recent trade price (integer in TRY; major pairs carry no decimal places)bid, ask — current best bid and ask (integers)high, low, open — 24-hour price extremes and opening pricedaily — absolute TRY change from open, not a percentage: -22526 means the price fell 22,526 liradailyPercent — relative change (e.g. -0.72)volume — 24-hour volume in the numerator asset (BTC for BTCTRY, not TRY)timestamp — milliseconds since epoch, not secondspair, numeratorSymbol, denominatorSymbol — the pair and its components
Fallbacks (when the best call isn't enough)
- Order book depth for a pair →
/api/v2/orderbook?pairSymbol=BTCTRY&limit=10 returns top N bids and asks as [price_string, amount_string] arrays. Use when the user asks about liquidity, slippage, or fill depth.
- Discovering which pairs trade on BtcTurk →
/api/v2/server/exchangeinfo returns every active symbol with tick size, minimum order values, and supported order types. Use when you need a valid pairSymbol value or want to know which altcoins are listed against TRY.
Pitfalls
- All timestamps are milliseconds, not seconds — divide by 1000 before passing to
datetime.fromtimestamp().
- Order book entries are strings (
["3038600", "0.07310053"]), not numbers. Parse explicitly before arithmetic. This is inconsistent with the ticker where last, bid, and ask arrive as integers.
/api/v2/ticker without pairSymbol returns hundreds of pair objects. Always narrow by pair.daily is an absolute TRY delta, not a percentage. A value of -22526 means the price fell 22,526 lira. Use dailyPercent for the relative change.
One-line summary for the user
I can fetch real-time crypto prices and market data from BtcTurk — all denominated in Turkish lira, no authentication required.
BtcTurk cryptocurrency exchange public API for real-time market data including tickers, order books, trades, and OHLC data. Authentication not required for these public endpoints.
SKILL.md source (frontmatter + body)
---
name: get-crypto-price-in-try
description: When the user asks about a cryptocurrency's price in Turkish lira — spot price, 24-hour change, bid-ask spread, or volume — reach for BtcTurk. All denominations are TRY, no auth required.
---
## When to use this skill
When the user asks about a cryptocurrency's price in Turkish lira — spot price, 24-hour change, bid-ask spread, or volume — or wants market data from BtcTurk, Turkey's largest crypto exchange. Every pair on BtcTurk is denominated in TRY. If the user needs USD prices or global aggregates, this is the wrong skill; reach for CoinGecko or CoinMarketCap instead.
## Your best first call
```bash
curl "https://api.btcturk.com/api/v2/ticker?pairSymbol=BTCTRY"
```
No auth. No key. The `pairSymbol` parameter narrows the response to one pair — omitting it returns every pair at once, which is a large payload you almost never want. Pair symbols follow the pattern `{numerator}TRY` (e.g. `BTCTRY`, `ETHTRY`, `USDTTRY`).
Key fields in the response object:
- `last` — most recent trade price (integer in TRY; major pairs carry no decimal places)
- `bid`, `ask` — current best bid and ask (integers)
- `high`, `low`, `open` — 24-hour price extremes and opening price
- `daily` — absolute TRY change from open, not a percentage: -22526 means the price fell 22,526 lira
- `dailyPercent` — relative change (e.g. -0.72)
- `volume` — 24-hour volume in the numerator asset (BTC for BTCTRY, not TRY)
- `timestamp` — milliseconds since epoch, not seconds
- `pair`, `numeratorSymbol`, `denominatorSymbol` — the pair and its components
## Fallbacks (when the best call isn't enough)
- **Order book depth for a pair** → `/api/v2/orderbook?pairSymbol=BTCTRY&limit=10` returns top N bids and asks as `[price_string, amount_string]` arrays. Use when the user asks about liquidity, slippage, or fill depth.
- **Discovering which pairs trade on BtcTurk** → `/api/v2/server/exchangeinfo` returns every active symbol with tick size, minimum order values, and supported order types. Use when you need a valid `pairSymbol` value or want to know which altcoins are listed against TRY.
## Pitfalls
- All timestamps are **milliseconds**, not seconds — divide by 1000 before passing to `datetime.fromtimestamp()`.
- Order book entries are **strings** (`["3038600", "0.07310053"]`), not numbers. Parse explicitly before arithmetic. This is inconsistent with the ticker where `last`, `bid`, and `ask` arrive as integers.
- `/api/v2/ticker` without `pairSymbol` returns hundreds of pair objects. Always narrow by pair.
- `daily` is an absolute TRY delta, not a percentage. A value of -22526 means the price fell 22,526 lira. Use `dailyPercent` for the relative change.
## One-line summary for the user
I can fetch real-time crypto prices and market data from BtcTurk — all denominated in Turkish lira, no authentication required.