Skip to main content
Fetch up to 20 live URLs now as a browser or named AI crawler (GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot) to check HTTP status, robots.txt verdicts, brand mentions, contacts, and JSON-LD (paid: $0.01/page loaded, runs within monthly budget; quote: true prices without buying). Use only for work the user asked for or pages Parse lacks (never for routine lookups — read_item reads stored copies free). Robots verdicts, 403/404, and blocked/failed loads are free (notCharged). Identical calls within the UTC hour deduplicate.

Who may call it, and what it costs

Price. $0.01 a page that loads. A page that does not answer, an HTTP error, a challenge page or a robots.txt verdict is free. quote: true prices it only and starts nothing. Every reply says what the call cost in meta.costCredits. The prices are on Spending, tracking and stopping.

Arguments

list of URL
required
up to 20
one of browser, gptbot, oai-searchbot, claudebot, perplexitybot
browser (default) or a named AI crawler, whose robots.txt rules are obeyed
list of string
brd_ ids to mark in the text; default the workspace’s brands up to 20
list of one of structuredData
structuredData: the page’s raw JSON-LD blocks, left out unless asked (contacts found in them are always returned) up to 1
boolean
true: the price and whether it fits, buying nothing; without it the call runs when it fits
string
the same key with the same arguments returns the same job and charges nothing more; other arguments are refused. Left out, an identical call within the UTC hour is the same call; pass a key to buy it again
Every argument the tool takes, as GET /v1/tools serves it, every shared object written out; https://agent.parse.gl/openapi.json serves the same schema with the filter and the window named once under components and pointed to by $ref. MCP tools/list leaves out the arguments few calls send, and says the filter and the window once, under search_answers; resolve_ids {"kinds": ["argument"]} lists what it left out, and a call with any of them runs:

Example call

Fetch a page as GPTBot sees it, with the robots.txt verdict. Over REST:
Over MCP, the assistant calls the tool by name with the same arguments:
The reply has data, context, next, page and meta; follow next for the calls that come after. A refused call returns { code, message, fix }: see the error table.