菜单
Diagnose and fix Exa API errors by HTTP code and error tag. Use when encountering Exa errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "exa error", "fix exa", "exa not working", "debug exa", "exa 429", "exa 401".
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace --skill exa-common-errors命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Deploy a LangChain 1.0 / LangGraph 1.0 app to Cloud Run, Vercel, or LangServe correctly — with timeouts sized for chain length, cold-start mitigation, SSE anti-buffering headers, and Secret Manager over .env. Use when prepping a first production deploy, debugging a stream that hangs behind a proxy, or diagnosing p99 latency spikes. Trigger with "langchain deploy", "langchain cloud run", "langchain vercel python", "langchain langserve", or "langchain docker".
Build a correct LangGraph 1.0 ReAct agent with create_react_agent — typed tools, error propagation, recursion caps, and stop conditions that actually stop. Use when writing a first tool-calling agent, migrating from AgentExecutor or initialize_agent, or diagnosing an agent that loops on vague prompts. Trigger with "langgraph agent", "create_react_agent", "langgraph tool calling", "AgentExecutor migration", or "agent loop cost".
Build LangGraph 1.0 human-in-the-loop approval flows with interrupt_before / interrupt_after and Command(resume=...) — JSON-serializable state, clean resume semantics, and UI wiring for approval decisions. Use when adding an approval gate before an expensive tool call, wiring a Slack/web UI for agent approvals, or debugging a graph that crashes on interrupt. Trigger with "langgraph human in loop", "langgraph interrupt_before", "langgraph approval flow", "Command resume", "langgraph HITL".
正在显示 SKILL.md
| name | exa-common-errors |
| description | Diagnose and fix Exa API errors by HTTP code and error tag. Use when encountering Exa errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "exa error", "fix exa", "exa not working", "debug exa", "exa 429", "exa 401". |
| allowed-tools | Read, Grep, Bash(curl:*), Bash(node:*) |
| version | 1.11.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","exa","debugging","errors"] |
| compatibility | Designed for Claude Code |
Quick reference for Exa API errors by HTTP status code and error tag. All error responses include a requestId field — include it when contacting Exa support at hello@exa.ai.
| Error Tag | Cause | Solution |
|---|---|---|
INVALID_REQUEST_BODY | Malformed JSON or missing required fields | Validate JSON structure and required query field |
INVALID_REQUEST | Conflicting parameters | Remove contradictory options (e.g., date filters with company category) |
INVALID_URLS | Malformed URLs in getContents | Ensure URLs have https:// protocol |
INVALID_NUM_RESULTS | numResults > 100 with highlights | Reduce to <= 100 or remove highlights |
INVALID_JSON_SCHEMA | Bad schema in summary.schema | Validate JSON schema syntax |
NUM_RESULTS_EXCEEDED | Exceeds plan limit | Check your plan's max results |
NO_CONTENT_FOUND | No content at provided URLs | Verify URLs are accessible |
# Verify your API key is set and valid
echo "Key set: ${EXA_API_KEY:+yes}"
# Test with curl
curl -s -o /dev/null -w "%{http_code}" \
-X POST https://api.exa.ai/search \
-H "x-api-key: $EXA_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query":"test","numResults":1}'
Fix: Regenerate API key at dashboard.exa.ai.
| Error Tag | Cause | Solution |
|---|
NO_MORE_CREDITS | Account balance exhausted | Top up at dashboard.exa.ai |
API_KEY_BUDGET_EXCEEDED | Spending limit reached | Increase budget in API key settings |
| Error Tag | Cause | Solution |
|---|---|---|
ACCESS_DENIED | Feature not available on plan | Upgrade plan or contact Exa |
FEATURE_DISABLED | Endpoint not enabled | Check plan capabilities |
ROBOTS_FILTER_FAILED | URL blocked by robots.txt | Use a different URL |
PROHIBITED_CONTENT | Content blocked by moderation | Review query for policy violations |
// Default rate limit: 10 QPS (queries per second)
// Error response format: { "error": "rate limit exceeded" }
// Fix: implement exponential backoff
async function searchWithBackoff(exa: Exa, query: string, opts: any) {
for (let attempt = 0; attempt < 5; attempt++) {
try {
return await exa.search(query, opts);
} catch (err: any) {
if (err.status !== 429) throw err;
const delay = 1000 * Math.pow(2, attempt) + Math.random() * 500;
console.log(`Rate limited. Waiting ${delay.toFixed(0)}ms...`);
await new Promise(r => setTimeout(r, delay));
}
}
throw new Error("Rate limit retries exhausted");
}
| Error Tag | Cause | Solution |
|---|---|---|
FETCH_DOCUMENT_ERROR | URL could not be crawled | Verify URL is accessible and not paywalled |
| Code | Tag | Action |
|---|---|---|
| 500 | DEFAULT_ERROR / INTERNAL_ERROR | Retry after 1-2 seconds |
| 501 | UNABLE_TO_GENERATE_RESPONSE | Rephrase query (answer endpoint) |
| 502 | Bad Gateway | Retry with delay |
| 503 | Service Unavailable | Check status page, retry later |
| Tag | Cause | Resolution |
|---|---|---|
CRAWL_NOT_FOUND | Content unavailable at URL | Verify URL correctness |
CRAWL_TIMEOUT | Fetch timed out | Retry or increase livecrawlTimeout |
CRAWL_LIVECRAWL_TIMEOUT | Live crawl exceeded timeout | Set livecrawlTimeout: 15000 or use livecrawl: "fallback" |
SOURCE_NOT_AVAILABLE | Paywalled or blocked | Try cached content with livecrawl: "never" |
UNSUPPORTED_URL | Non-HTTP URL scheme | Use standard HTTPS URLs |
set -euo pipefail
echo "=== Exa Diagnostics ==="
echo "API Key: ${EXA_API_KEY:+SET (${#EXA_API_KEY} chars)}"
# Test basic connectivity
echo -n "API connectivity: "
HTTP_CODE=$(curl -s -o /tmp/exa-test.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":"connectivity test","numResults":1}')
echo "$HTTP_CODE"
if [ "$HTTP_CODE" != "200" ]; then
echo "Error response:"
cat /tmp/exa-test.json | python3 -m json.tool 2>/dev/null || cat /tmp/exa-test.json
fi
requestId from error responses when contacting supportFor comprehensive debugging, see exa-debug-bundle. For rate limit patterns, see exa-rate-limits.