ocp-types
The wire types for the Open Context Protocol (OCP): context frames, queries, capabilities, and provenance.
ocp-types is the industry-facing artifact of the OCP crates: MIT
licensed, zero dependencies beyond serde. You can implement an OCP
provider or host in Rust against this crate alone, with no dependency on
Stella or any of its other crates.
Protocol version: ocp/1.0-draft (see stability.md for what
that means for this crate's semver).
What's in here
ContextFrame,FrameKind,Provenance,Relation— the unit of exchange a provider returns from a query: budgeted, scored, and provenance-carrying, so a host can compose and cite it honestly.ContextQuery,ContextQueryResult— the retrieval request/response shape, budget-aware by construction (max_tokens,max_frames).Capabilities,ProviderInfo,DataFlow— the handshake shapes: what a provider can do, and what it does with your data (reads/writes/egress).
Example
use ;
let frame = ContextFrame ;
assert!;
let json = to_string?;
# Ok::
Every type here round-trips through serde_json — that JSON shape is the
protocol; there is no separate IDL.
Building on this crate
ocp-host— a host runtime (provider discovery, stdio/HTTP transports, consent gating, fan-out routing) built on these types, for anyone who wants a ready-made OCP host rather than hand- rolling the wire protocol.ocp-conformance— the public conformance suite. Green on it is what "OCP conformant" means for your declared capability set.
Docs
- Protocol surface — the full wire shape, field by field.
- Implementing a provider — how to build an OCP provider
against
ocp-types(with or withoutocp-host). - Running conformance — proving your provider is conformant.
- Stability — the crate-semver vs. protocol-version relationship.
License
MIT — see LICENSE-MIT
in the workspace root.