Skip to content
GridRouterhome

Search

Search providers, capabilities and pages

Docs

GridRouter docs

One API, one key and an MCP server for every go-to-market data provider, with quality scores measured on real traffic.

GridRouter puts email finders, enrichment, phone, signals and the rest of the go-to-market data stack behind one REST API, one API key and one MCP server. Every provider endpoint is described in the same catalog: the same input shape, the same normalized output fields, a price and a quality score measured on real calls.

Launch: everything runs on your own vendor keys

Every workspace is on the Free plan. Calls run on the vendor keys you add (BYOK), GridRouter never charges for them, and nothing is sold yet. Paid plans and managed vendor accounts are coming soon.

Start here

How it fits together

  • Capabilities and endpoints. An endpoint is one provider's API call (hunter/email.find). A capability is the task it performs (people.email.find), shared by every provider that can do it.
  • /v1/call and /v1/run. call runs exactly the endpoint you name. run takes a capability and tries providers in order until one finds the answer.
  • Waterfalls save a provider order, stop rules and a per-field merge as your own endpoint.
  • Execution options control timeouts, cost caps, cache and logging per request, key, preset or workspace.
  • Logs record every call, stream live and say whether the provider billed it correctly.

For agents

Every page is also Markdown: add .md to its URL, or send Accept: text/markdown. The index is at /llms.txt and every written page in one file at /llms-full.txt. The OpenAPI document is at https://api.gridrouter.io/openapi.json.