Platform API Index
Document ID: API-INDEX-001
File Path: docs/09-api/index.md
Version: 1.1.0
Status: Active
Owner: AI Platform Team
Last Updated: 2026-07-04
1. Purpose
Section titled “1. Purpose”This document is the central navigation and architecture index for the Wovyr AI Platform API — the external REST/gRPC surface through which clients, SDKs, and the dashboard manage agents, workflows, memory, tools, plugins, projects, and users.
The API is fronted by the API Gateway (c4-container §4.1) and is the single, governed front door to the platform.
2. API Surface
Section titled “2. API Surface”Clients (Dashboard / CLI / SDK / external) │ HTTPS (REST) · gRPC · WebSocket ▼ API Gateway ── authn · authz · rate limit · validation · versioning │ ├──► Agents API → Agent Runtime ├──► Workflows API → Workflow Engine ├──► Memory API → Memory Engine ├──► Tools API → Tool Runtime ├──► Plugins API → Plugin Engine ├──► Projects API → Platform Services └──► Users/Auth API → Platform ServicesThe Gateway routes each resource group to the owning subsystem. See C4 Container §4.1.
3. Management API vs. Service Contracts
Section titled “3. Management API vs. Service Contracts”This section documents the management / control-plane API (CRUD + actions on platform resources). Several subsystems also expose a data-plane service contract for high-throughput operations; those are specified in their own sections and referenced here:
| Domain | Management API (this section) | Data-plane contract |
|---|---|---|
| Inference | — | LLM Gateway Provider API |
| Memory | memory.md | Memory Engine API |
| Tools | tools.md | Tool Runtime Execution API |
| Plugins | plugins.md | Plugin Engine |
The management API is for configuring and operating resources; the data-plane contracts are for running them at scale.
4. Document Map
Section titled “4. Document Map”| Document | Responsibility |
|---|---|
| overview.md | API conventions: REST/gRPC, versioning, pagination, errors, idempotency |
| deprecation-policy.md | Breaking-change definition, deprecation window, /v2 parallel-run rule |
| authentication.md | AuthN/Z: OAuth2, JWT, API keys, RBAC scopes |
| agents.md | Agent definitions, runs, sessions |
| workflows.md | Workflow definitions, executions, control |
| memory.md | Memory management (namespaces, records, policy) |
| tools.md | Tool registry + invocation |
| plugins.md | Plugin install, lifecycle, grants |
| projects.md | Organizations, projects, tenants |
| users.md | Users, roles, teams, API keys |
5. Design Principles
Section titled “5. Design Principles”- One front door — all external access goes through the API Gateway.
- Resource-oriented — predictable REST resources with consistent verbs.
- Versioned —
/v1; additive changes are backward compatible. - Secure by default — every request authenticated, authorized, and audited.
- Consistent — shared conventions for pagination, errors, idempotency.
- Dual protocol — REST and gRPC expose equivalent semantics.
- Observable — every call is traced, metered, and rate-limited.
6. Dependencies
Section titled “6. Dependencies”02-architecture/c4-container.md— API Gateway container04-agent-framework/policy-engine.md— authorization01-product/system-overview.md— request flow
7. Related Documents
Section titled “7. Related Documents”09-api/overview.md10-dashboard(planned: consumes this API)11-cli(planned: consumes this API)
8. Revision History
Section titled “8. Revision History”| Version | Date | Description |
|---|---|---|
| 1.1.0 | 2026-07-04 | Added deprecation-policy.md to the document map |
| 1.0.0 | 2026-06-27 | Initial Platform API Index |