# JD Codec

> Compress browser-agent perception streams ~80%+ via a stateful, lossy cloud codec — with on-device PII redaction.

## Docs

- [Liveness probe with codec build identifier](https://jdcodec.com/docs/api-reference/health/liveness-probe-with-codec-build-identifier.md): Returns the service liveness status and the current codec build identifier. The build identifier matches the `X-JDC-Codec-Version` header on every snapshot response, so monitoring tools can detect deploys by polling this endpoint.
- [Submit one snapshot for compression](https://jdcodec.com/docs/api-reference/snapshot/submit-one-snapshot-for-compression.md): Submit one already-redacted snapshot to the codec service. The response carries the compressed output the connector should splice into its agent's tool response in place of the original `snapshot_yaml`.
- [Privacy posture](https://jdcodec.com/docs/concepts/privacy-posture.md): What stays local, what reaches the cloud, what's never persisted.
- [Sessions, tasks, and steps](https://jdcodec.com/docs/concepts/sessions-tasks-steps.md): The unit framing JD Codec uses — what each one means for your usage and billing, with a concrete example.
- [What is JD Codec?](https://jdcodec.com/docs/concepts/what-is-jdcodec.md): The codec, the connector, the cloud — what each piece does and why.
- [JD Codec](https://jdcodec.com/docs/index.md): Compress browser-agent perception streams ~80%+ via a stateful, lossy cloud codec — with on-device PII redaction.
- [Quickstart](https://jdcodec.com/docs/quickstart.md): Install the connector, get an API key, see your first compression event. ~5 minutes.

## OpenAPI Specs

- [openapi](https://jdcodec.com/docs/openapi.yaml)