AI agents — install + integration guide

1 · MCP descriptor (recommended; works today)

Policy Window publishes a Model Context Protocol descriptor at https://policywindow.org/mcp.json documenting the 8 read-only tools (search_catalog, get_instrument, get_topic_coverage, get_coverage_cell, compare_jurisdictions, list_changes, cite_article, glossary_lookup), the response-envelope shape, the charter-compliance constraints, and the public endpoints to wire them against.

Until the full @policywindow/mcp-server npm package ships (Wave 2, ~weeks 4-9 of the iter-316 plan), agents wire the tool surface directly against the existing public endpoints documented in the descriptor.

# Fetch the descriptor + see the tool surface
curl -s https://policywindow.org/mcp.json | jq '.tools[].name'

2 · llms.txt + sub-audience variants (auto-discovered)

AI assistants (Claude, ChatGPT, Perplexity, Google AI Overview, Gemini) increasingly look for /llms.txt at the site root as a curated guide to high-value content. Policy Window publishes:

• /llms.txt — canonical short-form index
• /llms-full.txt — full-context companion (methodology + charter + AI-disclosure inlined)
• /llms-researchers.txt — for academic-researcher agent contexts
• /llms-journalists.txt — for journalist-on-deadline agent contexts
• /llms-procurement.txt — for procurement-evaluator agent contexts
• /llms-regulators.txt — for regulator-staffer agent contexts
• /llms-advocates.txt — for civil-society-advocate agent contexts
• /llms-developers.txt — for developer-integration agent contexts

Configure a Claude Project / Custom GPT / Gemini Gem to fetch the appropriate sub-audience variant as its system context; the agent will navigate the catalog with the right priorities for its workflow.

3 · Schema.org structured data (Google AI Overview eligibility)

Every PW article emits schema.org JSON-LD (Article + Legislation + BreadcrumbList + FAQPage). The hub at https://policywindow.org/wiki adds a Dataset node. Every topic article emits per-cell ClaimReview nodes (the single highest-leverage AI-Overview citation move; peer platforms with correct ClaimReview report 48%+ AI-Overview citation rate).

4 · Open APIs (no auth, CORS-open)

• GET /wiki/catalog/json — full structured catalog (~3MB, CC0 citation graph)
• GET /api/search?q=foo&kind=instrument&limit=50 — ranked search (10KB; resolve natural-language refs to slugs)
• GET /api/openapi — OpenAPI 3.1 spec
• GET /wiki/[slug]/datacite.xml — DataCite 4.4 per article
• GET /wiki/changelog/feed — RSS 2.0
• GET /mcp.json— MCP descriptor (this page's primary integration target)

5 · Roadmap (iter-316 plan Wave 2-3)

• @policywindow/mcp-server npm package (Wave 2, ~weeks 4-9) — stateless stdio + HTTP transport with the 8 tools wired
• /wiki/catalog/cells/[instrument]/[topic] — per-cell JSON anchor
• /wiki/catalog/rdf — Turtle export with owl:sameAs to Wikidata + ELI + CELEX
• Claude Project / Custom GPT / Gemini Gem / NotebookLM / Microsoft Copilot forkable templates (Wave 3)
• Provision-level verbatim text backfill (~580 cells × 6 min editorial via Coverage Games quarterly cycles)
• /wiki/catalog/coci.csv — OpenCitations-compatible outbound citation dump
• /embed/cell/[instrument]/[topic] + oEmbed JSON for CMS-pasteable citation cards