Four questions need one; everything that draws the pages does not. Send it as a bearer token, and keep it on your own server — a key in a browser is a key anyone can read.

$ curl -H "Authorization: Bearer pc_live_…" \
       https://priorcase.com/v1/search?asset=BTC&scale=15m&k=8

Keys are given out by hand while this is young. Ask at [email protected], and say what you are building — it is read by a person, not a form.

An MCP server at /mcp, over HTTP. The same key, as the bearer token; the tools reach the endpoints beside them, so an agent and a program are answered by one path.

• find_analogsGET /v1/searchThe past moments whose price path most resembles a given one, each with what the market was then and what followed. Nothing given means now.
• market_stateGET /v1/moment/{at}What the market was at one moment — returns over 1h to 30d, the day's high, low and volume, how wild it was against its month — and what followed.
• query_historyGET /v1/whenEvery past moment a condition in words was true. The reading of the condition comes back with the answer, so you can see what it was understood to mean.
• outcomesGET /v1/pathsThe price path around moments, as percent from the close at each, so paths of different sizes lie on each other. Offsets are minutes: negative before, positive after.

{ "mcpServers": {
    "priorcase": {
      "type": "http",
      "url": "https://priorcase.com/mcp/",
      "headers": { "Authorization": "Bearer pc_live_…" }
    } } }

• GET /v1/after/{topic}?asset=Every event of a kind, each with its own before and after. Never averaged.
• GET /v1/topics?q=…The kinds of event, found from a question such as “after rate cuts”.
• GET /v1/events?q=&kind=&since=&until=Events already known, most recent first, each with the time it became public and its source.
• GET /v1/events/upcoming?days=&limit=The releases the calendar holds ahead: their kind and time, never what they will say.
• GET /v1/news?since=&until=&q=Government releases in a window, at the time each became known.
• GET /v1/prices?step=5m|15m|30m|1h|4h|1d&since=&until=Closes on a grid.
• GET /v1/assetsThe assets in the data: symbol, name, kind, and the range each covers.
• GET /v1/spell?q=…The words of a question set right against the ones the search knows.
• GET /v1/statusThe data's range, and whether it is sample data.

$ curl https://priorcase.com/v1/after/halving

{ "topic": { "slug": "halving", "label": "halvings", "count": 2 },
  "items": [ { "event": { "name": "Bitcoin's fourth halving", "known_at": "2024-04-20T00:10:00Z", … },
               "moment": { "time": "2024-04-20T00:10:00Z", "then": { … }, "after": { … } } }, … ],
  "disclaimer": "Past similarity does not guarantee future outcomes." }

• Before holds only what was knowable at the moment. After starts at the moment.
• A past moment is returned only once its 32 hours after have closed before the query.
• A window must cover the time it claims. One drawn across a stretch the market was shut is refused, on both sides of the search.
• No direction, probability or action fields. Every response carries the disclaimer.
• Times are UTC, ISO 8601. Events carry their source.

Nothing yet — there is no checkout, and every key in use is free. What a key may spend is counted against its plan all the same, so the allowance you would have is the allowance you have. The plans say what each carries.

Counted in answers, not calls: a reply costs what it draws, so ten moments is one answer and fifty is five. The count follows the k or limit in your own query string, and a call past the allowance or the rate comes back 429 saying which of the two it was and what had been spent.

What yours has spent is on your account page.