Register agent identity
FOR AGENTS
Identity. Verify. Transact.
This page is not marketing copy. It states what an agent can use ADI for, which conditions apply, and which machine-readable path names exist on the application host — once that host is published.
Public marketing domain ≠ runtime host
https://adi-hub.ai is the public
presentation and lead site. It does not host agent runtime
endpoints, Agent Cards, A2A mounts, or OpenAPI. Application-host surfaces
are published only with Freigabe / Go-Live — this page lists relative path
names only, never absolute staging or app URLs.
Do not probe /.well-known/*,
/a2a/*, or
/openapi.json on the marketing root —
those paths return 404 there by design.
Create Verify Authorize Transact Audit
CAPABILITIES
What an agent can use ADI for.
ADI exposes identity, trust, and transaction access as a controlled operational surface — on the application host, under policy.
Bind an agent to a business or operator
Work with trust assertions and verification status
Use approved payment capability within policy (pilot for live rails)
Participate in controlled buy and sell flows
Retrieve machine-readable metadata from application-host surfaces (when published)
REQUIREMENTS
What must be true before an agent may transact.
Transaction access is conditional. Discovery alone is not enough.
✓
An agent must be identified before it performs transaction-grade actions.
✓
A business or operator context must be bound.
✓
Policies, limits, and allowed flows must be defined.
✓
A wallet or payment method must be approved (where payment is in scope).
✓
Every transaction must remain inside the approved rules.
ACCESS SURFACES
Where to integrate.
Application-host surfaces are published only with Freigabe / Go-Live — no hostnames or absolute URLs here. Path names below are relative to that future application host, not to adi-hub.ai. MCP endpoints are not listed until shipped scope is confirmed. Trust-Chain URI under the marketing site is a stub until Spec freeze (HTTP 404) — not a machine entry point.
Not published yet. The list shows relative path names only. Do not construct staging or production URLs from this page.
Agent Card
Path only · URL withheld/.well-known/agent-card.json
Public discovery metadata for the platform agent surface.
Per-agent Card
Path only · URL withheld/api/public/agents/{agent_id}/agent-card
Direct metadata lookup for a known agent. Alternate well-known path may exist — confirm stability before hardcoding.
A2A credentials provider
Path only · URL withheld/a2a/credentials_provider
Mounted A2A credential-provider endpoint. Do not treat as production-ready until confirmed.
A2A status
Path only · URL withheld/api/a2a/status
Operational status of the A2A runtime surface.
AP2 status
Path only · URL withheld/api/ap2/status
Operational status of the AP2 payment surface.
OpenAPI
Path only · URL withheld/openapi.json
Schema for REST-adjacent surfaces. Availability depends on the application host release.
Access (OIDC / Keycloak) ≠ trust decisions
OIDC / OAuth / JWT — including ADI-provided Keycloak and relying-party flows — authenticate humans and agents so they can sign in. That is login / access. ADI's trust layer still answers identity binding, delegation, revocation, verification, and audit before transaction-grade action. ADI does not replace the customer's general enterprise IdP as its core product.
More context for humans, less friction for machines.
Businesses get the outcome story. Architects get the layered system. Agents get capability, conditions, and path names for application-host surfaces — with hostnames only after Freigabe.