THE DATA LAYER.

The product, as it ships

One API for every market's data

AsherCore is a product other people pay for and build on, not an internal module. This is its own front page: one key, one REST endpoint, one bill, across crypto, stocks and FX.

ashercore.comLIVE

The layer, running

A real call, and what comes back

This is the production candles endpoint answering a live request. One shape — time, open, high, low, close, volume — with the venue and source named in the response, for every asset class.

ashercore.com · API consoleLIVE

Why this layer exists

Everything above it reads from here

AsherCore is not a feature of the trading product — it is the layer the trading product stands on, and it is a product other people build on too. The ecosystem's rule is that a named instrument is served by that instrument's own series, and AsherCore is where that rule is kept.

What it serves

Nine things AsherCore does

Market data, streaming, normalization, funding, order books, the Asher Wire, news signals, the economic calendar, and the API that exposes all of it.

• Market data

  Candles, quotes, mids, a searchable catalog and a screener — the same request shape whether you are asking for a crypto perp, a listed equity or a currency pair.

  • Intervals 1m, 5m, 15m, 1h, 4h, 1D, 1W
  • Between 10 and 5,000 bars per request
  • A `before` unix cursor for scroll-back through history
  • An optional venue override when you need a specific book

• Streaming

  Server-sent events for live push, so an application updates instead of polling. Connections resume with Last-Event-ID, and the roughly five-minute connection ceiling is disclosed rather than discovered.

  • Stream tokens are stateless and never expire
  • AsherCore states plainly that a stream token is not a credential
  • Reconnect-and-resume is part of the contract, not a workaround

• Multi-asset normalization

  One normalized candle — time, open, high, low, close, volume — with provenance tags, across crypto, equities and FX. This is the part that makes the rest of the ecosystem possible: a chart or an indicator is written once, not once per asset class.

  • Same shape across all three asset classes
  • Provenance tags travel with the data
  • 2,500+ instruments across 5 venues as published

• Funding

  Perpetual funding is first-class data rather than something inferred downstream, exposed per instrument and through a dedicated funding radar endpoint.

  • /api/market/funding
  • /api/market/funding-radar

• Order books

  Book data through a single endpoint, for applications that need to see resting liquidity and not only the last trade.

  • /api/market/orderbook
  • Available on the Growth plan and above

• Asher Wire

  Original briefs, not a syndication feed. Every story carries its attribution and a link to the source, and AsherCore never republishes the source article — so an application built on the Wire inherits a defensible position on attribution rather than a problem.

  • Attribution fields must be preserved wherever a story is displayed
  • English and Spanish
  • /api/wire/headlines and /api/wire/article

• News signals

  A machine-readable signal attached to each story, so news can be treated as data instead of as text an application has to parse.

  • Bias: bullish, bearish, neutral or mixed
  • The assets the story moves
  • A rationale for the call
  • A per-asset rollup scored from −1 to +1

• Economic calendar

  Scheduled macro events with an impact rating, plus forecast, previous and actual values — the context that explains why a chart moved at a particular minute.

  • /api/wire/calendar

• API

  One HTTPS and JSON GET API. No SDK required — AsherCore’s own words — so anything that can make an HTTP request is already a client, and there is no library release cycle between you and the data.

  • Base URL https://ashercore.com
  • An OpenAPI 3.1 spec at /api/openapi.json
  • Authorization: Bearer core_live_… , or ?key= where a header is awkward

ashercore.com · Asher WireLIVE

How you call it

The interface, in full

There is one way in, and it is deliberately boring: an HTTP GET with a bearer token.

Also shipped

Two things you can drop straight into a page

Plans

Published pricing

AsherCore publishes four tiers. Keyless requests are capped per IP — enough to try an endpoint before you take a key, and the response headers state the cap in force.

Posture

What AsherCore is not

Go deeper

Explore AsherCore

The full endpoint reference, the OpenAPI spec and the plan details live on AsherCore's own site.