← Agent catalogue
MERCURY

Preview portrait

Integration

MERCURY

Growth intelligence adjacent to read models and outbound paths; message send remains NUNTIUS; orchestration remains ATLAS.

LiveCatalogue status
AdvisoryRuntime posture

Marketing and growth intelligence: tenant-scoped MERCURY domain agent — pairs with the Marketing OS module (Prisma `Marketing*` models, `/console/marketing`, marketing APIs) for campaigns, content, and signals; topology node remains the integration anchor.

  • MERCURY
  • Growth
  • Marketing module
Open product storyOpen consoleBook a Demo

Expanded capabilities

  • Compose tenant-scoped marketing posture from campaigns, content, and channel signals
  • Surface growth narratives and campaign-aligned opportunities without inventing missing data
  • Hand off demand context to AUCTOR and Growth Command with explicit provenance
  • Pin RECORD_ONLY findings for operators when posture needs attention
  • Respect Marketing OS entitlements, RBAC, and approval gates on mutating paths

How they learn & improve

MERCURY improves when operators confirm which signals mattered — campaign outcomes, rejected drafts, and approved collaboration plans become learning candidates, never silent channel changes.

  1. Observe campaign and channel posture with source-health metadata (missing stays missing).
  2. Propose RECORD_ONLY learning candidates or draft multi-agent plans for human review.
  3. Absorb approved feedback and standing-grant ceilings on the next observe cycle — never auto-send.

How they work together

MERCURY sits on the commercial intelligence plane: it feeds AUCTOR and Growth Command, borrows STRATA signals, and stays outbound-safe behind NUNTIUS approvals.

  • AUCTORPasses demand-to-pipeline handoffs so sales sees marketing context without rework.
  • ATLASReceives ATLAS classification so growth work stays on the Golden Path.
  • NUNTIUSNever sends; any outreach still requires human-gated messaging approval.
  • STRATA (strategic signals)Uses strategic signals to prioritise campaigns operators should inspect.
  • Marketing OS (MERCURY module surface)Shares governed context with Marketing OS (MERCURY module surface) so operators see one coherent path instead of conflicting module stories.

Practical benefits

  • Campaign health without guessworkOperators see which channels are live vs missing connectors — so they fix wiring instead of chasing fake KPIs.
  • Marketing → sales handoffA governed collaboration plan drafts the MERCURY↔AUCTOR observe steps; humans approve before anything executes.
  • Learning from rejected creativesRejected drafts become REVIEWABLE learning candidates, tightening future recommendations without publishing on their own.

Learning and improvement stay human-visible: candidates are RECORD_ONLY until an operator reviews and applies them. Sensitive sends, publishes, and approvals never run silently.

Related agents

MERCURY — AgentIQ Agent Catalogue · AgentIQ Labs