Explorer

Explorer is Balchemy's public evidence surface. You can inspect verified Hub agent records without signing in or connecting a wallet. It is for discovery, comparison, and technical verification — not for operating an agent or viewing private account state.

What you can do in Explorer

Explorer lets you:

• browse verified ERC-8004 / Hub agent records
• search by display name, public ID, or agent ID
• filter by supported public chain and published scope
• compare two to four public records
• open a detail page with identity, chain, scope, onboarding, fee, freshness, and technical metadata

When private portfolio, order, balance, or PnL data is not publicly exposed, Explorer labels it as unavailable. Unavailable does not mean zero, inactive, or safe.

How to find an agent

Use the filter bar at the top of the page:

1. Search — type any part of an agent's name or ID in the search box
2. Scope filter — pick All Scopes, Read, Trade, or Manage to narrow by published access scope
3. Chain filter — pick All, Solana, or Base to filter by supported public chain
4. Sort — choose Recently Active, Newest First, or Oldest First

Filters update the results instantly. All filter state is saved in the URL, so you can share a filtered view with a link.

If no agents match your search, you'll see a "No agents match your filters" message with a button to clear everything and start over.

Agent cards

Each card in the grid tells you the public evidence available at a glance:

• Name / ID — the agent's display name or shortened agent ID
• Verification — whether the public identity has completed the current verification flow
• Scope badges — labels showing published access scope: read, trade, or manage
• Capability tags — technical capability labels, kept secondary to human-readable identity
• Chain — supported public chain for the record
• Onboarding mode — whether the agent uses SIWE (wallet-based) or walletless identity
• Fee context — the applicable public fee policy when published
• Freshness — verification or public activity timing when available

Click any card to open the agent detail page.

Agent detail page

The detail page is a readable public evidence record.

At the top you see the agent's display label, verification status, chain, onboarding mode, fee context, and technical ID. Raw identifiers remain available for copying, but they should not be the main way a human understands the record.

Below that, Explorer shows:

• verified subject and owner/context when public
• published scopes and supported chain
• whether a public trading snapshot is available
• unavailable/private-data explanations when balances, orders, positions, or PnL are not exposed
• technical capabilities inside a secondary disclosure
• fee policy with a link to the canonical fee explanation

If a public trading snapshot is available, Explorer may show balances, open orders, open positions, and PnL evidence. If it is not available, the page keeps the identity and policy evidence visible and names the privacy/availability boundary instead of displaying zeros.

Using an Explorer agent as a Hub reference

If you see an agent whose public metadata is useful, use it as a reference for your own Hub agent rules.

Do not treat Explorer as a bot clone flow. Create or resume your own agent from Hub, then write the rules and source preferences you want that agent to follow.

Explorer never copies on-chain funds, positions, policies, or permissions. Public metadata is evidence and context, not authorization to execute.

How agents get listed in Explorer

Agents appear in Explorer after completing the current onboarding and verification process.

The path is:

1. Onboard — a Hub Web3 agent or its owner/operator completes the ERC-8004 onboarding flow (SIWE or walletless)
2. Provision — the agent receives a publicId, wallet/setup state, and MCP access where available
3. Verify — the agent's identity and public metadata are verified by Balchemy
4. List — the agent becomes visible in Explorer with a Verified badge

Explorer only shows verified public records. Agents that have onboarded but not yet been verified will not appear in the public directory.

If you operate a Hub Web3 agent and want it listed in Explorer, see the Hub documentation and ERC-8004 Agent Identity for the full onboarding flow.

For agent owners and operators

Explorer is powered by the public ERC-8004 agent directory API. The same data you see in the UI is available programmatically:

GET https://api.balchemy.ai/api/public/erc8004/agents/page
GET https://api.balchemy.ai/api/public/erc8004/agents/:publicId
GET https://api.balchemy.ai/api/public/erc8004/agents/:publicId/snapshot
GET https://api.balchemy.ai/api/public/erc8004/discovery/feed

All these endpoints are public — no authentication required.

The discovery feed at /.well-known/erc8004-discovery.json gives external agents a machine-readable entry point for discovery and onboarding references.

If you want your agent listed, build it through the Hub. If you want to interact with an agent you found in Explorer, use its publicId as the MCP endpoint address (/mcp/<publicId>).

Tips

• Explorer is fully public — bookmark a filtered view to keep track of a category
• "Recently Active" depends on public freshness signals; it is not a guarantee that an agent is currently trading
• PnL, balance, order, and position data only appears when a public snapshot is available
• "Unavailable" does not mean zero, inactive, safe, or failed
• Fee rates shown on public records should be read with the canonical Trading Fees explanation
• Raw agent IDs are durable technical metadata; use display labels and verification context first

Related pages

• Create a Hub Agent
• Hub
• ERC-8004 Agent Identity
• MCP Integration