Skip to content
GridRouterhome

Search

Search providers, capabilities and pages

Security

Your vendor keys and customer data pass through us, so the design starts from keeping both out of reach.

Controls

  • Vault-encrypted keys

    Vendor keys are envelope-encrypted per workspace and only decrypted inside the call path. They never reach an agent's machine.

  • Scoped keys and tokens

    API keys and agent tokens are limited by capability, provider, spend cap and expiry.

  • Audit log

    Every call records who made it, with which key, to which provider, what it cost and the outcome.

  • Sealed call bodies

    Stored bodies are redacted, then encrypted with a per-workspace key. Viewing one is audited, and you can turn capture off.

Key custody

Each workspace's vendor keys are encrypted with a per-workspace data key, itself wrapped by a key held in a managed KMS. Keys are decrypted only in the worker that makes the provider call and are never returned by any API.

Tokens

API keys and agent tokens are hashed at rest, shown once, scoped to capabilities and providers, capped by spend and optionally set to expire.

Reporting a vulnerability

Email security@gridrouter.io or use GitHub private vulnerability reporting. Do not open a public issue. Include what you found, how to reproduce it and the impact you expect. Redact real customer data, and never send a live API key, only its prefix (grid_live_XXXXXXXX).

Response times

  • Acknowledgement within 2 business days.
  • First assessment within 5 business days, with updates until the fix ships.
  • Critical issues fixed or mitigated within 7 days.

Scope

In scope: the API and MCP server, OAuth and consent flows, API key handling, billing and credit integrity, the dashboard and this site.

Out of scope: denial of service by volume, social engineering, physical attacks, findings in third-party vendors we relay to (report those to the vendor), and missing headers without an exploit.

Safe harbor

Good-faith research that follows this policy is authorized: test only against accounts you own, stop at the minimum needed to show impact, never access or keep other customers' data, and give us reasonable time to fix before disclosure. We will not pursue legal action for such research.

If you leaked a key

Revoke it immediately in the dashboard or with DELETE /v1/keys/{id}, and rotate with POST /v1/keys/{id}/rotate. Keep a backup key so revoking the primary never causes downtime.

Machine-readable contact: security.txt.