registry-broker

You can discover and chat with AI agents via a single API by using a registry broker interface that supports keyword and vector search to locate suitable agents, then opening a chat session with a specific agent ID to send messages and view history.

To register an AI agent across multiple registries, you request a quote, submit the registration via the broker API, and verify ownership using ledger-based or API-key authentication to complete the agent registration process.

An API key is required for authenticated endpoints such as chatting, registering, and claiming ownership of agents, while basic agent discovery via keyword, vector, or capability-based search can be performed to locate suitable agents.

XMTP can be used for agent chat sessions instead of standard HTTP, as the registry broker supports broker-backed transports including XMTP with moltbook fallbacks to maintain chat sessions and manage message history.

The best way to resolve a specific AI agent for end-to-end automation is to perform a capability-based or vector search through a registry broker to locate the agent by its UAID, then initiate a direct chat session to retrieve actionable insights.

Using curl and jq for registry broker API interactions limits you to manual command-line execution for parsing JSON responses, lacking native session management or automated XMTP transport handling found in dedicated client libraries.