Evidence your systems can read.
Procurement, ERP, forwarding and underwriting systems should not need to scrape a PDF. The API model exposes deterministic quotes, canonical records, commitments, anchors and revocation state.
Resource-oriented, versioned and explicit
| Method | Path | Purpose |
|---|---|---|
| POST | /v2/quotes | Deterministic indicative fee from published rules |
| POST | /v2/units | Submit a canonical batch evidence record |
| GET | /v2/units/{unit_id} | Read grade, method, commitment and status |
| POST | /v2/anchors | Request inclusion in the next daily root |
| GET | /v2/anchors/{id} | Retrieve Merkle path and public timestamp proof |
| POST | /v2/shipments | Bind plot, batch, container and transport evidence |
| POST | /v2/autograde/batches | Grade signed telemetry or return ABSTAIN |
| POST | /v2/units/{id}/revoke | Append a visible revocation with reason |
| GET | /v2/registry/export | Export the authorised registry state for audit |
Reference interface. Production base URL, credentials, availability and tenant scopes are provided only under an executed agreement. Public verification does not require an API key.
Keys are not the root of trust
API credentials control who may submit. Public SHA-256 commitments and time anchors control whether a published record can be independently checked.
A leaked key must never permit silent history rewriting. Revocation and version changes are new events.
A record is a portable object
Canonical serialisation and proof paths are defined in the method, not hidden in application code.
Start where your records already live
Forwarder / broker
Shipment intake, pack status and exportable filing fields.
ERP / agri-platform
Turn existing batch and meter records into evidence units.
Buyer procurement
Pull supplier grade, exceptions and revocation state.
Finance / insurance
Read evidence quality without asking for a favourable decision.