Bixel API and MCP
Verified private company and market data with receipts. Current facts, dated change history, and cryptographic proof, over REST and MCP.
Bixel tracks what companies actually publish: pricing, features, security posture, positioning, stack, hiring, reliability, funding, location, and legal terms. Every fact carries its provenance, an as_of date, and the source it came from. Most facts point at a stored capture you can verify cryptographically.
The ways in:
| Surface | Auth | What you get |
|---|---|---|
| Open REST | none | Current state per company, masked change feed, proof bundles |
| Keyed REST | free API key | Values and summaries unmasked for the last 90 days of history |
| Pro REST | Pro key | The full archive — history depth back to the earliest event |
| MCP server | free account | All 12 tools in your agent, over OAuth sign-in or an API key |
The base URL is https://api.bixel.com/v1. The MCP endpoint is https://api.bixel.com/mcp.
Where to start
- Quickstart makes your first call in under a minute, keyless.
- Authentication, keys and tiers covers keys, OAuth, quotas, and metering.
- The data model explains dimensions, provenance, and the change feed's guarantees.
- Connect over MCP wires Bixel into Claude, Cursor, or any MCP client.
- How verification works shows what a proof bundle attests and how to check one offline.
- Errors lists every problem code and what to do about it.
- API reference is generated from the live OpenAPI contract.
The contract
https://api.bixel.com/v1/openapi.json is the normative contract, served by the deployed API itself. The reference section renders from the same document, so it cannot drift from what the API does.