Developer Integration
Connect your local agevidence SDK workflow to managed evidence infrastructure. The console starts where the local SDK stops.
Production
SDK compatibilityPython 0.2.xAlpha
Canonical primitives6Stable narrow waist
Source adapters4 active
Schema extensions required0Adapters integrating without widening the waist
Local — your environment
Connect your SDK
1Install locally
shell
pip install agevidence agevidence doctor
Nothing leaves your environment.
2Prove your mapping
shell
agevidence ingest record.json --format table agevidence explain record.json --format table
Structural validity and provenance, checked offline.
3Export portable evidence
shell
agevidence export record.json > evidence.json
Portable output — usable with or without AgEvidence.
native records → source adapter → primitives → provenance / explain → portable export
Hosted — AgEvidence
Optional managed submission
4Connect AgEvidence
shell
from agevidence import Client client = Client(api_key=os.environ["AGEVIDENCE_API_KEY"])
Optional. The console starts where the local SDK stops.
5Send managed evidence
shell
client.submit("evidence.json")
# → accepted · EV-443 · sha256:8e9f…Portable evidence enters the private hosted graph.
Hosted lifecycle
AcceptedProjectedProfile evaluatedHuman reviewArtifact assembledVerified
Canonical primitives
- SourceRecordA controlled record exactly as the source system holds it.2,412
- ObservationA measured value with unit, method and time.3,184
- SpatialObservationAn observation bound to a geometry or parcel.641
- InterventionEventA deliberate action taken on animals, land or inputs.1,487
- OperationalEventA routine operational occurrence in the production system.512
- ModelRunA deterministic model execution over referenced evidence.176
Hosted operations today
- Events received
- 1,284
- Acceptance rate
- 98.7%
- Open schema errors
- 12
- Webhooks failing
- 1
- Rust verifier
- Connected
agevidence-verify 0.4.1
Hosted submission is optional — portable evidence stands alone.