Build against explicit contracts.
Architecture, APIs, SDKs, specifications, release evidence, and contribution workflows in one place. Public documentation stays public; account and admin operations stay behind their own access boundaries.
6
Core guides
7
Delivery modes
1
OpenAPI
Choose the developer job
Six canonical entry points
Each page owns one concern. No duplicate admin dashboard is presented as a public product.
Understand
FAI Architecture
System boundaries, delivery stages, data flow, trust, and how the products compose.
Integrate
FAI API Reference
Canonical endpoint, schema, authentication, tool, and SDK contracts.
Embed
Agent FAI Platform API
Grounded chat, architecture, citations, diagrams, Play search, and cost workflows.
Inspect
Complete Feature Spec
A public product map with current ownership, access, maturity, and canonical links.
Track
Changelog
Published channel versions separated from development history and source releases.
Contribute
Contribution Guide
Real repository setup, primitive scaffolding, validation, review, and release boundaries.
Start from intent
Use → integrate → authenticate → contribute
Do not begin with an admin panel or an internal release command. Choose the smallest public contract that completes the job.
Use an existing product
Choose VS Code, MCP, Python, CLI, Docker, or web based on the runtime boundary.
02Integrate through a contract
Read the API reference, OpenAPI document, or MCP connection contract before coding.
03Create authenticated access
Sign in before creating an Agent FAI API key or invoking account-scoped workloads.
04Contribute upstream
Work from the public repository, run local validation, and submit a reviewable PR.
Delivery contracts
One ecosystem, different runtime boundaries
Web
Discovery, evidence, documentation, and account-scoped workflows.
VS Code
Native architecture and delivery workbench with local-first catalogs.
MCP
Hosted knowledge or local federation with explicit credential boundaries.
Python
In-process SDK or a separately launched Python MCP server.
CLI
Factory, conformance, release, and MCP federation operator surface.
Docker
Pinnable stdio or HTTP runtime with health and readiness probes.
Open-source development