Platform Coverage

Embed's current Console algorithm builder covers prediction markets, DEX and wallet activity, token items, Hyperliquid, and notification candidate streams.

The product surface today is search plus hydration. Users pick an index, filter candidates, hydrate result rows, sort them, and return output for a feed or notification config. Separate Features, Scoring, and Ranking pages are hidden because those are not Console steps today.

Current Console coverage

Platform or domain	Current indices	Primary workflows
Polymarket	`polymarket-items`, `polymarket-trades`, `polymarket-wallets`, `polymarket-notifications`	Market feeds, wallet/trader feeds, market or wallet notifications.
Hyperliquid	`hyperliquid-items`, `hyperliquid-trades`, `hyperliquid-wallets`, `hyperliquid-notifications`	Perps/activity feeds, wallet monitoring, notifications.
DEX activity	`base-trades`, `ethereum-trades`, `solana-trades`, `dex-notifications`	Chain-specific trade feeds and DEX notification candidates.
Tokens and coins	`token-items`	Token discovery feeds and market-cap or volume based feeds.
Wallet profiles	`wallet-users`, `hyperliquid-wallets`, `polymarket-wallets`	User or wallet profile feeds and account-owned joins.
Kalshi notifications	`kalshi-notifications`	Kalshi notification candidates.

Feed algorithms

Feeds use item, trade, token, or wallet indices. A typical feed algorithm searches one index, applies filters, hydrates rows, sorts results, and returns them.

const rows = await mbd
  .search()
  .index("token-items")
  .include()
  .numeric("zora_market_cap", 10000)
  .sortBy("zora_market_cap_delta_24h", "desc")
  .size(30)
  .execute();

Notification algorithms

Notifications use notification indices and account-owned user or wallet joins when delivery is user-specific.

const candidates = await mbd
  .search()
  .index("hyperliquid-notifications")
  .include()
  .inAppUsers("wallet_address")
  .sortBy("timestamp", "desc")
  .size(50)
  .execute();

Data-source coverage

For private data, create a Data Source in Console and ingest users, items, and interactions through the Datasources. Those records can be used by Console workflows and by account-scoped joins such as in_app_users.

See Data Sources and Supported Indices.