Exa Incident Containment Runbook

Overview

Contain Exa credential, data, cost, capacity, or correctness incidents while preserving safe evidence and vendor request IDs. Treat credentials, queries, retrieved content, generated output, spend, and destructive state as separately governed boundaries.

Prerequisites

• The target repository, environment, Exa team, product surface, and accountable owner.
• The workload's data classification, latency and freshness promise, cost ceiling, and retention policy.
• Current first-party documentation plus credentials only for a narrowly approved live check.

Current Contract

Containment choices differ by incident: revoke or rotate a key, disable a caller, pause or delete Monitors, stop or cancel Agent runs, cancel Batches, quarantine webhook processing, or switch to a tested fallback. Deletion and cancellation are destructive and require exact targets.

Authentication

For normal REST work, inject EXA_API_KEY from an approved server-side secret manager and send it only as Authorization: Bearer to the configured first-party Exa API host. Team Management service keys, hosted MCP OAuth or enterprise managed authorization, and payment-protocol calls are separate trust models. Never print, commit, place in a URL, or expose a credential to an untrusted client.