agent-readiness-insights-protocol
Shared schema, dataclasses, and version constants for the agent-readiness insights ecosystem.
This is a tiny PyPI package that defines the contract between three independent consumers of the insights system:
| Consumer | Repo |
|---|---|
| OSS rule pack | agent-readiness-rules |
| Public scanner | agent-readiness |
| Closed insights engine | (private) |
Splitting the protocol out keeps each consumer honest about the contract,
lets either side iterate behind versioned interfaces, and means the engine
never has to install the full agent-readiness runtime to deserialize
a JSON response.
Install
pip install agent-readiness-insights-protocol
Pydantic is the only runtime dependency.
What's inside
- Dataclasses —
Rule,Insight,SearchHit,EvaluateRequest,EvaluateResponse,HealthResponse. Allpydantic.BaseModelsubclasses with strict JSON serializers. - Version constants — two independent integers:
PROTOCOL_VERSION— JSON shapes for/evaluate,/insights/search,/healthz.RULES_VERSION— YAML rule schema (match types, required fields).
- JSON Schema export —
schemas/rule.schema.jsonis generated bytools/export_schema.pyand committed so any consumer's CI can validate YAML rule files without importing Python.
Versioning rules
Bump only on breaking changes. Adding optional fields is non-breaking
and does NOT bump either version (mirrors the existing convention in
agent-readiness/src/agent_readiness/models.py).
The engine's /healthz reports both versions:
{
"protocol_version": 1,
"rules_version_supported": [1],
"rules_pack_version_loaded": "1.0.0",
"engine_version": "0.1.0"
}
A client refuses to call when protocol_version mismatches; logs a warning
when a rules version it doesn't recognise appears.
Usage
from agent_readiness_insights_protocol import (
PROTOCOL_VERSION,
RULES_VERSION,
Rule,
EvaluateRequest,
EvaluateResponse,
)
req = EvaluateRequest(repo_path="/path/to/repo", with_insights=True)
print(req.model_dump_json())
Develop
make dev # pip install -e ".[dev]"
make test # pytest
make lint # ruff check
make schema # regenerate schemas/rule.schema.json
make build # build wheel + sdist
License
MIT
Metadata
Release files for agent-readiness-insights-protocol 0.12.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| agent_readiness_insights_protocol-0.12.0.tar.gz | 87.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| agent_readiness_insights_protocol-0.12.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 121.9 kB
Release files / agent_readiness_insights_protocol-0.12.0.tar.gz
| Download URL | agent_readiness_insights_protocol-0.12.0.tar.gz |
|---|---|
| Size | 87.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ac86e00045ea97d3ae1b3b3c2454940d6f868800e2433f54124e1b632991d2a1
|
|
BLAKE2b-256 checksum How to use checksums |
ae17054e46d3f0cca3b8fbc52e655cf0b6607c3e5073546f07db02744421f57a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 28, 2026.
Transparency logRelease files / agent_readiness_insights_protocol-0.12.0-py3-none-any.whl
| Download URL | agent_readiness_insights_protocol-0.12.0-py3-none-any.whl |
|---|---|
| Size | 34.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fc02a89bfdb72314e9a0419ce45bd40b6280faaff54901b55fbd65e2ba606646
|
|
BLAKE2b-256 checksum How to use checksums |
89a368519b217076d13d92bdc371424860b4eb9cc19c4edb784072884d849e02
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 28, 2026.
Transparency log