By FLINT Network
Cross-Domain Agent Identity: What Survives the Border
Portable agent identity is shipping. Cross-domain acceptance still depends on the issuer, the current mandate, the exact tool, and the relying party's policy.
The Short Version
A cross-domain agent credential carries verifiable claims from one system to another. The receiving system checks the issuer, signature, subject, lifecycle, and claims, then applies its own policy. Portability makes verification possible. It does not guarantee acceptance.
The market moved fast in 2026. DigiCert now offers a portable AI Passport with policy-based visas and runtime enforcement. Postman Passport binds API access to a holder. Workday announced Agent Passport for enterprise agent testing and monitoring. The open problem has narrowed from whether agent identity can travel to how a relying party evaluates that identity at a consequential action.
The Passport Category Is Crowded
DigiCert's September release changed the competitive claim. Its AI Passport is designed to travel across organizations, connect an agent to an accountable owner, carry policy-based permissions, support runtime enforcement, and revoke authority. Postman uses the passport label for secure API access. Workday announced its own product with early access planned for the second half of 2026. Microsoft and AWS govern agent identity inside their platforms.
No credible FLINT position can rest on owning the word passport or being the only cross-domain issuer. The differentiator has to be a measurable control: what the system verifies immediately before an action, how it binds the exact tool version, what decision it returns, and what evidence survives execution.
Four Questions at the Border
- Identity Which agent and accountable principal are presenting this request, and which issuer supports that claim?
- Authority Does the current mandate allow this action, amount, counterparty, destination, and time window?
- Tool integrity Is the agent using the exact assessed tool or skill version that was approved, or did the artifact change?
- Outcome What executed after the decision, and can an auditor link the result to the same agent, tool, assignment, and policy?
A portable identity can answer the first question. It can carry evidence for the second. The third and fourth require controls at the invocation and execution boundaries.
Issuer Trust Is Policy, Not Physics
A relying party may trust a platform issuer, a security vendor, a customer-operated issuer, a neutral third party, or several issuers under different conditions. The choice depends on assurance, incentives, auditability, revocation, and the cost of a bad decision.
Neutral issuance can reduce dependence on one platform and make cross-rail evidence easier to compare. Platform issuance can carry stronger first-party knowledge of the workload and owner. A sound architecture can compose both instead of pretending one issuer model fits every transaction.
What a Cross-Domain Credential Needs
A relying party needs enough information to verify the credential and make a separate action decision.
- Verifiable issuer The verifier can authenticate the issuer, signature, and verification material and can decide whether that issuer is trusted for this purpose.
- Composition, not reinvention NIST's agent-identity initiative favors adapting existing identity and authorization standards. Portable credentials should carry compatible evidence instead of replacing OAuth, SPIFFE, workload identity, or signed agent metadata.
- Pairwise identifiers The issuer and verifier minimize correlatable identifiers and disclose only the attributes needed for the requested action.
- Fresh authority The action is checked against the current mandate, policy, and credential lifecycle instead of inheriting permanent authority from an identity document.
- Signed, retained evidence The decision can be retained and verified later, with separate outcome evidence when the action executes.
- Lifecycle The verifier checks expiration, renewal, suspension, revocation, and the active credential version.
Where FLINT Fits Now
FLINT issues hybrid-signed Agent Passports and uses them as durable identity and reputation anchors. FLINT Verify evaluates a specific transaction across 6 evidence categories and emits a signed four-state verdict. A Passport strengthens that check but does not guarantee ALLOW.
FLINT Command is in managed design partnership, not self-serve release. Its current bounded workflow connects an accountable owner, active mandate, exact assessed tool version, assignment, and policy. The gateway records ALLOW or BLOCK, then records the execution outcome separately. That is the sharper September position: identity travels, authority expires, software changes, and evidence must link all 3 facts.
Cross-domain identity is shipping. The harder control is binding that identity to current authority, an approved software version, a decision at the gateway, and a signed outcome after execution.
Primary Sources
Related Academy Briefs
Get in touch
If you are building on agentic payment rails and want to talk through how FLINT fits your stack, reach out directly.
contact@flint.network