AWS Bedrock integration

Industrial Agent Trust for Bedrock

Your Bedrock agent already uses Forge for equipment data through AgentCore Gateway. Assay adds the trust layer: verify the agents yours coordinates with, and build a verified track record for your own agent that travels to any platform.

The use case

When would a Bedrock agent need Assay?

Forge tells your Bedrock agent what the equipment is doing. Assay tells it who to trust. When your agent coordinates with a technician agent, a supplier agent, or a peer on another platform, it needs one portable way to check their record, and to carry its own. Register once for a platform-neutral identity, verify before you delegate, attest every outcome, and hand out a signed passport so other platforms trust your agent without re-litigating its history.
Integration flow

Five steps against the live APIs

STEP 1

Give your Bedrock agent a portable identity POST /v1/agents/register

One identity that isn't tied to Bedrock. Trust starts at a neutral 0.5 and is earned from outcomes.

register.sh
curl -s https://assay.foundrynet.io/v1/agents/register \
  -H "Content-Type: application/json" \
  -d '{ "name": "bedrock-maint-agent", "owner_org": "your-co",
       "platform": "bedrock",
       "capabilities": ["diagnostics","scheduling"] }'

# -> 200, keep api_key secret
{ "agent_id": "agt_5aa1...", "api_key": "aid_…" }
STEP 2

Use Forge for equipment intelligence AgentCore Gateway

Your agent keeps calling Forge tools (normalize, predict, fleet_health) through the AgentCore Gateway for the equipment layer. Assay sits alongside as the trust layer, the two are complementary, not coupled.

forge-via-mcp.sh
# Forge over MCP (equipment data), a forge_sandbox_ key evaluates free
claude mcp add --transport http forge https://mcp.foundrynet.io/mcp \
  --header "Authorization: Bearer forge_sandbox_…"
STEP 3

Verify agents before coordinating POST /v1/verify

Before delegating to another agent, on any platform, check its trust and confirm its claimed capabilities in one call.

verify.sh
curl -s https://assay.foundrynet.io/v1/verify \
  -H "X-API-Key: $ASSAY_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "agent_id": "agt_partner...",
       "claimed_capabilities": ["field_repair"],
       "min_trust_threshold": 0.7 }'

# -> 200
{ "verified": true, "trust_score": 0.78 }
STEP 4

Build your own track record POST /v1/agents/:id/attest

After your agent completes work, attest the outcome. Every success (and honest failure) shapes the trust other platforms will read.

attest.sh
curl -s https://assay.foundrynet.io/v1/agents/agt_5aa1.../attest \
  -H "X-API-Key: $ASSAY_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "task_type": "diagnostics", "outcome": "success",
       "first_fix": true }'

# -> 200
{ "attestation_id": "att_a70c...", "updated_trust_score": 0.6 }
STEP 5

Share your credentials GET /v1/agents/:id/passport

Hand other platforms a signed passport instead of asking them to trust your word. It carries identity, verified capabilities, and score, signed and refreshed daily.

passport.sh
curl -s https://assay.foundrynet.io/v1/agents/agt_5aa1.../passport

# -> 200, portable, signed, free
{ "agent_id": "agt_5aa1...", "trust_score": 0.6,
  "capabilities_verified": { "diagnostics": 0.6 },
  "issuer": "assay.foundrynet.io", "signature": "a1b2c3..." }
Try it now

Register your Bedrock agent in two minutes

Registration is open and your first 50 Assay calls are free; Forge equipment tools evaluate free on a forge_sandbox_ key. Wire both, then run verify → attest → passport.

quickstart.sh
# Assay identity (free)
curl -s https://assay.foundrynet.io/v1/agents/register \
  -H "Content-Type: application/json" \
  -d '{ "name": "bedrock-agent", "owner_org": "your-co",
       "platform": "bedrock", "capabilities": ["diagnostics"] }'

# Forge equipment tools (free sandbox key at forge.foundrynet.io/pricing)
export ASSAY_KEY="aid_…"

Get your free Assay key →   Forge sandbox key