Test range (synthetic)
Try GAIP against things that go wrong on purpose.
Synthetic: part of GAIP's test range for developers. Not a real shop, product or service; no third parties and no personal data. Calls and checks of the test range are never counted as use of GAIP.
A shop whose sources disagree
/test-range/shop/products/demo-mug is a demo product page. Its JSON-LD says £24.00 and in stock, its meta tags say £15.00 and out of stock, and its product feed (/test-range/shop/products/demo-mug.js) says £36.00 and unavailable. Ask the Listing Observer:
gaip_observe_listing {"url": "https://www.gaipagents.com/test-range/shop/products/demo-mug"}An MCP server that misbehaves on request
https://www.gaipagents.com/test-range/mcp answers the MCP handshake. Its tool list changes every UTC day (odd days add a parameter to flaky), so gaip_watch and gaip_tools_changed_since have something to notice. Tool flaky fails when asked: mode error, tool_error, slow, rate_limited, server_error, unauthorized or bad_json. Then paste the error into gaip_diagnose.
gaip_check {"url": "https://www.gaipagents.com/test-range/mcp"}Fixed versions for repeatable tests: /test-range/mcp/schema-a · /test-range/mcp/schema-b · /test-range/mcp/unauthorized · /test-range/mcp/rate-limited · /test-range/mcp/server-error · /test-range/mcp/slow (schema-a and schema-b are the two tool lists; the others fail every request with 401, 429 with Retry-After, 500, or answer 3 seconds late).
Witness and permissions
Register what a test-range endpoint should deliver with witness_register_terms (service_url https://www.gaipagents.com/test-range/mcp) and check it with witness_delivery. Ask whether a crawler may fetch a test-range page with gaip_check_permission (it reads GAIP's own robots.txt).
What is never counted
Requests to /test-range and tool calls that name a test-range URL are classed as test traffic: they are left out of GAIP's usage figures, its datasets and the Agent Observatory's record.