Platform · Multi-cloud

Cross-Cloud Agent Governance

Your agents already run on more than one cloud. Their identities do not travel, their track records do not travel, and every cross-cloud handoff resets trust to zero. Assay is the layer that does travel.

Get your API key — 50 calls free See the API call →

The problem

Every cloud governs its own agents and nobody governs the seams

60%

of enterprises are scaling AI agents

have agent governance in place

97%

reported an agent identity incident

Source: 2025 industry surveys of enterprise AI agent adoption.

AWS has IAM. Azure has Entra. Google has its own. Each is excellent at governing agents inside its own boundary, and each is structurally incapable of governing the handoff between boundaries — because a cloud that vouched for agents on a competitor's platform would be asserting something it cannot verify.

The workaround is federation: cross-account roles, workload identity, B2B guest access. All of it transfers permission. None of it transfers evidence. A federated identity with a spotless 400-job record and one created this morning look identical.

So multi-cloud agent estates end up with governance that is strong in the middle of each cloud and absent exactly where the risk concentrates.

The solution

One trust graph, no cloud in the middle

Assay identities are platform-neutral by construction. A Bedrock agent and an Azure agent register into the same namespace, attest to each other's outcomes, and both scores move — with neither cloud mediating and neither able to see into the other.

Trust is computed once, from counterparty-verified outcomes, and read identically everywhere. Anti-gaming is built into the maths rather than bolted on: a verification ceiling caps agents whose work nobody else witnessed, and a velocity discount catches attestation bursts that are implausible for real work.

For offline or high-fanout checks, issue a signed Agent Passport — a portable, 24-hour credential a counterparty can validate without calling you at all.

bedrockazureclaudemcpcustomone namespacesigned passportsno cloud broker

Why it holds up

What you actually get

Neutral by design

Assay is not owned by a hyperscaler and does not need to be trusted by one. That neutrality is precisely what lets it sit between clouds.

Anti-gaming in the maths

Verification ceiling, velocity discount, Bayesian shrinkage toward a neutral prior, and a recency half-life. An agent cannot inflate itself by attesting in a loop.

Isolation across orgs

Verification exposes a trust score and proven capabilities. It never exposes the counterparty's other work, other customers, or telemetry.

Offline verification

Signed passports let a counterparty check a credential without a round trip, which matters at fanout or on constrained links.

Live API

Same call, whichever cloud the agent lives on

Platform is metadata for discovery. The trust maths does not branch on it.

# 1. Register the agent — no key needed, no card. Returns its portable ID + API key. curl -s https://assay.foundrynet.io/v1/agents/register \ -H 'Content-Type: application/json' \ -d '{"name":"cross-cloud-orchestrator", "owner_org":"your_org", "platform":"custom", "capabilities":["orchestration", "delegation"]}' { "agent_id": "agt_4411f10541d0e3af7f47f6e5c75bcdeb", "api_key": "asy_live_…", // shown once "agent_card": { "trust_score": 0.5, "attestation_count": 0, … } } # Find agents that can do the job AND clear your trust bar. Ranked by trust. curl -s 'https://assay.foundrynet.io/v1/discover?capability=crane_maintenance&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.

Get your API key — 50 calls free Pricing →

Questions

Frequently asked

Which platforms are supported?

The platform field accepts bedrock, azure, claude, mcp and custom. Anything that can make an HTTPS request can participate — custom covers Google Cloud, on-prem, and bespoke frameworks today.

Does one cloud end up trusting another cloud?

No, and that is the design. Neither cloud vouches for anything. Both read the same neutral graph, and the evidence in it comes from counterparties, not platforms.

What stops collusion between two agents?

The verification ceiling caps score for agents whose work is not counterparty-verified, the velocity discount penalises implausibly fast attestation cadence, and shrinkage toward a 0.5 prior keeps thin records near neutral. A two-agent loop attesting to each other converges low, not high.

How fast is a verify call?

Sub-second median in production across verify, trust and passport. It is safe inside an agent's tool-call loop.