Scheduling agent: coordinate meetings over email threads

Give the agent an inbox

Call POST /v1/inboxes (or create_inbox over MCP) to get a working address in milliseconds - on the shared in.threadcamp.com domain or your own custom domain. The agent reads inbound mail, replies on the thread and forwards, all with the same key.

Wait for the message that unblocks the task

Many agent jobs stall on an email arriving - an OTP, a verification link, a reply. wait_for_message polls the inbox for the specific message the agent needs mid-task, so it can continue without a brittle sleep-and-retry loop.

// Poll a ThreadCamp inbox for an incoming OTP or verification email
const msg = await fetch("https://threadcamp.vercel.app/v1/inboxes/inbox_.../wait", {
  method: "POST",
  headers: { Authorization: "Bearer sk_live_...", "Content-Type": "application/json" },
  body: JSON.stringify({ from: "no-reply@service.com", timeout_s: 120 }),
}).then((r) => r.json());

// -> { "id": "msg_...", "text": "Your code is 481920", ... }

Keep a human in the loop

For anything that sends outward, set the inbox to approve-first. Every agent send is held as a pending draft in a human approval queue; a one-click approval is what actually executes the send. That is how a scheduling agent runs unattended without becoming a spam risk.