When you get a freight rate estimate from Freight Rate Intelligence, it comes with proof — not promises.
Most freight data tools give you a number and ask you to trust it. You don't know where the data came from, when it was last updated, or whether anything was modified.
Freight Rate Intelligence works differently. Every rate estimate, every diesel price, every cost breakdown comes with a constitutional receipt — a verifiable record proving exactly where the data originated, when it was fetched, and that nothing changed along the way.
If your CFO asks "where did this $2,847 rate estimate come from?" — you hand them the receipt. It shows the EIA diesel price used, the BLS labor rate, the DOE fuel surcharge formula applied, and the exact model version that produced the estimate.
No black box. No "trust us." Verifiable.
AI is becoming the default interface for business decisions. Procurement teams ask AI for freight rates. Supply chain agents call APIs to optimize routing. Financial models ingest AI-generated data for budgeting.
But most AI tools generate answers with no provenance. You cannot verify where the data came from. You cannot confirm whether it was hallucinated, interpolated, or sourced from a real dataset.
This is not a theoretical risk. When a freight rate estimate drives a $2 million logistics budget, "the AI said so" is not an acceptable audit trail.
Every rate estimate you receive can be verified back to its government data sources. When your finance team, auditor, or trading partner asks where a number came from, the receipt answers with evidence — not explanation.
When an orchestration agent calls the Freight Rate Intelligence API, the response includes a receipt proving data lineage. The agent can evaluate trustworthiness before incorporating it into downstream decisions. No other freight data API provides this.
The EU AI Act (effective August 2026) requires organizations to demonstrate the provenance of AI-generated outputs used in business decisions. Constitutional receipts provide exactly this evidence — automatically, with every request.
| Capability | Typical Freight API | Freight Rate Intelligence |
|---|---|---|
| Data source transparency | Black box. "Trust us." | Every source named, linked, dated. |
| Audit trail | API logs (mutable, deletable) | Immutable receipt chain. Tamper-evident. |
| Confidence scoring | None or self-assessed | Data-freshness-driven, per-estimate |
| Attribution lineage | Not tracked | Full chain from source to output |
| Agent trust evaluation | Agent must trust blindly | Agent verifies provenance before use |
| Regulatory readiness | Manual documentation if audited | Machine-readable compliance evidence |
A constitutional receipt is a verifiable record generated every time Freight Rate Intelligence produces a result. It captures the data sources used, when they were fetched, the model that processed them, and a confidence score. The receipt is immutable — once created, it cannot be changed or deleted. Think of it as a bank statement for your freight data.
Because the governance rules are embedded in the system's architecture, not applied after the fact. Just as a constitution defines the rules a government must follow before it acts, constitutional receipts enforce data integrity rules before a result is produced.
Yes. Every receipt includes links to the original government data sources (EIA, BLS, DOE). You can check the diesel price, labor rate, or fuel surcharge formula yourself.
No. Receipt generation adds less than 5 milliseconds to each request. The governance is embedded in the execution path, not bolted on.
The EU AI Act (effective August 2026) requires organizations using AI in business decisions to demonstrate data provenance and model transparency. Constitutional receipts provide exactly the evidence regulators require.
You care about it the same way you care that your bank shows you where every charge came from. When your CFO questions a freight budget number, when a carrier disputes a benchmark, or when an auditor asks how you arrived at a rate — the receipt is there.
No. Constitutional receipts use cryptographic hashing and append-only audit logs to achieve the same integrity guarantees — without the overhead.
Yes. Every API response includes a receipt_id and auth_obj_id. Agents can use these to verify the provenance chain before incorporating data into their outputs.