OP

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.zip

Installs 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.
44 charsno explicit “when” trigger
Beginner

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

You give it
OpenEvidence API error codes and messages
You get back
Categorized error, cause, and fix for OpenEvidence API issues

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

CodeMessageCauseFix
401Authentication failedInvalid or expired API keyRegenerate at OpenEvidence developer portal
403Organization access deniedAPI key not authorized for orgVerify org ID matches the key's assigned organization
404Citation not foundReferenced study retracted or removedQuery for updated evidence; citation database refreshes weekly
408Query timeoutComplex multi-condition query exceeded 90s limitSimplify query to single clinical question; avoid compound conditions
422Query too broadQuestion not specific enough for clinical analysisAdd condition, population, or intervention to narrow scope
422Non-medical queryQuestion not recognized as clinicalRephrase using medical terminology and clinical context
429Rate limitedExceeded API request quotaImplement backoff; check Retry-After header
503Service unavailableDeepConsult queue at capacityRetry 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

ScenarioPatternRecovery
Query too broad422 with specificity warningAdd condition + population + intervention details
Citation not found404 on citation lookupRe-query for updated evidence; citations refresh weekly
DeepConsult queue full503 on complex queriesFall back to standard query mode; retry deep after delay
Timeout on compound query408 after 90sSplit into individual clinical questions
Org access mismatch403 despite valid keyVerify 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.

SkillInstallsUpdatedSafetyDifficulty
openevidence-common-errors (this skill)127dReviewBeginner
fastapi-templates5202moNo flagsIntermediate
android-kotlin-development2685moReviewAdvanced
mcp-builder1363moReviewAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

More by jeremylongshore

View all by jeremylongshore

analyzing-logs

jeremylongshore

Analyze application logs to detect performance issues, identify error patterns, and improve stability by extracting key insights.

14123

ollama-setup

jeremylongshore

Configure auto-configure Ollama when user needs local LLM deployment, free AI alternatives, or wants to eliminate hosted API costs. Trigger phrases: "install ollama", "local AI", "free LLM", "self-hosted AI", "replace OpenAI", "no API costs". Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.

1167

backtesting-trading-strategies

jeremylongshore

Backtest crypto and traditional trading strategies against historical data. Calculates performance metrics (Sharpe, Sortino, max drawdown), generates equity curves, and optimizes strategy parameters. Use when user wants to test a trading strategy, validate signals, or compare approaches. Trigger with phrases like "backtest strategy", "test trading strategy", "historical performance", "simulate trades", "optimize parameters", or "validate signals".

1071

generating-database-seed-data

jeremylongshore

Process this skill enables AI assistant to generate realistic test data and database seed scripts for development and testing environments. it uses faker libraries to create realistic data, maintains relational integrity, and allows configurable data volumes. u... Use when working with databases or data models. Trigger with phrases like 'database', 'query', or 'schema'.

1033

cursor-codebase-indexing

jeremylongshore

Execute set up and optimize Cursor codebase indexing. Triggers on "cursor index setup", "codebase indexing", "index codebase", "cursor semantic search". Use when working with cursor codebase indexing functionality. Trigger with phrases like "cursor codebase indexing", "cursor indexing", "cursor".

885

testing-mobile-apps

jeremylongshore

Execute mobile app testing on iOS and Android devices/simulators. Use when performing specialized testing. Trigger with phrases like "test mobile app", "run iOS tests", or "validate Android functionality".

810

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.

5201,086

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.

268679

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).

136215

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.

79181

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.

72170

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.

106130

Search skills

Search the agent skills registry