The SDK layer was retired
Protocol v0.7 retired the OGR SDKs — openguardrails on PyPI and
@openguardrails/core on npm — along with everything they existed to wrap:
request signing, enrollment, batching, and the ingest channel all left the
protocol. The Runtime API is the integration
surface.
What an SDK used to do is now one HTTP call: since v0.8 the whole protocol
is POST /v1/evaluate — a GuardEvent
of eight required fields in, a Verdict
out, twice per model call. There is nothing left to serialize, sign, or
batch, so a language binding had nothing left to add. Every plugin this
project ships speaks the API directly.
Where to go instead
- Integrating your own agent — the
quickstart: the complete integration is ~30 lines
of plain
requests/fetch, fail-open by default. - The wire contract — the API reference and the
JSON Schemas (
guard-event,verdict). - Ready-made integrations — plugins for gateways and agent harnesses.
The retired packages remain on PyPI/npm at their last published versions for archaeology, but they speak protocol v0.6 and will not work against a v1.0 runtime. Do not build new integrations on them.