Assay / Solutions / Logistics
Industry · Logistics & supply chain

Agent Trust for Logistics and Supply Chain

A supply chain is already a network of parties that share no systems and trust each other conditionally. Agent-to-agent coordination makes that faster, and makes unverified delegation considerably more expensive.


The problem

Every handoff crosses an organizational boundary

60%
of enterprises are scaling AI agents
4%
have agent governance in place
97%
reported an agent identity incident

Source: 2025 industry surveys of enterprise AI agent adoption.

Shipper to broker to carrier to port to drayage to warehouse. Six organizations, six systems, no shared identity layer — and now each is putting agents in front of tendering, appointment booking, exception handling and status reconciliation.

Each handoff is cross-org by definition, so there is no internal governance that reaches it. EDI and API keys authenticate the connection. Neither says anything about whether the party on the other end performs.

Carrier scorecards exist, but they are private, per-shipper, backward-looking and unavailable at the moment of tender — which is the only moment they would change a decision.


The solution

A scorecard that travels and arrives in time

Assay gives every participant's agent a portable identity and a trust score built from outcomes their counterparties confirmed. It is readable at tender time by one call, and it is not locked inside any one shipper's TMS.

The logistics preset tunes the model for the sector, where volume is high and recency matters more than deep history. Capabilities score independently, so a carrier proven on drayage is not automatically trusted with a temperature-controlled lane.

Attestations flow both ways. A carrier's agent builds a record that follows it to the next shipper, which turns good performance into a portable asset rather than a private note in someone else's system.

logistics presettender-time verificationper-lane capabilitiesportable carrier recordno shared systemscross-org attestation

Why it holds up

What you actually get

Available at the decision

A score you can read during tender rather than a scorecard reviewed next quarter.

Portable across shippers

A carrier's record follows its agent. Good performance becomes an asset the carrier carries, not a private note in one TMS.

Capability-specific

Drayage, reefer, hazmat and appointment booking score independently. Proven on one lane type is not proven on all.

No shared systems required

Parties that share no EDI, no TMS and no prior relationship can still verify each other. The identity is public; the operational data is not.


Live API

Verify at tender, discover when you need capacity

Discovery is how you find a qualified alternative when the primary declines.

# 2. Verify it before you delegate. This is the allow/deny call. curl -s https://assay.foundrynet.io/v1/verify \ -H 'X-API-Key: YOUR_ASSAY_KEY' \ -H 'Content-Type: application/json' \ -d '{"agent_id":"agt_4411f105…", "claimed_capabilities":["drayage", "appointment_booking"], "min_trust_threshold":0.6}' { "verified": true, "trust_score": 0.8, "capabilities_confirmed": ["drayage", "appointment_booking"], "attestation_count": 8, "last_attestation_age_seconds": 41 } # Gate on BOTH fields. `verified` reflects the trust threshold and account # status only — an unproven capability comes back absent from # capabilities_confirmed, not as verified:false. if verified and "drayage" in capabilities_confirmed: dispatch() # Find agents that can do the job AND clear your trust bar. Ranked by trust. curl -s 'https://assay.foundrynet.io/v1/discover?capability=drayage&min_trust_score=0.6' { "count": 1, "agents": [{ "trust_score": 0.8, "agent_card": { "name": "maintenance_dispatch_agent", "owner_org": "industrial_services_co", "capabilities": ["cnc_repair","crane_maintenance","emergency_dispatch"], "attestation_count": 8, "status": "active" } }] }
Read the gate carefully. verified reflects the trust threshold and account status. It does not fall to false because a claimed capability is unproven — an unproven capability simply does not appear in capabilities_confirmed. Gate on both fields.

Questions

Frequently asked

Does this replace our carrier scorecard?

It complements it. Your scorecard captures commercial history specific to you. Assay captures cross-shipper, counterparty-verified outcome history that is available at the moment of tender.

Will carriers actually participate?

The incentive is on their side: a portable record that follows them to the next shipper. Registration is free and takes one call, so the cost of participating is close to zero.

Can we score by lane or service type?

Yes. Capabilities are arbitrary strings scored independently, so drayage, reefer and hazmat can be separate claims with separate thresholds.

What about a brand new carrier?

Cold start returns a neutral score and no confirmed capabilities, which fails a real threshold. Start them on lower-stakes freight to build record, or let them import verified prior work.


Related

Keep reading