BixelDocs

Overview

Verified private company and market data with receipts. Current facts, dated change history, and cryptographic proof, over REST and MCP.

Your first call needs no key and no signup:

curl https://api.bixel.com/v1/companies/pinecone.io

That returns the company's full current state — pricing, features, security posture, positioning, stack, hiring, reliability, funding, location, and legal terms — every fact carrying its provenance, an as_of date, and the source page it came from. Most facts point at a stored capture you can verify cryptographically. The Quickstart takes you from this call to an agent with all 18 tools in about three minutes.

The ways in:

SurfaceAuthWhat you get
Open RESTnoneCurrent state per company, tracked-tier liveness for millions more, masked change feed, proof bundles
Keyed RESTfree API keyValues and summaries unmasked for the last 90 days of history
Pro RESTPro keyThe full archive — history depth back to the earliest event
MCP serverfree accountAll 18 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. A ready-made Postman collection is generated from the live contract.

Where to start

Identity

Every company Bixel holds has a permanent Bixel ID (bxc_ + 12 characters) and a kind: a brand (the operating presence people look up by its name or domain) or a legal_entity (a registered company on an authoritative register). GET /v1/resolve turns a name, a domain or URL, an email, a LinkedIn or Crunchbase URL, an LEI or a Wikidata QID into that ID, with an evidence tier and the reason for any non-answer. Identity is free and unmetered on every plan; the identity guide has the rules, the result types and the attribution block.

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.

On this page