by sending.ac

Agentic Cold Outreach for Claude Code, Codex, OpenCode, Gemini CLI, Cursor, Windsurf, Devin, OpenClaw, or Manus

Your agent creates outreach infrastructure, monitors campaigns and deliverability, and manages incoming replies in real-time. The closest thing to autonomous infrastructure on the market.

Give this to your agent

  • Codex
  • Claude Code
  • Cursor
  • Gemini CLI
  • OpenClaw

Set up builders.ac — https://github.com/ac-ecosystem/kit.builders.ac

  • Domains: domains.authenticate, SPF · DKIM · DMARC
  • Mailboxes: mailboxes.create, 36 inboxes
  • Warmup: warmup.status, reputation 98
  • Campaigns: campaigns.launch, 1,000 a day
  • Replies: replies.triage, 3 positive

Build on the signal before the market sees it.

 

  1. 01AgentYour agent takes the goal and works through it from your repo.
  2. 02SetupOne folder in your repo, connected through MCP & API.
  3. 03WorkflowMailbox signals become a health brief you review and approve.

01 Agent

Tell your agent the goal.

Four example turns, typed the way you would type them. Select one to read it in full.

/Users/yannic/claude/gtm-outreach

I need to send 1,000 emails a day. Use builders.ac to create infrastructure for my client and start the warmup.

Provisioning…(0s · esc to interrupt)

02 Setup

Keep the harness you already run.

builders.ac adds skills, scripts and an AGENTS.md to your repo. MCP & API connect your agent to sending.ac, your sequencer and the tools you use.

Agent harness
  • Claude Code
  • Codex
  • Cursor
  • Windsurf
  • Gemini CLI
  • OpenCode
  • OpenClaw
  • Manus
  • Devin
  • + any

Whatever you already run.

Your repo

builders.ac/

  • skills/
  • scripts/
  • AGENTS.md

The Skills, Scripts & Structure to make it seamless.

MCP & API

The key piece for the agent to know what's up.

Your stack
sending.acMailboxes, domains, warmup
Your sequencerInstantly, Smartlead, Bison, Plusvibe
Your existing toolsCRM, enrichment, whatever you run

03 Workflow

Work from first‑party signals.

Inbox activity, outbound mail, delivery notices and conversation context come from sending.ac. Your workflow compares them with a recent baseline and prepares a health brief for you to approve.

sending.ac
Infrastructure

Your mailbox layer

Inbox activity
Outbound mail
Delivery notices
Conversation context
Bounce spike investigator

Find what changed.

Delivery noticeFailures rise
CompareRecent baseline
Group evidenceMailbox + domain
OutputHealth brief ready
Ready for review
Deliverability

More control over time

See sooner. Act earlier.

sending.ac supplies the infrastructure and signals.You turn those signals into faster action on deliverability.
Get early access