Sanaf AI
Start free
AI Web Scraping

WebCrawlerAPI, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your WebCrawlerAPI account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • AI Web Scraping
  • Connects with a key
  • 10 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What WebCrawlerAPI is

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

You paste in a key from your own WebCrawlerAPI account. It is kept encrypted, and you can withdraw it from inside WebCrawlerAPI whenever you like.

How a run works

One message in, the work done in WebCrawlerAPI.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in WebCrawlerAPI. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own WebCrawlerAPI account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

10 tools it already has

What it can do in WebCrawlerAPI

These are the ready-made tools your AI employee already has in WebCrawlerAPI. It is not limited to them, but it never has to be taught these.

  • Create CrawlStart a metered asynchronous crawl over a site and return its job ID. The crawl may visit and charge for up to itemslimit pages; use GETCRAWLJOB to monitor it.
  • Create FeedCreate 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
  • Delete FeedPermanently 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 JobGet a crawl job's status, configuration, per-page results, content URLs, errors, and observed costs. Respect recommendedpulldelayms when polling.
  • Get FeedGet 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 provi
  • Get Organization CostsReturn 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 ChangesReturn one page of detected feed changes as structured JSON, with an opaque continuation cursor for older pages.
  • List FeedsList active and paused feeds for the connected organization, newest first. Logically canceled feeds are omitted.
  • Scrape PageScrape 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 StatePause 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 me
Access, and who is in charge of it

You stay the boss of your WebCrawlerAPI account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own WebCrawlerAPI account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in WebCrawlerAPI is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in WebCrawlerAPI and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about WebCrawlerAPI

Can an AI employee really work inside WebCrawlerAPI?
Yes. It signs in to your own WebCrawlerAPI account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of WebCrawlerAPI?
No. Nothing moves and nothing is replaced. Your records stay in WebCrawlerAPI, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my WebCrawlerAPI account?
You paste in a key from your own WebCrawlerAPI account. It is kept encrypted, and you can withdraw it from inside WebCrawlerAPI whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in WebCrawlerAPI?
It has 10 ready-made tools in WebCrawlerAPI today, among them Create Crawl, Create Feed and Delete Feed. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use WebCrawlerAPI and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in WebCrawlerAPI and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in WebCrawlerAPI?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in WebCrawlerAPI is written down with what it did and when.