What problem does it solve? Developers integrating Exa's API platform often pick the wrong endpoint, misplace request parameters, or use deprecated fields, causing failed calls and wasted debugging time. This Skill provides endpoint selection guidance, correct request shapes, and SDK naming rules for every Exa surface. ## Core Features & Use Cases - Endpoint Decision Workflow: Routes tasks to the right Exa surface, defaulting to POST /search with type auto and highlights, and escalating to the Agent API only for multi-step research. - Request Shape References: On-demand reference files cover search, contents, answer, context, agent, monitors, websets, OpenAI-compatible endpoints, and SDK casing differences between exa-py and exa-js. - Anti-Pattern Corrections: Documents common mistakes such as nesting contents fields incorrectly, using deprecated parameters like useAutoprompt and numSentences, or inventing unsupported category values. - Use Case: When building an agent that needs fresh web data, ask for an Exa integration and receive a correct /search call with highlights, proper EXA_API_KEY authentication, and guidance on when to use /answer, /context, or /agent instead. ## Quick Start Ask the agent to write an Exa search integration in Python or TypeScript that retrieves recent articles on a topic with highlights enabled.