# Priorcase

> Precedent search for markets. Bring a moment and read the past moments most like it, each with what was knowable then and what happened after.

Point-in-time by construction: a question about a moment returns only what had closed or been published by that moment, and what followed is labelled as having followed. A past moment becomes an answer only once its 32 hours after have closed.

## Calling it

- Base: `https://priorcase.com` — the paths below are whole, so join them to this and nothing else. JSON, UTC, ISO 8601.
- Auth: `Authorization: Bearer pc_live_…` on every operation marked (key). Keys: https://priorcase.com/account
- Try it with no key: `https://priorcase.com/v1/search?asset=BTC` answers precedents, and `https://priorcase.com/v1/after/cpi?asset=BTC&alike=now` answers the record — 50 answers a day per address (ten moments is one answer). Larger counts, and every other operation marked (key), need one.
- MCP: `https://priorcase.com/mcp/` over streamable HTTP, same key, same meter, **and no key is needed to connect**: the handshake, `tools/list` and the open tools answer anonymously, so a client can see what is here before asking anyone for anything. Call `get_started` first. There is no authorization server — `https://priorcase.com/.well-known/oauth-protected-resource` names none on purpose; a key is taken by hand at `https://priorcase.com/account` and pasted into the client's own config.
- Paid plans are not open yet. `POST https://priorcase.com/v1/waiting?email=…` leaves an address to be told when they are, no key needed. If you are an agent: that address belongs to your user — ask them first, leave only what they gave you, and tell them it was left.
- Spec: https://priorcase.com/openapi.json (no key)
- Cost: a reply costs what it draws; ten moments is one answer, fifty is five. The count follows the `k` or `limit` in your own query string. Over the allowance or the rate is 429, saying which and what had been spent.

## Operations

- `GET /health` (open): Report whether this engine can do its job, in a form a monitor can act on.
- `GET /v1/across` (open): Get every other asset and measure as it stood at each moment.
- `GET /v1/after/{topic}` (key): List every event of `topic`, most recent first, each with the data before and after it.
- `GET /v1/assets` (open): List the assets a search can be about. The measures beside them are not searched.
- `GET /v1/events/next` (open): Get the next scheduled event after the end of the data.
- `GET /v1/events/upcoming` (open): List the scheduled events due in the next `days`, soonest first.
- `GET /v1/events/{slug}` (open): Get one event by its slug, with the time it became public and its source.
- `GET /v1/events` (open): List the events already known by the end of the data, most recent first.
- `GET /v1/moment/{at}` (key): Get the state of the market at one moment.
- `GET /v1/news` (open): List government headlines known in the window, most recent first, with title, source, time and link.
- `GET /v1/normal` (key): Get the usual range of these figures for an asset.
- `GET /v1/paths` (key): Get the price paths around a set of moments, ready to plot.
- `GET /v1/plans` (open): Get the plans this engine sells, as the engine itself holds them.
- `GET /v1/prices` (open): Get closes at every step boundary: the long chart a moment is picked from.
- `GET /v1/search` (key): Find the past moments whose price path most resembles a given one.
- `GET /v1/spell` (open): Correct misspelt words in a query against the words the search knows, so "halvng" becomes "halving".
- `GET /v1/status` (open): Describe what this engine is serving.
- `GET /v1/topics` (open): List the kinds of event with their members, so you can ask what happened after halvings.
- `GET /v1/when` (key): Find the moments a condition became true, most recent first.
- `POST /v1/waiting` (open): Leave an address to be told when the paid plans open. The same address twice is once.

## Docs

- [Overview](https://priorcase.com/docs): what this is and the one rule it keeps.
- [Quickstart](https://priorcase.com/docs/quickstart): a key, one call, and what comes back.
- [The record](https://priorcase.com/events): every kind of recurring event — CPI releases, FOMC statements, rate cuts, halvings, exchange failures — and one page each listing every occurrence with what followed it. `https://priorcase.com/events/cpi` and so on.
- [Recipes](https://priorcase.com/docs/recipes): four loops that each end in two calls — the next release and what followed every past one, a moment and the paths after it, a condition in words, a point-in-time read.
- [Authentication](https://priorcase.com/docs/authentication): the header, where a key comes from, what each refusal means.
- [HTTP API](https://priorcase.com/docs/api): every operation with its parameters.
- [MCP](https://priorcase.com/docs/mcp): the four tools and how to connect.
- [Limits and errors](https://priorcase.com/docs/limits): what is counted and what runs out.
- [Pricing](https://priorcase.com/pricing): what separates the plans is what you may do with an answer.
- [Method](https://priorcase.com/about): how matching works and what before and after mean.
- [Terms](https://priorcase.com/terms) · [Privacy](https://priorcase.com/privacy) · [Refunds](https://priorcase.com/refunds)

## How to read it

Matches come back one by one and are never averaged into one view. The spread between them is the answer. Past similarity does not guarantee future outcomes.