Unified API and routing
One API for every go-to-market data provider
See it working
What you get
Capability-first calls
POST /v1/run/people.email.find and get the same input and output shape whichever provider answers.
Fallbacks that stop at the first hit
Misses, provider errors and providers you have no key for fall through to the next one. Failed and missed attempts are free.
Load balancing by price and health
With no order set, providers with recent errors go last and the rest are drawn by price. Open circuit breakers are skipped.
Provider preferences per call or preset
order, only, ignore, sort, max price, preferred latency and data policy, in the request body or a saved preset.
Every attempt in the response
Outcome, cost, latency and error code for each provider tried, and one call log row per attempt.
Direct calls when you want them
POST /v1/call/{provider}/{endpoint} runs exactly one endpoint and never routes.
How it works
Add your vendor keys once. They're sealed in your workspace's vault.
Call a capability with one GridRouter API key, optionally with provider preferences.
Read the answer in one schema, with every attempt, its cost and its latency.
curl https://api.gridrouter.io/v1/run/people.email.find \
-H "Authorization: Bearer $GRID_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"input": { "first_name": "Ada", "last_name": "Lovelace", "domain": "example.com" },
"provider": { "order": ["prospeo", "hunter"], "allow_fallbacks": true },
"fields": ["email", "confidence"],
"stop_when": "hit"
}'Questions
What's the difference between /v1/run and /v1/call?
/v1/call/{provider}/{endpoint} runs one endpoint and never routes. /v1/run/{capability} plans the providers that serve a capability and tries them in turn until one hits.
Do I pay for failed or missed attempts?
No. GridRouter never charges for a miss or a failed attempt. On your own vendor keys GridRouter charges nothing at all; the provider bills your account by its own rules.
Can I pin the order or turn fallbacks off?
Yes. Send provider.order with the providers you want first, and "allow_fallbacks": false to try only those.
More in GridRouter
- MCP serverPoint any MCP client at one URL and your agent can search the catalog, get a quote and call any capability, inside the budget you set.
- WaterfallsPut providers in order, choose how fast and how far to go, and publish the result as a versioned endpoint your code and agents can call.
- Logs and log explorerSee exactly what every provider returned, what it cost and how long it took, from the dashboard, the API, the CLI or your agent.
- Vendor billing verificationGridRouter checks what each provider charged against what its own pricing says, call by call, and hands you the mismatches as a CSV.
- Private cacheStop paying twice for the same person or company. Every answer is cached for your workspace only and reused until its fields expire.
- Alerts, webhooks and integrationsHear about a failing provider, a runaway agent or a wrong charge in seconds, in the tools your team already watches.
- Security and governanceYour vendor keys, data and spend stay inside your workspace, and every change is on the record.
- Provider catalog and docsFind the right provider for a capability, see how it bills and what its API looks like, before you sign a contract.