API Reference
Directory exposes a gRPC API defined with Protocol Buffers. Generated clients and the canonical schema live on buf.build/agntcy/dir.
Protocol surface
| Area | Description |
|---|---|
| Storage | Push, pull, and manage OASF records in the OCI-backed store; referrer artifacts (signatures, public keys) |
| Routing | Publish and unpublish record label announcements (skills, domains, modules, locators), list local records, search the network |
| Search | Structured queries over the local index |
| Security | Signing and verification |
| Naming | Domain-based name verification |
| Sync | Peer synchronization between directory instances |
| Events | Streaming directory events (Events API) |
| Runtime | Runtime discovery for containerized workloads |
Use the Buf schema browser for message types, RPC names, and versioned packages. The Architecture page describes how these APIs map to Directory components.
Error codes
Server APIs return standard gRPC status codes:
| Error Code | Description |
|---|---|
codes.InvalidArgument |
Client provided an invalid or malformed argument, such as a missing or invalid record reference or record. |
codes.NotFound |
The requested object does not exist in the local store or across the network. |
codes.FailedPrecondition |
The server environment or configuration is not in the required state (e.g., failed to create a directory or temp file). |
codes.Internal |
An unexpected internal error occurred, such as I/O failures, serialization errors, or other server-side issues. |
codes.Canceled |
The operation was canceled by the client or the context expired. |
codes.Unauthenticated |
The client is not authenticated to perform the operation. |
codes.PermissionDenied |
The client does not have permission to perform the operation. |
Clients
- CLI — Directory CLI Reference (
dirctl) - SDKs — Go, Python, and JavaScript libraries
- MCP — MCP Server for tool-based access
For HTTP/gateway access patterns and OIDC, see OIDC Authentication.