API / FOR AI & BUILDERS
Usable from ChatGPT,
Grok and Claude.
All guide content is available through static JSON, a REST API (OpenAPI 3.1) and MCP (Model Context Protocol). Nothing depends on a particular AI vendor’s account or key.
1. Static JSON (works anywhere)
Read-only data published with the site, readable by ChatGPT, Grok or Claude browsing, or your own code. Index: /api/v1/index.json; AI-oriented overview: /llms.txt.
curl https://inspection.airfficworld.com/api/v1/assets/bridge.json
curl https://inspection.airfficworld.com/api/v1/countries/jp.json
2. REST API (OpenAPI 3.1)
Search, calculators and learning-state sync. Specification: /openapi.json. In ChatGPT custom GPTs, import this URL as an Action. For Grok or Claude, use the same specification for function/tool definitions.
npm start # http://localhost:8787
curl "http://localhost:8787/v1/search?q=bridge+gnss&lang=en"
curl -X POST http://localhost:8787/v1/calc/gsd -H 'content-type: application/json' \
-d '{"sensorWidthMm":13.2,"focalLengthMm":8.8,"imageWidthPx":5472,"distanceM":3}'
3. MCP (Claude, ChatGPT and Grok clients that support it)
Runs over stdio and over HTTP (Streamable HTTP at /mcp). Tools: search_guide, get_asset, get_environment, list_cases, get_regulation, list_country_sources, calc_gsd, calc_coverage, calc_cost.
# Claude Desktop / Claude Code (stdio)
{ "mcpServers": { "airffic-inspection": { "command": "node", "args": ["tools/mcp.mjs"] } } }
# Remote MCP (ChatGPT connectors, xAI/Grok remote tools, Claude)
https://<your-host>/mcp
4. CLI and Git
npm run cli -- search "トンネル 非GPS"
npm run cli -- asset sewer --lang en
npm run cli -- gsd --sensor 13.2 --focal 8.8 --width 5472 --distance 3Everything is text in Git (`src/content/`, `research/`). Any AI agent can follow `AGENTS.md` in the repository to contribute under the same rules.
5. Airffic common infrastructure
Sign-in uses the shared Airffic account (Supabase Auth). Saved items, reading status, checks and notes sync only as the user’s own record via `inspection_pull` / `inspection_push`. People and organisations reuse the shared records. The database change is under review as common-infra PR #29 and will be applied to production only after founder approval; until then records stay on this device.