Skip to main content
Source: packages/oracle-runtime/src/plugins/domain-indexer/

Summary

Domain analysis and entity lookup across the IXO ecosystem — organisations, projects, DAOs, DIDs. Exposes a sub-agent (call_domain_indexer_agent) that searches the IXO Domain Indexer and resolves entity domain cards by DID. Base URL defaults to per-network endpoints (https://domain-indexer{.testnet|.devnet}.ixo.earth) resolved from NETWORK; override with DOMAIN_INDEXER_URL.

Environment variables

What it contributes

  • Tools (inside the sub-agent): domain_indexer_search, get_domain_card.
  • Sub-agents: call_domain_indexer_agent.
  • Middleware: none.
  • HTTP routes: none.
  • Shared state: none.

Opt out / Opt in

When to use it

  • User asks “what is X?” or “tell me about X” for an organisation, project, DAO, or DID.
  • User needs the summary, overview, or FAQ of an IXO entity.
  • Looking up a domain card by its DID.
  • Discovering entities by topic, category, or keyword.

Search filters

domain_indexer_search accepts a filters object that maps directly to the Domain Indexer’s dc.* query parameters. Two of these come from on-chain data and have exact-match semantics you need to know about.

dc.entity_type — exact compound match

The entity_type on each domain card is sourced from the chain type field and stored as a single compound token. It is never split on /, so filter values must match the full compound value: Passing a partial prefix like asset when you want every asset sub-type returns zero results. To match multiple compound types, pass a comma-separated list: dc.entity_type=asset/device,asset/vehicle.

dc.entity_verified — chain-verified status

entity_verified reflects the on-chain entityVerified flag for the entity: null (not-yet-indexed) is distinct from false. Records still awaiting the chain-metadata backfill return entity_verified: null in results and are only excluded when you set the filter to true or false.

Example

When NOT to use it

  • General web search unrelated to IXO entities — use firecrawl.
  • Personal memory or past-conversation recall — use memory.
  • Page editing or workspace pages — use editor. Pages are not entities.

Add a sub-agent

Sub-agent contribution pattern.

Environment variables

All env vars including NETWORK.