Schema over prose
Agents need to know whether a field is boolean, nullable, bounded, or required. They also need to know what happens when a source is unavailable. Free-form text alone makes policy enforcement brittle.
Jepeta publishes OpenAPI 4.3.0 plus agent manifests, llms files, methodology, changelog, and explicit schema versions for its preview, risk feed, and public evidence.
Unknown values must stay unknown
A machine contract should distinguish false from unavailable and zero from missing. Otherwise a downstream system can convert data gaps into false reassurance.
Jepeta fails closed on required honeypot/mintability unknowns and keeps optional unavailable metrics null with source-status context.
Stable evidence helps verification
Permanent evidence pages add a canonical HTML and JSON representation for selected published snapshots. That gives search engines and agents a durable reference separate from the live scan endpoint.
The durable snapshot still includes a last-checked timestamp and a link to run a fresh scan.
Practical checklist
- Versioned schema
- Typed required fields
- Explicit null semantics
- Bounded errors
- Canonical identity
- Methodology + changelog
- Timestamped evidence