openevidence-common-errors
Troubleshooting guide for common OpenEvidence API error codes and clinical query timeouts.
Install
mkdir -p .claude/skills/openevidence-common-errors && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/3067" && unzip -o skill.zip -d .claude/skills/openevidence-common-errors && rm skill.zipInstalls to .claude/skills/openevidence-common-errors
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Diagnose and fix OpenEvidence common errors.Key capabilities
- →Diagnose OpenEvidence API authentication errors
- →Resolve OpenEvidence API rate limit issues
- →Address OpenEvidence API query validation errors
- →Handle OpenEvidence API service unavailability
- →Debug OpenEvidence API errors using a provided script
How it works
The skill provides a reference table and a TypeScript function to classify OpenEvidence API errors based on status codes and messages, offering solutions for common issues.
Inputs & outputs
When to use openevidence-common-errors
- →Fixing API authentication errors
- →Resolving query timeout issues
- →Debugging broad clinical query errors
- →Managing citation-not-found issues
About this skill
OpenEvidence Common Errors
Overview
OpenEvidence provides AI-powered clinical decision support through evidence-based query answering with citation tracking. API integrations involve submitting clinical questions, retrieving evidence summaries, and managing citation references. Common errors include overly broad queries that exceed processing limits, citation-not-found errors when referenced studies are retracted, and timeouts on complex multi-condition queries that trigger deep literature analysis. The DeepConsult mode provides more thorough analysis but consumes 5x the rate limit quota and has a 90-second timeout. This reference covers authentication, query validation, and clinical-specific error patterns.
Error Reference
| Code | Message | Cause | Fix |
|---|---|---|---|
401 | Authentication failed | Invalid or expired API key | Regenerate at OpenEvidence developer portal |
403 | Organization access denied | API key not authorized for org | Verify org ID matches the key's assigned organization |
404 | Citation not found | Referenced study retracted or removed | Query for updated evidence; citation database refreshes weekly |
408 | Query timeout | Complex multi-condition query exceeded 90s limit | Simplify query to single clinical question; avoid compound conditions |
422 | Query too broad | Question not specific enough for clinical analysis | Add condition, population, or intervention to narrow scope |
422 | Non-medical query | Question not recognized as clinical | Rephrase using medical terminology and clinical context |
429 | Rate limited | Exceeded API request quota | Implement backoff; check Retry-After header |
503 | Service unavailable | DeepConsult queue at capacity | Retry after 60s; consider standard query mode instead |
Error Handler
interface OpenEvidenceError {
code: number;
message: string;
category: "auth" | "rate_limit" | "query" | "availability";
}
function classifyOpenEvidenceError(status: number, body: string): OpenEvidenceError {
if (status === 401 || status === 403) {
return { code: status, message: body, category: "auth" };
}
if (status === 429) {
return { code: 429, message: "Rate limited", category: "rate_limit" };
}
if (status === 503) {
return { code: 503, message: body, category: "availability" };
}
return { code: status, message: body, category: "query" };
}
Debugging Guide
Authentication Errors
OpenEvidence API keys are scoped per organization. A 401 means the key itself is invalid; a 403 means the key is valid but not authorized for the specified org ID. Verify both the OPENEVIDENCE_API_KEY and the org_id parameter match. Keys are rotated quarterly for compliance -- check expiration date.
Rate Limit Errors
Rate limits vary by plan tier. Standard plans allow 100 queries/hour; enterprise plans have higher limits. DeepConsult queries (longer analysis) consume 5x the rate limit quota of standard queries. Use Retry-After header and implement exponential backoff.
Validation Errors
Queries must be clinically relevant and specific. "What causes headaches?" is too broad -- narrow to "What is the first-line treatment for migraine with aura in adults?" Add population, intervention, or comparison to improve query specificity. Non-medical queries are rejected with 422. Citation references use DOI-based identifiers; retracted studies return 404 and should be re-queried for updated evidence.
Error Handling
| Scenario | Pattern | Recovery |
|---|---|---|
| Query too broad | 422 with specificity warning | Add condition + population + intervention details |
| Citation not found | 404 on citation lookup | Re-query for updated evidence; citations refresh weekly |
| DeepConsult queue full | 503 on complex queries | Fall back to standard query mode; retry deep after delay |
| Timeout on compound query | 408 after 90s | Split into individual clinical questions |
| Org access mismatch | 403 despite valid key | Verify org_id parameter matches key's assigned organization |
Quick Diagnostic
# Verify API connectivity and key validity
curl -s -o /dev/null -w "%{http_code}" \
-H "Authorization: Bearer $OPENEVIDENCE_API_KEY" \
https://api.openevidence.com/v1/health
Resources
Next Steps
See openevidence-debug-bundle.
When not to use it
- →When the query is not clinical
- →When the query is too broad
- →When a citation is known to be retracted
Limitations
- →DeepConsult mode consumes 5x the rate limit quota
- →DeepConsult mode has a 90-second timeout
- →Citation database refreshes weekly
How it compares
This skill provides specific diagnostic and resolution steps for OpenEvidence API errors, unlike general API error handling.
Compared to similar skills
openevidence-common-errors side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| openevidence-common-errors (this skill) | 1 | 27d | Review | Beginner |
| fastapi-templates | 520 | 2mo | No flags | Intermediate |
| android-kotlin-development | 268 | 5mo | Review | Advanced |
| mcp-builder | 136 | 3mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
fastapi-templates
wshobson
Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.
android-kotlin-development
aj-geddes
Develop native Android apps with Kotlin. Covers MVVM with Jetpack, Compose for modern UI, Retrofit for API calls, Room for local storage, and navigation architecture.
mcp-builder
anthropics
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
fastapi-pro
sickn33
Build high-performance async APIs with FastAPI, SQLAlchemy 2.0, and Pydantic V2. Master microservices, WebSockets, and modern Python async patterns. Use PROACTIVELY for FastAPI development, async optimization, or API architecture.
api-design-principles
wshobson
Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.
telegram-bot-builder
davila7
Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategies, and scaling bots to thousands of users. Use when: telegram bot, bot api, telegram automation, chat bot telegram, tg bot.