Assay × Supply Chain, Verified Supplier Intelligence

The use case

Two independent signals, not one

A supplier's agent reports its line is healthy and on schedule. Taken alone, that's a claim from a party with an incentive to make it. Split it into two independent signals: Forge reads the actual equipment condition from the machines, and Assay scores the credibility of the agent doing the reporting. Commit to the production schedule only when both agree, the equipment is healthy and the reporter has earned the right to be believed.

Integration flow

Two signals, one decision

Signal 1 · Forge

Equipment condition

What the machines are actually doing, read from telemetry, not asserted.

Signal 2 · Assay

Reporter credibility

Whether the agent reporting that condition has a verified track record.

STEP 1

Read equipment condition Forge fleet_health

Ask Forge for the supplier's fleet health directly from the equipment layer.

forge-fleet-health.sh

# Forge, supplier fleet health (forge_sandbox_ key evaluates free)
curl -s https://forge.foundrynet.io/v1/fleet_health \
  -H "Authorization: Bearer forge_sandbox_…" \
  -H "Content-Type: application/json" \
  -d '{ "machines": [ { "machine_id": "line-3-cnc",
       "canonical_field": "spindle_load_pct",
       "time_series": [60,62,63,64,66,68,70,71,73,74,76,78,80,82,84,86],
       "threshold": 95 } ] }'

# -> 200, equipment signal
{ "fleet_summary": { "healthy": true } }

STEP 2

Verify the monitoring agent POST /v1/verify

Confirm the agent that produced that report is credible, active, above your trust threshold, and evidenced on the capability that matters.

assay-verify.sh

# Assay, reporter credibility signal
curl -s https://assay.foundrynet.io/v1/verify \
  -H "X-API-Key: $ASSAY_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "agent_id": "agt_supplier...",
       "claimed_capabilities": ["condition_monitoring"],
       "min_trust_threshold": 0.75 }'

# -> 200
{ "verified": true, "trust_score": 0.82,
  "capabilities_confirmed": ["condition_monitoring"] }

STEP 3

Require both to agree

Two independent signals: fleet_summary.healthy == true AND verify.verified == true. Either one alone is a claim; together they're a decision you can defend.

STEP 4

Commit to the schedule with confidence

Green on both, commit the production schedule. Keep the Forge reading and the supplier's signed Assay passport (GET /v1/agents/:id/passport) together as the record of why you committed.

Try it now

Wire both signals in two minutes

Assay registration is free (first 50 calls), and Forge equipment tools evaluate free on a forge_sandbox_ key. Run fleet_health and verify side by side.

quickstart.sh

# Assay key (free) for the credibility signal
curl -s https://assay.foundrynet.io/v1/agents/register \
  -H "Content-Type: application/json" \
  -d '{ "name": "supply-chain-agent", "owner_org": "your-co",
       "capabilities": ["sourcing"] }'

# Forge sandbox key (free) for the equipment signal:
# https://forge.foundrynet.io/pricing
export ASSAY_KEY="aid_…"

Get your free Assay key → Forge sandbox key