Manifests API
The Manifests API provides endpoints for managing team manifests -- declarative configurations that define composable AI teams with versioned components.
What the Manifests API Does
Team manifests follow the "npm for AI agents" paradigm. The API allows you to validate manifest syntax, resolve component versions (dry run), deploy teams from manifests, upgrade components, rollback to previous versions, and export current team state.
Component References
Components use URI-based references:
| Type | Pattern | Example |
|---|---|---|
| Store | store://type/name@version | store://agents/sdr-agent@^1.0.0 |
| Local | local://type/name | local://agents/my-custom-agent |
| External | external://provider/id | external://heygen/avatar-emma |
Version Specifiers
| Specifier | Example | Matches |
|---|---|---|
| Exact | 1.2.3 | Only 1.2.3 |
| Caret | ^1.0.0 | 1.x.x (minor/patch) |
| Tilde | ~1.2.0 | 1.2.x (patch only) |
Deployment Features
- Model alias resolution -- aliases like
claude-sonnet-latestare resolved to concrete model IDs at deploy-time - Authorization grants -- OpenFGA tuples provisioned from manifest declarations (non-fatal if unavailable)
- SPIFFE identity -- agents receive SPIFFE IDs automatically with optional SVID configuration
- Catalog validation -- YAML manifests validated against Zod schemas on load (warn-only)
Error Codes
| Code | Description |
|---|---|
INVALID_MANIFEST | Manifest syntax is invalid |
COMPONENT_NOT_FOUND | Referenced component doesn't exist |
VERSION_NOT_SATISFIABLE | No version matches constraint |
DEPLOYMENT_EXISTS | Team already deployed (use force) |
RESOLUTION_FAILED | Could not resolve all components |
ROLLBACK_FAILED | Target version not available |
LOCKED_COMPONENT | Cannot upgrade locked component |
See Also
- Team Manifests Guide - Manifest format reference
- Avatar Providers - External avatar config
- Store Overview - Browse and install components
- Agent Authorization - OpenFGA authorization details
- Agent Identity - SPIFFE identity system