curl -s https://www.pathwren.workers.dev/crawler/google-cloudvertexbot.json   # this page, as JSON

No key, no account, no handshake — every page here has a JSON twin one hop away. Machine doors: 6 keyless GET tools · documents.json · changes · llms.txt · openapi.json · agent card · mcp · a2a

Google-CloudVertexBot

Google · AI search crawlers · json

User-agent: Google-CloudVertexBot
Disallow: /


robots.txt token	`Google-CloudVertexBot`
User-agent contains	`Google-CloudVertexBot`
Operator	Google
Category	AI search crawlers
robots.txt	obeys robots.txt (documented)
Verify by	published IP ranges
Published ranges	136 IPv4 + 136 IPv6 · json · source

What it is

Crawls a site on behalf of a Vertex AI Agent Builder customer who is building an agent over that site. It only visits sites the customer has asked it to.

What blocking it costs you

Third parties can no longer build Vertex AI agents that read your site. Irrelevant to Google Search.

Full user-agent string

Mozilla/5.0 (compatible; Google-CloudVertexBot/1.0; +https://developers.google.com/search/docs/crawling-indexing/google-common-crawlers)

Allow it instead

User-agent: Google-CloudVertexBot
Allow: /

Ask this page a question, with one GET

A question about this page, answered by a call you can make right now — no key, no account, no JSON-RPC, nothing to assemble. The query string is already filled in with this page's own subject.

curl -s 'https://www.pathwren.workers.dev/tools/verification-methods?crawler=google-cloudvertexbot&s=client-dossiers'

/tools/verification-methods?crawler=google-cloudvertexbot
How do I prove a request really is Google-CloudVertexBot? The verification method its operator actually publishes — published IP ranges, reverse DNS, or nothing at all — and the mirror of it on this host.
/tools/verify-crawler?ip=108.177.2.0&ua=Google-CloudVertexBot
Is 108.177.2.0 really Google-CloudVertexBot? That address checked against every prefix this host mirrors. 108.177.2.0 is the first address of 108.177.2.0/27, one of the ranges listed on this page — so the link is a worked example that returns a match. Swap in an address from your own log.

Every parameter above is a value the endpoint reads, not an address it visits: nothing is fetched on your behalf. Called without any parameter, each endpoint returns its own specification instead of an error. All of them.

Operator documentation: https://developers.google.com/search/docs/crawling-indexing/overview-google-crawlers
Machine copies: json · markdown
Policies that name this crawler: allow-all · block-all-ai · allow-ai-search-only · maximum-ai-visibility