Build with Yep

Yep answers one request with ranked web pages: the URL, title and description of each, up to three passages that match the query, and page metadata such as language, publication time and category. The index is crawled continuously. There are two ways to use it.

Choose your path

• MCP — your agent calls Yep as a tool. Claude, Codex, Cursor, VS Code and Gemini CLI connect to one remote server and sign in with OAuth, with no API key and nothing to install. Start with Connect your agent.
• HTTP — your code calls GET or POST /api/v1/search with an API key, from any language. The first request is one cURL command: send your first request.

Both paths run the same search and cost the same: $4 per 1,000 completed requests on Balanced, nothing for a failed request, and a $15 credit when you sign up, with no card.

Get an API key

The HTTP path needs a key; the MCP path does not.

1. Create an account. The new workspace receives the signup credit.
2. In Settings → API keys, create a key and copy the secret when it is shown. Yep does not show it again.
3. Store the secret in the YEP_API_KEY environment variable, never in code, URLs or logs.

Give each application and environment its own key, with an optional monthly spend limit; see Authentication for rotation.

See it in use

Five jobs, each one runnable request with its response fields and its cost at a stated volume: Solutions. The generated API reference lists every operation.