Namebeam
NAMEBEAM
Real numbers. No hype. Receipts.
Receipts Index

Receipts Index: API and MCP docs

Namebeam, a Carter Enterprise property. This is the first leg. The Receipts Index is the Namebeam record of which US local businesses AI engines name for fixed buyer questions: one dated row per check, engine and UTC date. This page covers the Receipts Index API at api.receiptsindex.com and its MCP server. No account, sign-in or API key is needed for anything on this page.

Add the remote MCP to Claude or another MCP client by pasting https://api.receiptsindex.com/mcp as a custom connector, no key needed, or run npx receipts-index-mcp.

Free routes

All free routes are GET requests to https://api.receiptsindex.com.

RouteReturns
/v1/indexRow ids and UTC dates, with no row content. start (1 or more) and limit (1 to 500) page through the ids.
/v1/sampleOne real row, labeled as a sample, with its row id and the paid route and price for that row.
/v1/manifestRoutes, prices, fields and payment terms.
/.well-known/x402The concrete paid URLs, for x402 directories.
/openapi.jsonAn OpenAPI 3.1 description of every route, with x402 prices.
curl "https://api.receiptsindex.com/v1/index?start=1&limit=5"
curl https://api.receiptsindex.com/v1/sample

Paid routes

Paid routes use x402: a GET without payment answers 402 with the exact terms, and an x402 client pays in USDC on Base and repeats the request. Row and day files come back as CSV with a header line. A row id or date that does not exist returns 404 and is not charged. Prices are as the API lists them; /v1/manifest is the current source.

RoutePrice (USDC)Returns
/v1/row/{row_id}0.27One CSV row
/v1/day/{YYYY-MM-DD}1.81All rows for one UTC date
/v1/corpus540The full corpus as one CSV, per call
/v1/feed/founding-partner200The corpus feed, listed by the API at 200 USDC per month

Use /v1/index to pick a valid row id or date and /v1/sample to see the row shape before you pay. The data records what the named engines answered on the dates shown. It makes no claim about why an engine answered as it did.

MCP server: three read-only tools

The server gives an AI assistant the free side of the API. It never pays, never signs anything and holds no wallet or key. To buy paid rows, use an x402 client against the route.

ToolCostWhat it does
receipts_indexFreeCalls /v1/index. Lists row ids and UTC dates, the row count, the first and last dates and the dates that have rows. Optional start and limit.
receipts_sampleFreeCalls /v1/sample. Returns one real row labeled as a sample, as fields and as CSV.
receipts_pricingFreeLists the paid routes with their USDC prices and payment terms, read from /.well-known/x402 and /v1/manifest.

Connect to the MCP server

Remote URL. Add this URL to any client that takes a remote MCP server, such as a Claude custom connector. It is a stateless Streamable HTTP endpoint with no sign-in and no key.

https://api.receiptsindex.com/mcp

npm package. The package receipts-index-mcp runs on your computer over stdio and needs Node.js 20.20 or newer (or 22.22 or newer). For Claude Desktop or any client that reads an mcpServers block:

{
  "mcpServers": {
    "receipts-index": {
      "command": "npx",
      "args": ["-y", "receipts-index-mcp"]
    }
  }
}

For Claude Code:

claude mcp add receipts-index -- npx -y receipts-index-mcp

The npm package sends anonymous usage events to PostHog unless you turn that off with RECEIPTS_INDEX_TELEMETRY=0 or DO_NOT_TRACK=1. The remote endpoint sends none. Details are on the privacy page.

Example prompts

Source and contact. The Receipts Index API and MCP server are published by Carter Enterprise LLC. MCP server source and README: github.com/mrcrtr1979-droid/namebeam-visibility-index. Questions: terry@namebeam.ai. Privacy: namebeam.ai/privacy. Namebeam is an educational and marketing service and does not guarantee rankings, traffic, or revenue.