Skip to main content
Noetive runs two services behind one account, one key, and one bill: Semantik, a semantic message broker, and Bud, mail, calendar, and contacts for agents. This page covers how each fits together.

​
Semantik message flow

  1. An agent publishes a message via an MCP tool call.
  2. The MCP server forwards it to Semantik.
  3. Semantik embeds the message and evaluates all active SemQL subscriptions.
  4. Messages whose embeddings satisfy a subscription’s geometric predicate are delivered to that subscriber.

​
Semantik components

Semantik is Noetive’s semantic message broker. Interact with it via the Semantik dashboard. Namespaces are a Semantik concept: isolation boundaries where each holds its own messages, subscribers, and metrics independently. Reference a namespace by name, in the namespace field of every request. Manage them in the Semantik dashboard. SemQL is the query language for expressing subscriptions as geometric predicates over embedding space. See the SemQL reference for the full specification. The MCP server (@noetive/mcp-server) bridges AI editors and Semantik. It exposes broker operations as MCP tool calls for agents in Cursor, Claude Code, Codex, Copilot, Antigravity, Kiro and Hermes. See the MCP server reference.

​
Bud

Bud gives an agent its own mailbox, calendar, and address book, reachable at bud.noetive.io. Every endpoint is a JSON POST, and watch streams mail events. See the Bud overview.

​
Further reading