exa-incident-runbook

name	exa-incident-runbook
description	Execute Exa incident response with triage, mitigation, and postmortem procedures. Use when responding to Exa-related outages, investigating errors, or running post-incident reviews for Exa integration failures. Trigger with phrases like "exa incident", "exa outage", "exa down", "exa on-call", "exa emergency", "exa broken".
allowed-tools	Read, Grep, Bash(kubectl:*), Bash(curl:*)
version	1.11.0
license	MIT
author	Jeremy Longshore <[e-mail]>
tags	["saas","exa","incident-response"]
compatibility	Designed for Claude Code, also compatible with Codex and OpenClaw

Exa Incident Runbook

Overview

Rapid incident response procedures for Exa search API issues. Exa errors include a requestId field for support escalation. Default rate limit is 10 QPS. Contact [e-mail] for urgent production issues.

Severity Levels

Level	Definition	Response Time	Example
P1	All Exa calls failing	< 15 min	401/500 on every request
P2	Degraded performance	< 1 hour	High latency, partial failures
P3	Minor impact	< 4 hours	Empty results, content fetch failures
P4	No user impact	Next business day	Monitoring gaps

Quick Triage (Run First)

set -euo pipefail
echo "=== Exa Triage ==="

# 1. Test API connectivity
echo -n "API Status: "
HTTP_CODE=$(curl -s -o /tmp/exa-triage.json -w "%{http_code}" \
  -X POST https://api.exa.ai/search \
  -H "x-api-key: $EXA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query":"triage test","numResults":1}')
echo "$HTTP_CODE"

# 2. Show error details if not 200
if [ "$HTTP_CODE" != "200" ]; then
  echo "Error response:"
  cat /tmp/exa-triage.json | python3 -m json.tool 2>/dev/null || cat /tmp/exa-triage.json
fi

# 3. Check if it's a key issue
echo ""