ADI
Closed Beta

SECURE IDENTITY HUB

Closed beta is open for companies and people who want to build and test agent commerce with us.

The trust layer for agentic commerce.

ADI gives organizations identity, credential issuance, signatures, verification, revocation, auditability, and delegated card issuing for trusted agent flows — so agents can buy and sell under explicit control.

ADI is the trust and payment control layer for agent commerce — with OIDC (Keycloak) and relying-party flows so humans and agents can sign in and verify each other safely.

Identity Credentials Verification Revocation Audit Controlled issuing
Trust layer Payment control Agent card issuing

DUAL PORTAL

One trust layer. Two operational portals.

ADI is built as a dual portal: buyers govern what agents may spend and with whom; merchants present trust evidence for what agents may sell. Same control plane — different jobs.

Buyer portal

For buying organizations

Define purchase rules, approvals, limits, approved merchants, and issuing boundaries for agents that act on your behalf. Every transaction stays attributable and auditable.

Who it's for: SMBs, buying ops, procurement teams that need agents without uncontrolled spend.

Merchant portal

For merchants and digital sellers

Expose trust evidence — organization binding, catalog governance, and acceptance controls — so external buyer agents can verify you before money moves. Shop connectors feed the trust layer; they are not the trust layer.

Who it's for: Merchants whose agents sell or accept agent-initiated commerce.

WHAT ADI CONTROLS

What the trust layer must answer before an agent may act.

Discovery alone is not enough. ADI operationalizes the questions that remain after AgentCard plus OAuth.

Business identity

The agent is bound to an operator, tenant, or organization — not an anonymous endpoint.

Credentials & signatures

Issuance and verification of credentials and signatures that prove who authorized what, for how long.

Verification & revocation

Proofs can be checked; authority can be stopped. Status and policy stay inspectable.

Auditability

Actions remain attributable: who acted, under which mandate, within which limits.

Delegated card issuing

When payment capability is required, ADI can assign controlled virtual cards to specific agents — so policy, limits, and mandates actually reach the payment rail.

Example · Control instrument

CARDS FOR AGENTS

ADI issues cards for agents — business and consumer.

ADI issues cards for agents — business and consumer. Each card carries identity, limits, merchant scope, and mandates so spend stays under your control. Join closed beta to test issuing and trust control with us.

Business issuing

Dedicated instruments for buyer agents under policy, limits, and merchant scope — in closed beta with selected companies.

Consumer issuing

The same control model for consumer-facing agent payments — issue bounded cards your customers' agents can actually use. Available in closed beta.

Control travels with the charge

Identity, limits, scope, and AP2 mandates stay attached — so every spend stays attributable and auditable.

Core limits sit on the card. Markers open deeper control context · sample data

Bounded

Procurement agent

Monthly limit

2,000 EUR

Remaining

1,480 EUR

Office SaaS Approved merchants

Sample data — illustrative. ADI issues cards for agents (business and consumer). Join closed beta to try it with us. Request closed beta access.

HOW IT WORKS FOR BUSINESSES

A clear business workflow from identity to paid settlement.

ADI connects identity, approvals, payment capability, and controlled execution in one operational flow.

01

Create the agent

Set up a buying, sales, or service agent for your business.

02

Confirm identity

Bind the agent to a verifiable business or operator context.

03

Set rules and limits

Define where it may buy or sell, with whom, and within which budget.

04

Operate under control

The agent acts inside the approved scope; actions stay traceable.

INTERNATIONAL ECOSYSTEM

Built for a growing agent commerce environment.

ADI connects open agent protocols and partner payment rails into one controllable trust and issuing layer for real commerce.

Google AP2A2AStripeAttrianOIDC / Agent Login (Keycloak)

WHO THIS IS FOR

For companies that want agents to do more than talk.

ADI becomes relevant when agents buy, sell, request, approve, or represent your business in real transactions.

SMBs with little time

You want a governed business agent that can act — with identity, limits, and cards ready for closed-beta testing.

Buying and operations teams

Agents help with procurement and operational tasks without becoming uncontrolled spenders.

Digital sellers and merchants

Agents trigger real commercial activity with trust evidence buyers can verify — not chat-only API wrappers.

Give your agents identity, trust control, and bounded payment capability.

The business path stays simple. Architecture and agent paths stay available when you need depth.

CLOSED BETA

ADI is in closed beta — request access to test with us.

Join ADI closed beta. Tell us your use case — we onboard companies and people who want to test agent identity, trust control, and card issuing with us.