Detailed technical reference for integrators and architects. Concept and pillar pages stay short — field-level detail lives here.
Use this section after Build AI-ready systems when you need field-level schema, MCP, or CLI detail. Published capabilities serve Role Assistants and MCP clients through Operational Trust — not raw vendor APIs.
Schema reference
Integration JSON is validated against Builder schemas (versions from schema metadata.version; re-check after CLI upgrades):
| Document | Schema key | Current version |
|---|---|---|
| External system schema | external-system-schema |
1.17.0 |
| External datasource schema | external-datasource-schema |
2.9.11 |
| Application schema | application-schema |
1.6.2 |
Validate locally:
aifabrix validate <systemKey>
aifabrix validate <path-to-json>
If a cited version disagrees with your installed Builder schema bundle, trust the schema file and update tickets from metadata.version.
Contract reference
- Enterprise MCP reference — Enterprise Knowledge and Role Assistant MCP (same governed pattern), capability keys, datasource selector
CLI reference
- CLI reference — Builder command index (authoritative detail in Builder CLI docs)
API reference
OpenAPI and REST route detail is published from the dataplane after upload. Use aifabrix show <systemKey> --online and the dataplane API docs in your environment for live operation lists — do not treat stale static route tables as source of truth.