Extract API for agents

    Clean web context for your agents.

    Turn any URL into clean text or HTML, ready for your agent's next step.

    $0.50/1000 pages
    Checked-in usage rate
    Clean
    Page text
    MCP + REST
    Agent-ready access
    Agent tool flow
    GET /web/extract
    Agent asks

    Extract clean text from this URL.

    1. Agent decides

      Selects the Desearch tool

    2. Tool runs

      GET /web/extract

    3. Context returns

      Ready for the next step

    Extraction response previewrunning

    Clean page context, ready for your agent.

    clean text
    optional HTML
    rendered content
    extraction status
    Agent receivesclean textoptional HTMLrendered contentrequest status

    Agent-ready integration

    Give your coding agent one prompt. It wires Extract 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 verifies extraction on a real page.

    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 Extract is ready.

    Agent setup
    waiting for view
    Extract verifiedMCP connected

    Your agent can now turn a supplied URL into clean, model-ready page context.

    Direct integration

    Prefer direct API control?

    Call the same Extract endpoint from your application when you want full control over the URL and request lifecycle.

    GET /web/extract
    import requests
    
    page = requests.get(
        "https://api.desearch.ai/web/extract",
        headers={"Authorization": "YOUR_API_KEY"},
        params={"url": "https://example.com/article", "format": "text"},
    ).text

    Agent use cases

    Three ways agents use Extract.

    A focused extraction layer for workflows that need page content they can read, compare, and reuse.

    Give agents readable pages

    Turn a supplied URL into clean page text and metadata that an agent can reason over immediately.

    Monitor changing sources

    Re-extract important pages on your schedule and send fresh source context into research or monitoring workflows.

    Build ingestion pipelines

    Feed normalized web content into RAG, indexing, and multi-step agent systems without maintaining a scraper.

    Extract API FAQ

    Know what your agent receives.

    The short version of agent setup, page handling, pricing, and limits.

    Read the docs

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

    Extract turns a supplied URL into clean page content as text or HTML. Use the current endpoint reference as the contract for available formats and parameters.

    Page handling varies by site and response. Test the URLs your workflow depends on and validate important output against the source.

    Pricing is usage-based. Review the current rate and request history in Desearch Console before planning a production workload.

    Rate limits depend on the account and endpoint. Check Console, response headers, and the current API reference, and handle retryable responses with backoff.

    Ready when your agent is

    Connect your agent to clean page context.

    Start through the agent workflow, then call Extract 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 right tool.

    3. 03

      Review the check

      Setup finishes only after the key and an Extract request are verified.