Connect WebCrawlerAPI to your AI agent

Data & Analytics 10 actions available

WebCrawlerAPI provides crawling, page scraping, AI web agents, and monitored website feeds through a unified API.

We set up the connection using your own WebCrawlerAPI account, with keys you control, and keep it running. Your agent picks it up and starts doing the work.

Book a setup call → See pricing
Actions

What your agent can do in WebCrawlerAPI

Each one is a real action the agent can take on its own, the same things a person clicking around WebCrawlerAPI could do. Read-only by default; write actions are confirmed against your policy.

  • Create Crawl Start a metered asynchronous crawl over a site and return its job ID. The crawl may visit and charge for up to items_limit pages; use GET_CRAWL_JOB to monitor it.
  • Create Feed Create a recurring website-change feed. Creation immediately schedules an initial crawl that may consume metered credits, and future scheduled runs may also consume credits; delete the feed when it is no longer needed.
  • Delete Feed Permanently cancel a feed so it cannot be resumed. The feed is removed from feed listings, but retained history may remain directly readable for 30 days.
  • Get Crawl Job Get a crawl job's status, configuration, per-page results, content URLs, errors, and observed costs. Respect recommended_pull_delay_ms when polling.
  • Get Feed Get one feed's configuration, lifecycle status, and recent run history, including per-run crawl counts and cost. Canceled feeds remain directly readable while retained by the provider.
  • Get Organization Costs Return current spendable balance plus request count and USD usage for a date range. The connected API key is used for both organization routes.
  • List Feed Changes Return one page of detected feed changes as structured JSON, with an opaque continuation cursor for older pages.
  • List Feeds List active and paused feeds for the connected organization, newest first. Logically canceled feeds are omitted.
  • Scrape Page Scrape one web page synchronously and return requested content or structured extraction. This consumes metered credits; supplying a prompt adds $0.002 per request.
  • Set Feed State Pause an active feed's future scheduled runs or resume a paused feed. Pausing does not stop a run that has already started, and resuming schedules future crawls that may consume metered credits.
Setup

How we connect it

  1. 1

    Connect your account

    You create a key in WebCrawlerAPI, a key you create and control, and paste it in once. It lives in a secrets store on your server, not with us.

  2. 2

    Set the guardrails

    Read-only by default. You choose which write actions the agent may take, and anything outside that policy gets confirmed with you first.

  3. 3

    We keep it running

    Health checks on every connection, updates handled for you, and we watch the first week of activity to make sure the work lands.

FAQ

WebCrawlerAPI questions, answered.

With a key you create and control. You paste it in once, it is stored in a secrets store on your server, permissions are scoped to the minimum the agent needs, and you can revoke it at any time.
The actions WebCrawlerAPI's API allows, the same things a person clicking around the app could do. Connections start read-only by default; write actions are confirmed against the policy you set before the agent takes them.
Connections are priced per tool on top of the base plan. Some are included, some are premium. See pricing for how connection charges work.
Standard tools are ready inside 7 business days of the setup call. We test the connection end to end, walk you through how the agent uses it, and watch the first week of activity.

Ready to put WebCrawlerAPI to work?

Tell us what your team runs on. We set up the connection, secure it, and your agent takes it from there.

Book a setup call → Browse all connections

All product names, logos, and brands are property of their respective owners; used for identification only. ZeroToClaw is not affiliated with or endorsed by WebCrawlerAPI.