01 · Naming
Which token is which company
No list connects SPCXon to SpaceX. A program has to guess from the ticker, and tickers collide.
Guessanswered by companies.key
For machines
The same data, without the page around it
Everything the terminal shows is available as JSON. No key, no sign-up, no rate limit worth mentioning. If you are building an agent that touches tokenized equities on BNB Chain, this is the layer you were going to have to build yourself.
- 73
- Companies mapped
- 165
- Tokens
- 19
- With all three issuers
- 0
- API keys required
Endpoints
- GET/api/v1/companies?confidence=FIRM&limit=50
Every company with competing tokens, resolved to one price.
canonicalPriceUsd is null when no pool is deep enough. That is a real answer, not a missing field.
- GET/api/v1/companies/{key}
One company: every token, its mechanic, its multiplier, and the corporate-action record.
Use the key from the list endpoint, or the ticker.
- GET/api/v1/companies/{key}/wrappers
Just the token-to-company mapping, with the contract method names to read each mechanic.
This mapping does not exist anywhere else.
- GET/api/v1/tape?since={unix_ms}&confidence=PROVEN
Corporate actions as detected, typed and confidence-scored.
Filter to PROVEN when your code cannot tolerate an inference.
- GET/api/v1/divergence?min_bps=25
Companies whose own tokens disagree on price, across tradeable pools only.
Gaps between untradeable pools are excluded rather than reported.
Read the confidence field
Every price and every event carries one. It is the difference between a number you can act on and a number that happens to exist. Most of this market is the second kind, and no other source will tell you which is which.
- FIRM
- A pool over $100,000 stands behind this price.
- THIN
- There is a price, but only small pools behind it.
- UNPRICED
- No pool is deep enough. The price field is null.
- PROVEN
- The contract’s own counter matches the declared calendar.
- PARTIAL
- The counter and the calendar disagree on how many actions happened.
- INFERRED
- The issuer publishes nothing on-chain. Read from the calendar only.
MCP server
The same tools inside Claude Code, Cursor, or anything else that speaks Model Context Protocol. Add it to your MCP config:
{
"mcpServers": {
"tape": {
"command": "npx",
"args": ["-y", "@tape/mcp"],
"env": { "TAPE_API_URL": "https://tape.fi" }
}
}
}Exposes tape_companies, tape_company, tape_divergence and tape_feed. The endpoints above, as tools. Source is in mcp/.
Try it now
curl -s tape.fi/api/v1/divergence?min_bps=25 | jq
curl -s tape.fi/api/v1/companies/nvidia | jq '.wrappers[]
| {symbol, priceUsd, liquidityUsd, multiplier}'Why the fields exist
Four things software cannot guess.
Each of these is a gap a person fills by judgement and a program cannot. Every field in the responses above exists to close one of them.
02 · Units
Whether two prices should match
One token grows your balance, another grows its price. Comparing them gives the wrong answer with no warning.
Mismatchanswered by wrappers.mechanic
03 · Meaning
Whether a change was a dividend or a split
Both make your token count move. One is income, the other is not. Get it backwards and the books are wrong.
Ambiguousanswered by tape.type
04 · Timing
Whether it is safe to act right now
A token mid corporate action prices strangely for hours. Nothing tells you to wait.
Silentanswered by tape.detectedAt
TAPE answers all four. The endpoints above are the answers, and the terminal is the same data with a page around it.
What this API will not do
It will not execute a trade, hold a balance, or tell you what something is worth in the future. TAPE reads public data and publishes what it read. Everything on the roadmap that involves moving value is behind a planned tab, and stays there until it is real.