Beyond crypto: stocks, gold and FX land in the feed
Until now, CryHub was a crypto feed. As of this week it is a markets feed: 76 new USDC-quoted instruments are live across five asset classes, streaming over the exact same WebSocket and REST endpoints you already integrate.
What's included
- 50 stocks — AAPL, NVDA, TSLA, MSFT, AMZN, META and the rest of the large-cap names, plus a tail of high-interest tickers like COIN, HOOD, MSTR and PLTR.
- 9 ETFs — sector and country funds including SMH, XLE and the EW* country series.
- 8 commodities — GOLD, SILVER, COPPER, PLATINUM, PALLADIUM, BRENTOIL, CL and NATGAS.
- 4 indices — SP500, JP225, KR200 and the XYZ100 composite.
- 3 FX pairs — EUR, GBP and JPY against USDC.
Every market supports leverage — up to 50× on indices and FX, 20–25× on the majors elsewhere.
Nothing new to integrate
This is the part we care about most. The new markets use the same tick shapes, the same channel names, and the same REST envelope as every crypto pair:
GET /rest/v1/market/detail?source=s2&symbols=xyz-aapl"e=usdc&slice=1day&size=1
A detail tick for AAPL carries the same fields as one for BTC — price, change_percent, high, low, volume_quote. If your client already parses CryHub crypto data, it already parses equities. Subscribe with the xyz- symbol prefix and you're done.
Why it matters
Most teams that build with market data eventually need more than crypto — a portfolio app adds equities, a news site wants gold and oil next to BTC, a dashboard needs the S&P for context. The usual answer is a second vendor, a second auth scheme, and a normalization layer to reconcile the two. Our answer is one connection, one format, one token.
The new markets are already visible on the landing page's markets tape, and the full instrument list ships in the API docs. If your token was provisioned before this week, no changes are needed — the new symbols are live on your existing plan.