AI Search API for agents

    Cited answers your agents can verify.

    Search the web and selected communities, with sources and freshness attached.

    $0.40/1000 items
    usage rate
    7 sources
    select per request
    MCP + REST
    agent-ready access
    Live answer flow
    POST /desearch/ai/search
    Agent query

    What patterns make production AI agents more reliable?

    Sources found
    1

    Building effective agents

    anthropic.com

    2

    Web search tools

    platform.openai.com

    3

    Retrieval for agents

    docs.langchain.com

    Cited answer

    Reliable agents pair focused tools with fresh retrieval, cited sources, and outputs downstream systems can inspect. 123

    citations
    freshness
    MCP-ready setup
    cost metadata

    Agent-ready integration

    Give your coding agent one prompt. It wires Search up.

    Paste the onboarding prompt into Claude Code, Codex, Cursor, VS Code, or any agent that can read instructions. It connects Desearch through MCP and proves the setup with a real request.

    Agent onboarding prompt

    Use curl to read www.desearch.ai/agents.md and follow it to set up Desearch

    One instruction replaces a setup guide: your agent reads the source of truth, installs the connection, and verifies that Search is ready.

    Agent setup
    waiting for view
    Search verifiedMCP connected

    Your agent can now search fresh sources and return evidence it can cite.

    Direct integration

    Prefer direct API control?

    Use the same Search endpoint from your application. The code is here for teams that want to control the request themselves, not as the main onboarding path.

    POST /desearch/ai/search
    import requests
    
    answer = requests.post(
        "https://api.desearch.ai/desearch/ai/search",
        headers={"Authorization": "YOUR_API_KEY"},
        json={
            "prompt": "What patterns make production AI agents more reliable?",
            "tools": ["web", "twitter"],
            "result_type": "LINKS_WITH_FINAL_SUMMARY",
            "count": 10,
            "streaming": False,
        },
    ).json()

    Built for agent workflows

    Three ways agents use Search.

    Connect one search capability, then let each agent use the evidence in the way its task requires.

    01

    Answer with current context

    Give assistants a direct answer plus the links and passages users need to check it.

    • Support
    • Copilots
    • Chat interfaces
    02

    Research with traceable sources

    Turn a broad question into ranked evidence and a concise summary without a custom search stack.

    • Market research
    • Monitoring
    • Briefings
    03

    Ground autonomous workflows

    Give planning and monitoring agents fresh evidence they can cite before they recommend or take the next step.

    • Research agents
    • Monitoring agents
    • Decision support

    Search API FAQ

    Know what your agent receives.

    The short version of agent setup, source control, streaming, and usage.

    Read the docs

    Yes. Paste the agents.md onboarding prompt into Claude Code, Codex, Cursor, VS Code, or another coding agent. It reads the current instructions, installs the Desearch MCP connection, verifies your key, and tests Search before it finishes.

    Search returns structured results with source titles, links, snippets, relevant highlights, and publication dates when a source provides them. Request LINKS_WITH_FINAL_SUMMARY when you also want a synthesized answer alongside the evidence.

    Yes. Set the tools parameter to web, twitter (X), or both in one request. To focus web results on specific sites, keep web and add include_domains, for example reddit.com.

    date_filter is optional. When you leave it out, no time window is applied. Returned publication dates depend on what each source exposes, so your application can inspect the evidence instead of treating every result as equally recent.

    Yes. Set streaming to true to receive the generated summary through server-sent events. Keep it false when your application prefers one complete JSON response.

    Search pricing is usage-based and measured in returned items. New accounts get $5 in credits when a card is attached at sign-up, and usage is pay-as-you-go after that. Successful billable responses expose request cost and usage metadata; Desearch Console shows the current rate, balance, and request history.

    The API uses standard HTTP status codes. Check the current rate-limit guide for your account, handle 429 responses with backoff, and use the API reference for the complete request and response schemas.

    Ready when your agent is

    Connect your agent to live, cited search.

    Start through the agent workflow, then use the API directly whenever your application needs finer control.

    Earn up to $155 in API credits
    1. 01

      Copy one prompt

      Paste the agents.md instruction into the coding agent you already use.

    2. 02

      Let it connect

      Your agent installs Desearch MCP and configures the Search tool.

    3. 03

      Review the check

      Setup finishes only after the key and a cited Search request are verified.