url. The exceptions: name for prefetch_resolve, descriptor for prefetch_transaction, query for prefetch_search, task for prefetch_answer, urls for the batch tools, domains for prefetch_logo_urls, id for the crawl and monitor tools that act on one, and name plus schedule to create a monitor.
See MCP server for setup.
Finding a domain
prefetch_resolve
Turns a company, brand or product name into the domain of its official website: “Stripe” → stripe.com. Every other tool takes a URL, so this is where a task that starts from a name begins: resolve the name, then call prefetch_enrich, prefetch_brand or prefetch_company with the domain.
Each result has a confidence from 0 to 1. Only the first can reach 0.8, and at or above it that result is the answer. Over MCP, names the index is unsure of are looked up live by default. That takes a few seconds and costs 3 credits, versus 1 from the index.
prefetch_transaction
Turns a card transaction descriptor (a bank statement line like SQ *BLUE BOTTLE COFFE OAKLAND CA) into the merchant behind it: its name, website, processor and location, and a logo_url ready to show. Lines that are payments to a person, transfers, fees or ATM withdrawals say so in kind. See GET /transaction.
3 credits per lookup, 1 for a line looked up in the last 7 days.
Web extraction
prefetch_search
Search the web (Google results) and get each result’s title, URL and snippet, optionally with every result page scraped into markdown in the same call. Use it to find pages. For a researched answer, use prefetch_answer. See GET /search.
2 credits per 10 results, plus 1 per page scraped (4 with
summary or json).
prefetch_scrape
Fetch one URL and return its content. Handles JavaScript-rendered pages, strips boilerplate, and resolves every link and image to an absolute URL.
Use it when you know which page you want. To find pages first, use prefetch_map.
raw_html is much larger than markdown. Only ask for it when you need the source.
prefetch_map
Discover the URLs on a site, from its sitemaps and on-page links, without fetching page content. Fast and cheap.
Mapping first and then scraping the two or three pages you want is usually better, and much cheaper, than crawling.
prefetch_crawl
Crawl a site or a section of one, returning each page as markdown. Starts the crawl and waits for it. See how crawling works.
Crawls are billed per page. Scope them with include_paths and keep limit as low as will do.
Sitemap-seeded pages sit at depth 0, because they were handed over rather than followed. So
max_depth: 0 with use_sitemap: true crawls exactly what the sitemap lists and follows nothing.prefetch_check_crawl_status
Status and results for a crawl or batch. Returns one page of results at a time.
Calling this is free. Only pages that completed since your last call are billed.
prefetch_cancel_crawl
Stop a running crawl. Pages already fetched stay readable via prefetch_check_crawl_status until the crawl expires.
prefetch_batch_scrape
Scrape many known URLs in one job and get each page as markdown. Starts the job and waits for it (wait_seconds, default 60), returning the pages if it finishes in time and an id for prefetch_check_crawl_status if not. See POST /batch/scrape.
1 credit per page returned.
prefetch_batch
Run brand, enrich, company, classify, screenshot or styleguide on a list of URLs or bare domains as one job, and get every result back: the same result each single tool returns. Waits like prefetch_batch_scrape. See POST /batch/{endpoint}.
Each URL costs what one call of that tool costs; failed URLs are free.
Brand and company data
prefetch_enrich
Everything known about the company behind a URL in one call: brand assets, company details, and IAB classification.
screenshot_colors catches colors that only exist inside images, at the cost of a slower call. design_tokens is what to ask for when building UI that should match the site.
prefetch_brand
Brand identity for a URL: palette with color names and hex values, font families, logos, favicon, and Open Graph images.
Takes the same parameters as prefetch_enrich. Use prefetch_enrich instead if you also want company details or industry.
prefetch_company
Company name, contact emails, postal addresses, and social profiles for the organization behind a URL.
prefetch_classify
IAB content category and subcategory, with a description and, for public companies, stock tickers and ISINs.
The cheapest way to answer “what kind of business is this”.
prefetch_screenshot
Render a page and return a hosted image URL.
This returns a link, not image bytes. Pass the URL on to the user, or to a tool that can fetch images.
prefetch_styleguide
A site’s design system, read from the rendered page: colors by role, the type scale, spacing, radii, shadows, button, input, card and link styles, breakpoints and the site’s own CSS variables, plus the same as CSS custom properties (exports.css) and a Tailwind theme (exports.tailwind). Use it to build UI that matches a site. See GET /styleguide.
10 credits.
prefetch_logo_urls
Ready-to-embed logo image URLs for up to 50 domains, from the logo CDN. Put them straight in <img> tags or markdown. A domain without a known logo shows a letter mark.
Free: logos use your plan’s monthly logo quota, not credits.
Research
prefetch_answer
Research a question on the live web and get a sourced answer as JSON in the shape you describe. It searches the web, reads pages, and looks up company records as the task needs, then returns json_content in the shape of json_format plus the sources it read. Facts it could not establish come back null.
Use it when the answer needs searching or several sources. When you already know the page, prefetch_scrape with formats: ["json"] is cheaper; for a company’s profile from its URL, use prefetch_enrich.
Over MCP the default mode is
fast; over REST it is ultra. Failures and timeouts are never charged.Monitoring
A monitor re-checks pages on a schedule and records what changed. See Monitors for how changes are detected and judged. The tools take a flatter shape than the REST body:urls for specific pages and crawl_url for a site, instead of a list of targets.
An agent rarely has a webhook to receive changes at, so it reads them back, or passes email to have each check that finds changes emailed to a person: prefetch_run_monitor runs a check and waits for it, and prefetch_get_monitor_check shows the latest check by default. Both list only the pages that changed, appeared, disappeared or failed, the judge’s verdict first, then any field changes, then the diff, and count the unchanged ones.
prefetch_create_monitor
Start watching pages. Pass urls, crawl_url, or both.
A monitor bills on every check for as long as it’s active: 1 credit per page fetched, +3 when a JSON extraction runs, and +1 per change judged. So prefer few pages and a modest schedule.
prefetch_run_monitor
Run a check now, wait for it, and return what changed since the previous check. Billed like any check.
prefetch_get_monitor_check
What a check found. Leave check_id out for the most recent one. Free.
prefetch_list_monitors
The key’s monitors with each one’s schedule and last check. Free.
prefetch_get_monitor
One monitor’s settings, next run, estimated cost, and its five most recent checks. Free.
prefetch_update_monitor
Change a monitor. Fields you leave out stay as they are. Free.
prefetch_delete_monitor
Delete a monitor and its history, stopping all future checks. To stop it for a while, pause it with prefetch_update_monitor instead. Free.