# Webterra public agent guide

Webterra is the map of what AI agents can do on the web. Use the versioned read-only REST API at /api/v2 for public sites, tasks, interfaces, routes and evidence. REST /api/v1 remains available.

The limited public Beta supports anonymous catalog reads, developer OAuth and existing API keys. MCP uses Streamable HTTP at https://project-uiuj9.vercel.app/mcp/v2; /mcp preserves v1. For OAuth, use /mcp/v2/auth or /mcp/auth and first link the catalog identity to a verified Webterra account. Pre-registered Codex and Cursor setup, consent and disconnect instructions are at https://www.webterra.ai/developers. No dynamic client registration or registry listing is offered.

Anonymous ceilings across REST and MCP: 100 useful reads per normalized IP bucket per UTC day, 1,000 useful reads globally/day, 2,000 transport attempts globally/day, 60 attempts globally/minute and two active catalog reads. Shared networks share an IP allowance. Developer keys and OAuth share 10,000 reads per account per UTC month. These are maximum limits, not availability guarantees. Respect 429 Retry-After; invalid, expired or revoked credentials fail without anonymous fallback.

Start with /api/v2/tasks, /api/v2/sites and /api/v2/tasks/{id}/evidence, or MCP search_tasks, search_sites and get_task_evidence. Preserve no_verified_route, unavailable, stale and empty responses. Historical observations retain their actual dates and expired-interface labels; a past success does not establish a currently eligible route.

Catalog access never executes tasks, browses arbitrary URLs, exposes private evidence or owner reports, changes mappings, dispatches scans, grants operator access or performs billing actions. See /developers, /methodology, /data and /llms-full.txt.