Sanaf AI
Start free
Developer Tools

Context.dev, 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 Context.dev 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.

  • Developer Tools
  • Connects with a key
  • 11 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 Context.dev is

Context.dev provides web scraping, extraction, brand intelligence, monitoring, and structured web data APIs for AI applications.

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

How a run works

One message in, the work done in Context.dev.

  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 Context.dev. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Context.dev 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.

11 tools it already has

What it can do in Context.dev

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

  • Extract Structured Web DataCrawl relevant pages from a website and return data matching a caller-provided JSON Schema and extraction instructions. This is a higher-cost metered call; use SCRAPEWEBPAGEMARKDOW
  • Get BrandRetrieve enriched brand identity, logos, colors, industry, and description using exactly one domain, name, work email, ticker, direct URL, or transaction descriptor. Use SEARCHBRAN
  • Get Monitor LimitsReturn the connected account's plan and current monitor usage versus its monitor limit.
  • Get WebDB UsageReturn WebDB credit balance, period consumption, row count, storage, and per-collection usage for an optional time range.
  • Get Website StyleguideExtract a website's colors, typography, spacing, shadows, font assets, and common component styles from either a domain or one direct URL. A successful extraction normally consumes
  • List BatchesList and filter the connected account's asynchronous web batches from newest to oldest, returning one cursor-controlled page.
  • List MonitorsList and filter the connected organization's web monitors, returning one cursor-controlled page.
  • List WebDB CollectionsList the connected account's WebDB collections and return one cursor-controlled page, including each collection's sources, extraction configuration, status, usage, and timestamps.
  • Parse FileConvert an uploaded document, image, source file, or data file into LLM-usable Markdown.
  • Scrape Webpage to MarkdownRender one public URL and return its main or CSS-selected content as Markdown. This free-tier tool does not perform paid browser actions. A successful scrape normally consumes one
  • Search BrandsPrefix-search Context.dev's existing brand index by company name or domain and return up to 10 lightweight matches.
Access, and who is in charge of it

You stay the boss of your Context.dev 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 Context.dev 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 Context.dev 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 Context.dev 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 Context.dev

Can an AI employee really work inside Context.dev?
Yes. It signs in to your own Context.dev 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 Context.dev?
No. Nothing moves and nothing is replaced. Your records stay in Context.dev, 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 Context.dev account?
You paste in a key from your own Context.dev account. It is kept encrypted, and you can withdraw it from inside Context.dev 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 Context.dev?
It has 11 ready-made tools in Context.dev today, among them Extract Structured Web Data, Get Brand and Get Monitor Limits. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Context.dev 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 Context.dev 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 Context.dev?
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 Context.dev is written down with what it did and when.