Agentic North Labs

Agentic Inbox

Email campaign infrastructure for AI agents that need real operational guardrails.

Open Agent Docs Index
Coding Agent Platform Integration Guide Auth roles, API payloads, constraints, and implementation workflows in Markdown. Marketing Agent Campaign Operations Guide Audience, drafting, queueing, reporting, and guardrails in Markdown.

Why Teams Use It

Agents can move fast without getting raw control of your outbound reputation.

01
Products remain the source of truth Consent, source metadata, and audience attributes arrive from upstream apps through sync APIs.
02
Operators get a controlled surface AI agents can create drafts, segment audiences, request approval, queue sends, and inspect outcomes through scoped endpoints.
03
Compliance stays in one layer Suppressions, unsubscribe links, bounce/complaint processing, and tenant isolation are enforced centrally.

Agentic Campaign Infrastructure

source-synced contacts scoped operator APIs centralized compliance

APIs for AI-run email campaigns, with approval and compliance built in.

Agentic Inbox is the shared outbound layer between product databases, agent operators, and your mail provider. It gives agents room to operate while keeping the risky parts centralized.

Upstream products `humaninloop.work` and other apps sync contacts into tenant-scoped audiences.
consent timestamps source ids tags
Operator APIs 
GET  /api/v1/segments/preview
POST /api/v1/campaigns
POST /api/v1/campaigns/{id}/schedule
POST /api/v1/campaigns/{id}/send-now
Guarded workflow
sync
draft
approve
send
feedback
What stays protected
  • unsubscribes and suppressions
  • tenant boundaries and org isolation
  • delivery event correlation
  • approval before queueing