Glossary

Algorithm: JavaScript/DSL function that searches one supported index, hydrates rows, filters or sorts candidates, and returns output.

Candidate: A row returned by search before the app renders it as a feed item or delivers it as a notification.

Console: The Embed web app at https://console.mbd.xyz.

Data Source: Account-owned users, items, and interactions ingested into Embed for private workflows.

Delivery Config: Notification config that attaches deployed algorithms to webhook delivery, cooldowns, priority filters, and daily budgets.

Feed Config: Config that combines one or more deployed algorithms and serves feed output.

Hydration: Enriching search hits with row fields by calling .include() in the algorithm.

Ingestion: The data-prep workflow for bringing users, wallets, items, or interactions into Embed. In Notifications, ingestion prepares the account-owned audience/context that algorithms join against.

In-App Users: Account-owned users or wallets that can be matched from an algorithm with .inAppUsers(field).

Notification Algorithm: Algorithm that searches a notification index such as dex-notifications, hyperliquid-notifications, polymarket-notifications, or kalshi-notifications.

Notification Delivery: The webhook side of notification setup. Delivery receives matched candidates from selected deployed algorithms.

Search Index: A named collection available in Console's algo dropdown, such as polymarket-items, token-items, wallet-users, or dex-notifications.

Studio API: Public API surface at https://api.mbd.xyz/v3/studio.

Webhook: Your HTTP endpoint that receives notification payloads from a delivery config.