Registry Broker API

Name: Registry Broker API API
Brand: Registry Broker API
Availability: InStock

✓ Official Vendor SpecAI/MLEmbeddings Searchnone65 EndpointsREST

For Agents

Search a federated agent registry by keyword or vector, look up agent details by UAID, submit feedback, and inspect routing and federation health.

Connect the Registry Broker API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Registry Broker API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Registry Broker API API.

Run keyword and semantic vector search across the federated agent registry

Query capability-based search to find agents matching a specific intent or skill

Look up an agent's full record by Universal Agent ID (UAID)

Submit feedback for an agent and verify feedback eligibility before posting

GET STARTED

Start building with Registry Broker API API

Explore with Jentic

View OpenAPI Document

Hashgraph Online's Registry Broker exposes public HTTP endpoints for agent discovery and federated registry health. The API lets clients run keyword and semantic vector searches across a federated agent registry, look up agent details by Universal Agent ID (UAID), submit feedback, check eligibility, and inspect health, capabilities, facets, and routing data. It is intended for agent runtimes and integration layers that need to discover registered agents, score them, and route requests across federation peers.

Use Cases

Patterns agents use Registry Broker API API for, with concrete tasks.

★ Agent Discovery for Runtimes

Agent runtimes need to discover capable agents at runtime rather than hard-coding peers. The Registry Broker exposes keyword and vector search so a runtime can submit a natural-language intent and receive a ranked list of matching UAIDs. This makes the federation discoverable instead of static.

POST /api/v1/search with a semantic query 'summarise legal contracts' and return the top 5 UAIDs by score.

Capability-Based Routing

Brokers route work based on declared capabilities. The /api/v1/search/capabilities endpoint accepts a capability spec and returns matching agents, so an orchestrator can pick the right agent per request rather than per session. This supports dynamic federation where capabilities change over time.

POST /api/v1/search/capabilities with capability 'pdf-extract' and return matching agent UAIDs and routing endpoints.

Feedback-Driven Agent Quality

Submitted feedback shapes future ranking. The API supports an eligibility check before submission and a structured POST /api/v1/agents/{uaid}/feedback so noise is filtered from real ratings. Quality signals accumulate per UAID and feed back into search ranking.

Check feedback eligibility for uaid agt_123, then submit a 4-star feedback record for that agent.

Agent Selection via Jentic

An AI orchestrator connected via Jentic picks an agent for an incoming task by hitting the Registry Broker, loading agent details, and choosing by score and feedback. Because the broker is public and unauthenticated for these endpoints, the agent loads the operation schema from Jentic and calls without credential handoff. End-to-end orchestrator-to-agent selection takes under a second.

Search for agents matching the user's intent, fetch agent detail for the top result, and return the routing endpoint.

Key Endpoints

65 endpoints — hashgraph online's registry broker exposes public http endpoints for agent discovery and federated registry health.

METHOD

PATH

DESCRIPTION

GET

/api/v1/search

Keyword search

POST

/api/v1/search

Semantic vector search

POST

/api/v1/search/capabilities

Capability-based search

GET

/api/v1/agents/{uaid}

Agent detail by UAID

POST

/api/v1/agents/{uaid}/feedback

Submit agent feedback

GET

/api/v1/search

Keyword search

POST

/api/v1/search

Semantic vector search

POST

/api/v1/search/capabilities

Capability-based search

GET

/api/v1/agents/{uaid}

Agent detail by UAID

POST

/api/v1/agents/{uaid}/feedback

Submit agent feedback

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The public Registry Broker endpoints declared in this spec require no authentication, so Jentic calls them without any vault credentials. If an operator deploys the broker behind a private gateway, those credentials would be stored in the Jentic vault.

Intent-based discovery

Agents search Jentic by intent (e.g., 'find an agent that can summarise documents') and Jentic returns the matching Registry Broker operation with its input schema, so the agent calls the right discovery endpoint without reading the broker docs.

Time to first call

Direct Registry Broker integration: half a day for path discovery and search payload modelling. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

OpenAI API

LLM API used to interpret search intent before calling the Registry Broker

Choose OpenAI to interpret natural-language requests; pass the resulting intent into the Registry Broker for semantic agent search.

Complementary

Anthropic Messages API

LLM API for orchestrators that select and call agents from the Registry Broker

Choose Anthropic Messages for orchestration logic and let the Registry Broker handle the discovery layer.

Complementary

Render API

Hosting platform that runs registry brokers and federation peers

Choose Render to operate the broker infrastructure; the Registry Broker API itself sits on top of that runtime.

FAQs

Specific to using Registry Broker API API through Jentic.

What authentication does the Registry Broker API use?

The Registry Broker exposes its public discovery endpoints without authentication; no security scheme is declared on these operations. Through Jentic, agents call the public surface directly without holding credentials. Restricted operations require the deploying registry to wire its own auth on top.

Can I run semantic vector search through the Registry Broker?

Yes. POST /api/v1/search accepts a semantic vector search payload that returns ranked UAIDs by similarity. GET /api/v1/search runs keyword search for simpler lookups. Use POST /api/v1/search/capabilities when matching against declared capability tags rather than free text.

What are the rate limits for the Registry Broker API?

The Registry Broker spec does not declare hard rate limits. Treat the public endpoints as moderate-volume; back off on 429 responses. For heavy orchestrator workloads, coordinate with the registry operator on expected traffic.

How do I look up an agent by UAID through Jentic?

Search Jentic for 'lookup agent by uaid', load GET /api/v1/agents/{uaid}, and execute with the UAID. Run pip install jentic and use the async SearchRequest, LoadRequest, ExecutionRequest pattern to retrieve the agent record.

Does the Registry Broker support feedback submission?

Yes. Use POST /api/v1/agents/{uaid}/feedback/eligibility to check whether the caller can submit feedback, then POST /api/v1/agents/{uaid}/feedback with the rating and comment payload. Eligibility checks help filter spam from genuine ratings.