Skip to content
GridRouterhome

Search

Search providers, capabilities and pages

Every call logged, searchable and live

See exactly what every provider returned, what it cost and how long it took, from the dashboard, the API, the CLI or your agent.

See it working

Three days of callsSimulationOpen in the demo

Real catalog providers. Calls, results, costs and performance are simulated. No provider is contacted.

Calls over time720 calls, 90-minute buckets
  • Hit553
  • Miss152
  • Failed15
Calls per bucket by outcome
Bucket (UTC)HitMissFailed
Sep 27, 15:58 UTC1663
Sep 27, 17:28 UTC2181
Sep 27, 18:58 UTC1940
Sep 27, 20:28 UTC1240
Sep 27, 21:58 UTC1570
Sep 27, 23:28 UTC700
Sep 28, 00:58 UTC520
Sep 28, 02:28 UTC900
Sep 28, 03:58 UTC900
Sep 28, 05:28 UTC710
Sep 28, 06:58 UTC601
Sep 28, 08:28 UTC800
Sep 28, 09:58 UTC910
Sep 28, 11:28 UTC1030
Sep 28, 12:58 UTC2670
Sep 28, 14:28 UTC2540
Sep 28, 15:58 UTC2290
Sep 28, 17:28 UTC1530
Sep 28, 18:58 UTC1520
Sep 28, 20:28 UTC1730
Sep 28, 21:58 UTC1720
Sep 28, 23:28 UTC210
Sep 29, 00:58 UTC820
Sep 29, 02:28 UTC320
Sep 29, 03:58 UTC320
Sep 29, 05:28 UTC330
Sep 29, 06:58 UTC620
Sep 29, 08:28 UTC421
Sep 29, 09:58 UTC921
Sep 29, 11:28 UTC1110
Sep 29, 12:58 UTC1830
Sep 29, 14:28 UTC1440
Sep 29, 15:58 UTC1671
Sep 29, 17:28 UTC2441
Sep 29, 18:58 UTC1550
Sep 29, 20:28 UTC1442
Sep 29, 21:58 UTC1571
Sep 29, 23:28 UTC741
Sep 30, 00:58 UTC820
Sep 30, 02:28 UTC510
Sep 30, 03:58 UTC611
Sep 30, 05:28 UTC930
Sep 30, 06:58 UTC720
Sep 30, 08:28 UTC1010
Sep 30, 09:58 UTC600
Sep 30, 11:28 UTC870
Sep 30, 12:58 UTC1671
Sep 30, 14:28 UTC1670
TimeEndpointErrorStatusLatency
Sep 30, 13:47 UTCleadmagic/email.findinvalid_request4001.3 s
Sep 30, 04:20 UTCleadmagic/job-change.detectinvalid_request4001.5 s
Sep 30, 00:12 UTChunter/email.findupstream_timeout50415.0 s
Sep 29, 23:00 UTCprospeo/email.findupstream_error5021.1 s
Sep 29, 21:35 UTCprospeo/email.findupstream_error5021.0 s
Hits, misses and failures over time from the call log, and the newest failed calls. In the demo the same data opens in the full log explorer.

What you get

  • 360 days of call logs

    Every call and attempt with redacted, encrypted request and response bodies, kept for 360 days.

  • One query language

    provider:hunter status:>=400 -capability:email.find latency:>2000 works in /logs and GET /v1/logs.

  • Right-click exploration

    Filter to a value, exclude it, group by it or jump to the calls around it, from any cell or facet.

  • Live tail

    New calls stream in as they happen, in the dashboard, over SSE or WebSocket, or with grid logs tail.

  • Saved views and pins

    Save a query with its columns, share it with your workspace, pin calls to keep them on top.

  • Export and replay

    Export up to 10,000 rows as CSV or NDJSON, or copy any call as a cURL command without its secret.

How it works

  1. Make calls with the API, SDK or MCP; each one is logged in about a second.

  2. Search, filter and group in /logs, or right-click any value to drill in.

  3. Tail new calls live, or query the same log from the API.

GET /v1/logs/live
curl -N "https://api.gridrouter.io/v1/logs/live?format=sse&kinds=call&status=error" \
  -H "Authorization: Bearer $GRID_API_KEY"

Questions

How long are logs kept?

Every call is stored for 360 days. On the Free plan the last 30 days are readable; longer read windows come with paid plans.

Are request and response bodies stored?

Yes, redacted and encrypted, and never with your vendor credentials. Set data_policy.zdr on a call to skip storing its bodies.

Can I send logs to my own tools?

Log drains stream calls to a webhook, Datadog, Axiom, S3, GCS or R2. They come with paid plans.

Try it on your own data

Free while we launch. Bring your vendor keys; no card needed.