agent-cold-email

 ⟨56 unchanged words⟩ monthly bill: ask the account owner first). At most 5; on a live account, a domain with no managed mailboxes needs 3-5.","maximum":105,"minimum":1,"type":"integer"}, ⟨259 unchanged words⟩ 

Reach a human at Coldrig support for anything list_messages/infrastructure_status cannot answer (a ⟨132 unchanged words⟩ 

 ⟨28 unchanged words⟩  credit, lower price starts next renewal, minimum: 5see mailboxes/$99account pricing). Returns { releasedCount, failedCount, unreleased,  ⟨108 unchanged words⟩ 

 ⟨52 unchanged words⟩  `domains`/`inboxesEach` are the setup you want to HAVE, not an amount to add: a repeat call never buys twice; each ordinal 0..domains-1 fills to its own count.count, at most 5 (3-5 for a live account's new domain). Mailbox addresses are DETERMINISTIC from persona+ordinal+slot: keep persona ⟨38 unchanged words⟩  NO background retry exists: a `provisioning` result (pending|capacity_pending)of pending needs YOU to call again; capacity_pending needs contact_operator instead.contact_operator. Returns { jobId, billing, provisioning?, nextSteps }.

 ⟨11 unchanged words⟩ },"distribution":{"items":{"maximum":105,"minimum":1,"type":"integer"}, ⟨43 unchanged words⟩ ":"string"},"inboxesEach":{"maximum":105,"minimum":1,"type":"integer"}, ⟨142 unchanged words⟩ 

 ⟨59 unchanged words⟩ 404 if the id doesn't exist for this tenant.account.

Unified activity feed: campaign events (sent/reply/bounce/...) merged with deliverability loop actions (pause/throttle/replace-domain). Cursor-paginated → { items[] ⟨25 unchanged words⟩ 

Register or advance a BYO domain/mailboxdomain intake. action = register (needs domain + domainRelationship: fresh_standalone|subdomain_of_primary|is_primary — runs pre-flight scan + abuse gate + reputation ladder, returns starting byoStatus) | poll_dns (needs id — re-checks DNS delegation, advancesdelegation; pending_dnsmoves ->to active, or ->to abandoned after 7 idle days) | acknowledge_consent (needs id + acknowledged:true, only after the account owner agrees — required before a primary domain can proceed pastpasses pending_consent; documents informed consent, does not removeconsent; exposure remains) | request_managed_mailboxes (needs id + count — platform-provisionedmanaged mailboxes on an ALREADY-ACTIVE domain; on a live account this raises the bill: ask the account owner, and run it only after they approve the price; every response carries a billing projection { provisionedAfter, projectedMonthlyCents, formula }; quoteOnly:true previews without provisioningadding any) | connect_mailbox (needs id + email + transport — declares an EXISTING OAuth/SMTP+IMAP connection, bypassing provisioning;connection; transport is smtp | gmail_api | ms_graph, each with its own credential fieldscredentials).

 ⟨8 unchanged words⟩ ":"Required (must be true) for acknowledge_consent, —and SPEC.mdonly §20.4'safter separate,the unbundledaccount owner has agreed: the separate risk acknowledgment.","type":"boolean"},"action ⟨9 unchanged words⟩ description":"Required for request_managed_mailboxes — how many platform-provisionedColdrig-managed mailboxes to attach.add (on a live account this raises the monthly bill: ask the account owner first).","maximum":10,"minimum":1,"type ⟨101 unchanged words⟩ new mailbox count + projected monthly price WITHOUT provisioningadding any (SPECquote §18before

 ⟨20 unchanged words⟩ → default) | delete (id). update ischecks rev-CASthe rev: a stale rev returns { currentRev, currentLayout } toso rebaseyou can re-apply your change and retry. Optional note. Read the current rev+layout via get_dashboard first.

Reach a human operatorat Coldrig support for anything list_messages/infrastructure_status cannot answer (a stuck vendor ⟨14 unchanged words⟩  default normal). Files a ticket, notifies theColdrig operator;support; returns { ticketId, note, deduplicated }.  ⟨24 unchanged words⟩  as a message on THIS account (poll list_messages/infrastructure_status —list_messages; no reply-fetch call). Sending the IDENTICAL body+urgency ⟨44 unchanged words⟩ `needs_human` bypasses the ~10-min ops-email throttle. Rate-limited to 5/hour/tenant5/hour per account — a 429 names retryAfter (seconds).

{"destructiveHint":false,"title":"Contact OperatorColdrig Support"}

 ⟨22 unchanged words⟩  + rev (pass this rev as the CAS base towhen configure_dashboardyou update with configure_dashboard). Views are both agent- and human-editable; write them with configure_dashboard.

Warmup +and provisioningsetup progress per mailbox. Returns { domains, mailboxes, ⟨50 unchanged words⟩ capacity. Top-level `sendReady` is the AND across ALL mailboxes (true once every one is ramped) —mailboxes. forEach onemailbox mailbox'scarries capacitystatus use(warming/active, itsor ownresting flag.after Eachsitting mailboxunused) carriesand delivStatus (healthy/throttled/paused), complaint/bounce/softBounce rates; vendorReputationScore/vendorPlacementRate are VENDOR-REPORTED, null when unmeasured. Vendor-poolWarmup warmuprun in the mailbox provider's own pool is FEED-INVISIBLENOT shown here, by design. `messages[]` previews 5 unacked  ⟨20 unchanged words⟩ 

 ⟨8 unchanged words⟩  list. You supply name, offer, leads[], and sequence[] (per step: step, subject, body, delayDays — subject is REQUIRED on step 1; a LATER step); maythe omitplatform itdoes tonot keepwrite stepcopy. 1'sOptional: subjecttimezone, linesendWindow, [recommended]stopOnReply, whichlistSource resolves(one atsentence launchon towhere "Re:the "list +came stepfrom; 1'sREQUIRED subjecton (unchangeda ifcrowdfunding thataccount, alreadywhere startsa withmissing "Re:or "), orunknown" setsource oneis explicitlyrefused to400). changeStep onlynumbers thatmust step'sbe subjectunique. lineSubject —is everyREQUIRED lateron step is still1; senta In-Reply-Tolater step 1, thoughmay someomit mailit clientsto displayreuse astep changed1's subject as a separate conversation), and optionally"Re: timezone," sendWindow,+ stopOnReply,that listSourcesubject (one sentence on where the list came from — REQUIRED on a crowdfunding accountrecommended), where a missing or "unknown" source is refused 400) — the platformset doesits notown, writethough copy.some Eachmail step'sclients `step`show numbera mustchanged besubject uniqueas withina theseparate sequence;conversation; aevery duplicatelater step number is refusedstill (400)sent namingIn-Reply-To it.step 1. Subjects and bodies may use {{firstName}} and {{company}} (filled from each lead; firstName and company are both optional) plus your own {{key}} for any key every lead carries in its optional `vars` map (word-keys to one-line strings, e.g. vars:{ icebreaker:"..." }; a key may not be firstName or company). A; valuevalues isare inserted once as plain text. A launch is refused (400 ⟨4 unchanged words⟩  how many leads lack it, if a subject or body uses {{firstName}} or a {{key}} that any leadtoken has no non-empty value for — no fallback word is invented;some itlead, isand also refused if any subject or body uses a {{…...}} that is not one word, a single-brace form of a known token such as {firstName} or {company} (a typo for the double-brace form — it would otherwise reach the recipientis unsubstituted)used, or a run of 3three or more consecutive `{` or `}` anywhere (e.g. {{{firstName}}} or a lopsided run like {{{firstName}} —together: iteach would otherwise reach the recipient with stray braces attached).unfilled. The send window is evaluated in `timezone` (IANA, e.g. America/New_York; default UTC) —: set it to your recipients' zone. sendWindow is { startHour, endHour, days? }: integer hours 0-23, endHour INCLUSIVE (the last hour a send may start in), days 0=Sunday …... 6=Saturday. Each omitted field (or all of them, by omittingOmitted sendWindow)fields getsget the platform's RECOMMENDED default {"startHour":8,"endHour":16,"days":[1,2,3,4,5]} — (Monday-Friday business hours —), except on a sandboxtest-mode account, where omitted fieldsthey are open every hour of every day until it upgrades and they take thatgoes default;live; the decision is yours, e.g. include 0  ⟨5 unchanged words⟩ send on weekends. Setting exactly ONE of startHour/endHour combinespairs it with the recommended defaultvalue for the OTHERother (08/16, including on a sandboxtest-mode account, since that value re-resolves to the same default on upgradetoo); —a iflaunch that combination would wrap the window past midnight (start >is end)refused, the launch is refused;so set both explicitly, including for a deliberatean overnight window such as {startHour:22, endHour ⟨19 unchanged words⟩ step ACTUALLY sent, from the SAME mailbox, with In-Reply-To/References set toIn-Reply-To step 1's Message-ID —1, itand waits while that mailbox is at its daily cap, andcap. theA lead's remaining steps are cancelled (a 'failed' event says why) once that mailbox is paused or released, since neither ever lifts on its own, or when a paid account's thread went out from a connected BYO mailbox, which this buildColdrig never sends from; a step whose previous step never went out is skipped. Lead addresses are trimmed and lower-cased, and anlower-cased; addressa repeated in leads[]address is kept once (its first row).once; Suppressedsuppressed leads are skipped. Returns { campaignId, sendWindow, ⟨3 unchanged words⟩  duplicatesRemoved, alreadyEmailed, endByShortfall, warning, nextSteps } —: sendWindow and timezone are what actually applied; contacts ⟨11 unchanged words⟩  are on your suppression list (never scheduled), duplicatesRemoved the repeated rows dropped, alreadyEmailed the leads left out because they already got this email.. With an endBy, endByShortfall is at leastabout how many of the contacts this campaign will email cannotnot get their first email before endBy on thisthe account's current mailboxes (a guaranteed minimum: each mailbox's daily cap on each day, warmup and throttle included, on the sendWindow's days and hours in timezone, and on a paid account at most one email per recipient domain in each 5-minute send round, counted as if nothing else were sending), andmailboxes; warning is one plain sentence saying so when it is above 0, or(a sayingshortfall, thator other campaigns' waiting emails, this campaign's own follow-ups, or more people at one company than there are sending days before endBythat may still make some contacts miss endBy): tell the person before they confirm. Nothing  ⟨13 unchanged words⟩ is a dry run: every launch check runs (a launch that would be refused is refused the same way), nothing is created or sent, no idempotencyKey ⟨10 unchanged words⟩ duplicatesRemoved, alreadyEmailed, endByShortfall, warning, samples } — the same endByShortfall and warning the launch would carry;where samples[] is= { email, steps[] } for the first three leads, (each step itsstep's rendered subject and bodybody; (every real send then appends the required footer: ⟨480 unchanged words⟩ 

 ⟨176 unchanged words⟩  retry is not applied twice (no duplicate campaign/provision/sendcampaign/setup/send).","maxLength":200,"minLength":1, ⟨388 unchanged words⟩ 3,4,5]} — except on a sandboxtest-mode account, where omitted fields are open every hour of every day until it upgradesgoes live and they take the recommended default. If you  ⟨62 unchanged words⟩ 5] (every day while the account is ain sandboxtest mode); include 0 and 6 to send on ⟨349 unchanged words⟩ 

List this tenant'saccount's system +and operatorColdrig support messages (a retryable setup step, a credential going live, ana operatornote noticefrom Coldrig support), cursor-paginated. Unacked messages sort first (newest  ⟨29 unchanged words⟩  progresses | 'operator_pending' = platform stopped, only anColdrig operatorsupport can restart it, retrying the SAME call  ⟨66 unchanged words⟩ 

 ⟨15 unchanged words⟩ the same event counts as campaign_results but summed tenant-wideacross the whole account (no per-contact fields) (bounce = hard  ⟨27 unchanged words⟩ 

Pause EVERY active campaign foron the tenantaccount at once (each active status → 'paused';  ⟨36 unchanged words⟩ 

 ⟨80 unchanged words⟩  the price is for that many. warnings: over_60_mailboxes (above the 60-address self-serve ceiling), late_booking (safeReach is below contacts), own_list_cheaper_on_esp ( ⟨34 unchanged words⟩ 

 ⟨8 unchanged words⟩  the billed quantity. Inputs: count, acknowledged (musttrue beonly trueafter —the account owner agrees: release is immediate butand irreversible; no mid-cycle credit, lower price starts  ⟨9 unchanged words⟩ unreleased, billing, deduplicated }. `count` is RELATIVE (that many MORE, not a fleet target).target. ALWAYS pass an idempotencyKey: the FIRST call  ⟨20 unchanged words⟩ `releasedCount` can be less than `count` — `failedCount` namesis how many the vendor refused (still live, billed; `unreleased` lists them). ResendRepeat the call with the same key until `failedCount` is 0. `deduplicated: true` = NO new work —work; an earlier recorded outcome under that key was replayed. A genuinely NEW downgrade needs a NEW key. 409 = a release is already running; re-checkcheck infrastructure_status before retrying.first. To ADD mailboxes use setup_infrastructure or configure_byo_domain.

 ⟨32 unchanged words⟩  retry is not applied twice (no duplicate campaign/provision/sendcampaign/setup/send).","maxLength":200,"minLength":1, ⟨7 unchanged words⟩ 

 ⟨27 unchanged words⟩  retry is not applied twice (no duplicate campaign/provision/sendcampaign/setup/send).","maxLength":200,"minLength":1, ⟨22 unchanged words⟩ 

ProvisionSet sendingup infrasending: buy lookalike domains, create mailboxes, start warmup. Inputs:On brand,a primaryDomain,live domainsaccount +this inboxesEachspends (ormoney distribution),and persona,raises physicalAddressthe monthly bill, senderIdentity.so BillingALWAYS isask perthe provisionedaccount mailbox;owner first: get the price with quoteOnly:true, previewsshow costit, first.and run it for real only after the owner approves that price in this conversation. `domains`/`inboxesEach` are the infrasetup you want to HAVE, not an amount to add —: a repeat call never buys twice; each ordinal 0..domains-1 fills to its own count. Mailbox addresses are DETERMINISTIC from persona+ordinal+slot —: keep persona unchanged on a retry. `registerDomains:true` isBuying requireda consentNEW beforedomain anyalso NEWneeds domain`registerDomains:true` purchase;(and omitting`registrant`, itunless on a buyfile), callset isonly refusedafter 400the registrar_optin_missingaccount (self-correctowner byapproves resendingthat true,purchase; neverwithout anit operatorthe escalation)call —is alsorefused needs400 `registrant`,registrar_optin_missing unlessand alreadynothing onis file.bought. NO background retry exists: a `provisioning` result (pending|capacity_pending) needs YOU to retry tocall progress;again; capacity_pending needs contact_operator instead. Returns { jobId,  ⟨4 unchanged words⟩ 

 ⟨48 unchanged words⟩  retry is not applied twice (no duplicate campaign/provision/sendcampaign/setup/send).","maxLength":200,"minLength":1, ⟨151 unchanged words⟩ 

{"destructiveHint":falsetrue,"title":"Set Up Sending Infrastructure"}

Permanently suppress an email address tenant-wideaccount-wide (every current and future campaign) — the ⟨59 unchanged words⟩ 

 ⟨21 unchanged words⟩  mailbox, campaign, label, read, includeNonreply (bounces/OOOthreads whose last event is a bounce, complaint or automatic reply such as out-of-office; default true), archived (exclude|include|only). Use  ⟨5 unchanged words⟩ 

 ⟨151 unchanged words⟩  and {{company}} (filled from each leadlead; firstName and company are both optional) plus your own {{key}} for any key every lead carries in its optional `vars` map (word-keys to one-line strings, e.g. vars:{ icebreaker:"..." }; a key may not be firstName or company). A value is inserted once as plain text. A launch is refused (400), naming the token and how many leads lack it, if anya subject or body uses {{firstName}} or a {{key}} that any otherlead has no non-empty value for — no fallback word is invented; it is also refused if any subject or body uses a {{token…}} that is not one word, a single-brace form of a known token  ⟨314 unchanged words⟩ whose previous step never went out is skipped. Lead addresses are trimmed and lower-cased, and an address repeated in leads[] is kept once (its first row). Suppressed leads are skipped. Returns { campaignId, sendWindow, timezone, contacts, suppressed, duplicatesRemoved, alreadyEmailed, endByShortfall, warning, nextSteps } — sendWindow and timezone are what actually applied.applied; Campaignscontacts is how many leads were stored, suppressed how many of those are on your suppression list (never scheduled), duplicatesRemoved the repeated rows dropped, alreadyEmailed the leads left out because they already got this email. With an endBy, endByShortfall is at least how many of the contacts this campaign will email cannot get their first email before endBy on this account's current mailboxes (a guaranteed minimum: each mailbox's daily cap on each day, warmup and throttle included, on the sendWindow's days and hours in timezone, and on a paid account at most one email per recipient domain in each 5-minute send realround, mailcounted as if nothing else were sending), and warning is one plain sentence saying so when it is above 0, or saying that other campaigns' waiting emails, this campaign's own follow-ups, or more people at one company than there are sending days before endBy may still make some contacts miss endBy: tell the person before they confirm. Nothing is refused for it; whatever still waits at endBy is skipped. previewOnly:true is a dry run: every launch identicalcheck toruns one(a launch that would be refused is refused the same way), nothing is created or sent, no idempotencyKey is recorded, and it returns { preview, sendWindow, timezone, contacts, suppressed, duplicatesRemoved, alreadyEmailed, endByShortfall, warning, samples } — the same endByShortfall and warning the launch would carry; samples[] is { email, steps[] } for the first three leads, each step its rendered subject and body (every real send then appends the required footer: sender identity, postal address, unsubscribe link). People who already got this email are skipped: a contact is left out, never stored or emailed, when another campaign of this account madehas sent them, or still has waiting for them, an email with the same subject and body as this campaign's first email, as written before {{tokens}} are filled in (spacing differences do not count). A trial's test email counts only while the lastaccount 60is secondsstill on the trial, and the built-in demo campaign never counts. alreadyEmailed in the answer is REFUSEDhow withmany 409were {skipped code(anyone also on your suppression list is counted there, not in suppressed):'duplicate_campaign' tell the person in plain words, existingCampaignIdfor }example rather"skipped than12 contactingpeople who already got this email". To include them, send includeAlreadyEmailed: true on the launch itself (previewOnly: true shows the count first), or after a launch add them to that same prospectscampaign twicewith —add_leads checkand includeAlreadyEmailed: true. Never launch the same list again to include them: that emails everyone who was not skipped a second time. Naming a repeat with repeatOf includes them too. A launch on which everyone would be skipped is refused (400) and nothing is created; an add of contacts on which everyone is skipped adds no one, with no error. A launch, or an add of contacts, is refused with 409 duplicate_campaign when it would leave a campaign insteadwith exactly the same set of relaunching.contact Resendaddresses and the same idempotencyKeysubjects and bodies in the same step order as another campaign of this account, however long ago that one was launched and whether it is running, paused, ended or finished, so the same people are not sent the same emails twice. Nothing else is compared: a different name, offer, time zone, send window, delay, date, stopOnReply, listSource, row order or contact name, company or vars is still the same campaign. The refusal creates nothing and carries existingCampaignId, existingCampaignName and existingCampaignState. To repeat that campaign on purpose, send the request again with repeatOf set to that existingCampaignId: it is accepted once, and only while it names the most recent such campaign. To retry a call whose response you lost:, thatresend it with the same idempotency key, which replays the original result insteadinstead. ofA beingcampaign refused.launched Campaignson thata differtrial account emailed nobody and counts only while the account is still on the trial; the built-in demo campaign never counts. A trial account can launch up to 5 test campaigns in any field24 otherhours, thaneach listSourceholding (up to 100 contacts, which is notenough partfor a small test. Both are limits of thatthe check)trial, andnot deliberateof relaunchesColdrig: aftergoing thoselive 60removes secondsthem. Nothing in a campaign launched on the trial is ever really sent: when the account goes live, the emails it still has waiting are nevercanceled blocked.and it cannot be resumed or added to, so launch a new campaign to send real email.

 ⟨187 unchanged words⟩ "minLength":1,"type":"string"},"includeAlreadyEmailed":{"description":"Optional. true also stores and emails the contacts who already got this campaign's first email from another campaign of this account; without it they are skipped and counted in alreadyEmailed.","type":"boolean"},"leads":{"items":{"properties":{"company ⟨25 unchanged words⟩ ,"type":"string"},"firstName":{"default":"","maxLength":200,"minLengthtype":1"string"},"vars":{"additionalProperties":{"maxLength":2000,"type":"string"},"description":"Optional per-lead values for your own {{tokens}}: a flat map of word-keys (letters, digits, underscore; up to 64 chars) to one-line strings (up to 2000 chars), at most 50 keys. A {{key}} used in any subject or body must be present, non-empty, on EVERY lead or the launch is refused (400) naming it. A key may not be firstName or company."required,"propertyNames":[{"emailmaxLength":64,"firstNamepattern

 ⟨8 unchanged words⟩  counts{sent,reply,bounce,complaint,unsubscribe,failed,soft_bounce,auto_reply} }], newest first — no per-campaign  ⟨12 unchanged words⟩ 

 ⟨21 unchanged words⟩  notes, tags, suppressed, lastEventType, lastEventTs, createdAt.createdAt, threadId (that lead's conversation: pass it to thread for the lead's timeline; null if nothing was scheduled). Filters: campaign, interestStatus, suppressed, replied. This ⟨31 unchanged words⟩ 

 ⟨7 unchanged words⟩ reply, bounce, complaint, unsubscribe, failed, soft_bounce, auto_reply } — the same shapeevent counts as campaign_results but summed tenant-wide (no per-contact fields) (bounce = hard only, opens not trackedtracked; auto_reply = automatic replies such as out-of-office, never counted in reply). Use campaign_results for one campaign, list_campaigns  ⟨5 unchanged words⟩ 

Pause ONE campaign: its status → 'paused', soand thenothing tickmore schedulesin noit furthersends; its remaining steps are HELD, not cancelled (already-sent mail is unaffected; thereunaffected) is— nocall resume tool).to continue it. Input: campaignId. Returns { paused: true }. ⟨19 unchanged words⟩  already gave): their remaining steps are cancelled for good (resume does not bring them back), the campaign keeps running for everyone else, ⟨42 unchanged words⟩ 

 ⟨7 unchanged words⟩  at once (each active status → 'paused'; thenothing tickmore thenin schedulesthem nosends, furtherand sendstheir remaining steps are held). No inputs. Returns { pausedAll: true }. Use pause to pause a single campaign by id.id, and resume (one call per campaign) to continue one.

 ⟨21 unchanged words⟩ messages[] }, each message { type (sent/reply/bounce/...sent/reply/auto_reply/bounce/...; auto_reply = an automatic reply such as out-of-office), step (the sequence step of a sent message, null otherwise), ts, messageId, metadata }, oldest  ⟨15 unchanged words⟩ 

 ⟨21 unchanged words⟩  mailbox, campaign, label, read, includeNonreply (bounces/OOOthreads whose last event is a bounce, complaint or automatic reply such as out-of-office; default true), archived (exclude|include|only). Use  ⟨5 unchanged words⟩ 

 ⟨151 unchanged words⟩  and {{company}} (filled from each leadlead; firstName and company are both optional) plus your own {{key}} for any key every lead carries in its optional `vars` map (word-keys to one-line strings, e.g. vars:{ icebreaker:"..." }; a key may not be firstName or company). A value is inserted once as plain text. A launch is refused (400), naming the token and how many leads lack it, if anya subject or body uses {{firstName}} or a {{key}} that any otherlead has no non-empty value for — no fallback word is invented; it is also refused if any subject or body uses a {{token…}} that is not one word, a single-brace form of a known token  ⟨314 unchanged words⟩ whose previous step never went out is skipped. Lead addresses are trimmed and lower-cased, and an address repeated in leads[] is kept once (its first row). Suppressed leads are skipped. Returns { campaignId, sendWindow, timezone, contacts, suppressed, duplicatesRemoved, alreadyEmailed, endByShortfall, warning, nextSteps } — sendWindow and timezone are what actually applied.applied; Campaignscontacts is how many leads were stored, suppressed how many of those are on your suppression list (never scheduled), duplicatesRemoved the repeated rows dropped, alreadyEmailed the leads left out because they already got this email. With an endBy, endByShortfall is at least how many of the contacts this campaign will email cannot get their first email before endBy on this account's current mailboxes (a guaranteed minimum: each mailbox's daily cap on each day, warmup and throttle included, on the sendWindow's days and hours in timezone, and on a paid account at most one email per recipient domain in each 5-minute send realround, mailcounted as if nothing else were sending), and warning is one plain sentence saying so when it is above 0, or saying that other campaigns' waiting emails, this campaign's own follow-ups, or more people at one company than there are sending days before endBy may still make some contacts miss endBy: tell the person before they confirm. Nothing is refused for it; whatever still waits at endBy is skipped. previewOnly:true is a dry run: every launch identicalcheck toruns one(a launch that would be refused is refused the same way), nothing is created or sent, no idempotencyKey is recorded, and it returns { preview, sendWindow, timezone, contacts, suppressed, duplicatesRemoved, alreadyEmailed, endByShortfall, warning, samples } — the same endByShortfall and warning the launch would carry; samples[] is { email, steps[] } for the first three leads, each step its rendered subject and body (every real send then appends the required footer: sender identity, postal address, unsubscribe link). People who already got this email are skipped: a contact is left out, never stored or emailed, when another campaign of this account madehas sent them, or still has waiting for them, an email with the same subject and body as this campaign's first email, as written before {{tokens}} are filled in (spacing differences do not count). A trial's test email counts only while the lastaccount 60is secondsstill on the trial, and the built-in demo campaign never counts. alreadyEmailed in the answer is REFUSEDhow withmany 409were {skipped code(anyone also on your suppression list is counted there, not in suppressed):'duplicate_campaign' tell the person in plain words, existingCampaignIdfor }example rather"skipped than12 contactingpeople who already got this email". To include them, send includeAlreadyEmailed: true on the launch itself (previewOnly: true shows the count first), or after a launch add them to that same prospectscampaign twicewith —add_leads checkand includeAlreadyEmailed: true. Never launch the same list again to include them: that emails everyone who was not skipped a second time. Naming a repeat with repeatOf includes them too. A launch on which everyone would be skipped is refused (400) and nothing is created; an add of contacts on which everyone is skipped adds no one, with no error. A launch, or an add of contacts, is refused with 409 duplicate_campaign when it would leave a campaign insteadwith exactly the same set of relaunching.contact Resendaddresses and the same idempotencyKeysubjects and bodies in the same step order as another campaign of this account, however long ago that one was launched and whether it is running, paused, ended or finished, so the same people are not sent the same emails twice. Nothing else is compared: a different name, offer, time zone, send window, delay, date, stopOnReply, listSource, row order or contact name, company or vars is still the same campaign. The refusal creates nothing and carries existingCampaignId, existingCampaignName and existingCampaignState. To repeat that campaign on purpose, send the request again with repeatOf set to that existingCampaignId: it is accepted once, and only while it names the most recent such campaign. To retry a call whose response you lost:, thatresend it with the same idempotency key, which replays the original result insteadinstead. ofA beingcampaign refused.launched Campaignson thata differtrial account emailed nobody and counts only while the account is still on the trial; the built-in demo campaign never counts. A trial account can launch up to 5 test campaigns in any field24 otherhours, thaneach listSourceholding (up to 100 contacts, which is notenough partfor a small test. Both are limits of thatthe check)trial, andnot deliberateof relaunchesColdrig: aftergoing thoselive 60removes secondsthem. Nothing in a campaign launched on the trial is ever really sent: when the account goes live, the emails it still has waiting are nevercanceled blocked.and it cannot be resumed or added to, so launch a new campaign to send real email.

 ⟨187 unchanged words⟩ "minLength":1,"type":"string"},"includeAlreadyEmailed":{"description":"Optional. true also stores and emails the contacts who already got this campaign's first email from another campaign of this account; without it they are skipped and counted in alreadyEmailed.","type":"boolean"},"leads":{"items":{"properties":{"company ⟨25 unchanged words⟩ ,"type":"string"},"firstName":{"default":"","maxLength":200,"minLengthtype":1"string"},"vars":{"additionalProperties":{"maxLength":2000,"type":"string"},"description":"Optional per-lead values for your own {{tokens}}: a flat map of word-keys (letters, digits, underscore; up to 64 chars) to one-line strings (up to 2000 chars), at most 50 keys. A {{key}} used in any subject or body must be present, non-empty, on EVERY lead or the launch is refused (400) naming it. A key may not be firstName or company."required,"propertyNames":[{"emailmaxLength":64,"firstNamepattern

 ⟨8 unchanged words⟩  counts{sent,reply,bounce,complaint,unsubscribe,failed,soft_bounce,auto_reply} }], newest first — no per-campaign  ⟨12 unchanged words⟩ 

 ⟨21 unchanged words⟩  notes, tags, suppressed, lastEventType, lastEventTs, createdAt.createdAt, threadId (that lead's conversation: pass it to thread for the lead's timeline; null if nothing was scheduled). Filters: campaign, interestStatus, suppressed, replied. This ⟨31 unchanged words⟩ 

 ⟨7 unchanged words⟩ reply, bounce, complaint, unsubscribe, failed, soft_bounce, auto_reply } — the same shapeevent counts as campaign_results but summed tenant-wide (no per-contact fields) (bounce = hard only, opens not trackedtracked; auto_reply = automatic replies such as out-of-office, never counted in reply). Use campaign_results for one campaign, list_campaigns  ⟨5 unchanged words⟩ 

Pause ONE campaign: its status → 'paused', soand thenothing tickmore schedulesin noit furthersends; its remaining steps are HELD, not cancelled (already-sent mail is unaffected; thereunaffected) is— nocall resume tool).to continue it. Input: campaignId. Returns { paused: true }. ⟨19 unchanged words⟩  already gave): their remaining steps are cancelled for good (resume does not bring them back), the campaign keeps running for everyone else, ⟨42 unchanged words⟩ 

 ⟨7 unchanged words⟩  at once (each active status → 'paused'; thenothing tickmore thenin schedulesthem nosends, furtherand sendstheir remaining steps are held). No inputs. Returns { pausedAll: true }. Use pause to pause a single campaign by id.id, and resume (one call per campaign) to continue one.

 ⟨21 unchanged words⟩ messages[] }, each message { type (sent/reply/bounce/...sent/reply/auto_reply/bounce/...; auto_reply = an automatic reply such as out-of-office), step (the sequence step of a sent message, null otherwise), ts, messageId, metadata }, oldest  ⟨15 unchanged words⟩ 

 ⟨27 unchanged words⟩ paused: true }. 404 if not found. Add leadEmails to stop ONLY those leads in this campaign instead (e.g. a donor who already gave): their remaining steps are cancelled, the campaign keeps running for everyone else, and nobody is suppressed — returns { paused: false }. Matching ignores capitalisation; if any address is not a lead of this campaign, nothing is stopped and the call is refused (404) naming them. Use pause_all to pause every active campaign at once.

 ⟨12 unchanged words⟩ ","minLength":1,"type":"string"},"leadEmails":{"description":"Optional. Stop ONLY these leads in this campaign (any capitalisation): their remaining steps are cancelled, the campaign keeps running for everyone else, and nobody is added to the suppression list. Every address must be a lead of this campaign, or nothing is stopped and the call is refused naming the ones that are not. Omit to pause the whole campaign.","items":{"format":"email","pattern":"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$","type":"string"},"maxItems":5000,"minItems":1,"type":"array"}},"required":["campaignId"],"type":"object"}

 ⟨27 unchanged words⟩ paused: true }. 404 if not found. Add leadEmails to stop ONLY those leads in this campaign instead (e.g. a donor who already gave): their remaining steps are cancelled, the campaign keeps running for everyone else, and nobody is suppressed — returns { paused: false }. Matching ignores capitalisation; if any address is not a lead of this campaign, nothing is stopped and the call is refused (404) naming them. Use pause_all to pause every active campaign at once.

 ⟨12 unchanged words⟩ ","minLength":1,"type":"string"},"leadEmails":{"description":"Optional. Stop ONLY these leads in this campaign (any capitalisation): their remaining steps are cancelled, the campaign keeps running for everyone else, and nobody is added to the suppression list. Every address must be a lead of this campaign, or nothing is stopped and the call is refused naming the ones that are not. Omit to pause the whole campaign.","items":{"format":"email","pattern":"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$","type":"string"},"maxItems":5000,"minItems":1,"type":"array"}},"required":["campaignId"],"type":"object"}

Reach a human operator — for anything list_messages/infrastructure_status can'tcannot answer (a stuck vendor issue, a billing ⟨5 unchanged words⟩  Inputs: body (1-2000 chars), urgency ('normal' | 'needs_human'normal|needs_human, default 'normal'normal). Files a support ticket and, notifies the operator; returns { ticketId, note, deduplicated }. Works in every account state a tenant token still authenticates in, including (dunning-suspended, canceling and, canceled) — thisadmin-terminated is exactly the channel for 'why is my account suspended?'. The ONEone exception is an admin-TERMINATED (abuse) account, whose token is rejected at auth with 401 before this tool runs.auth. The operator's reply arrives as a message on THIS account (poll list_messages / infrastructure_status.messages[]list_messages/infrastructure_status — there is no separate reply-fetch call). Sending the IDENTICAL body AND urgencybody+urgency again within an hour returns the SAME ticketId and does not file a second ticket or send, ano second alertticket/alert (`deduplicated: true` on that response; `false` when a new ticket was actually filed) — no separate idempotency key is needed to retry a dropped response. This is a. TEXT matchMATCH, notNOT anAN intentINTENT matchMATCH: the platform cannot tell a deliberate retry from a coincidentally-identical NEW message, so a genuinely new askmessage with the sameidentical wording collapses into the earlier ticket justsame asway, silently — vary the wording (or raise urgency, which is always treated as an escalation and files a new ticket) if you have something new to say. 'needs_human'. also`needs_human` bypasses the ~10-minute~10-min ops-email throttle so an urgent message is pushed immediately.throttle. Rate-limited to 5 calls/hour per tenant5/hour/tenant — a 429 names retryAfter (seconds) when hit..

Warmup + provisioning progress per mailbox. New mailboxes are ramp-limited server-side: 5 sends/day week 1 rising to 40/day after 4 weeks; current dailyCap for each mailbox is in the response below — ramp caps permit CAPPED sending from day 1, never zero until fully warmed. Returns { domains, mailboxes, sendReady, mailboxHealth[], messages[], nextSteps }; each mailbox: warmupDay, dailyCap, sentToday, sendReady, delivStatus (healthy/throttled/paused),. complaint/bounce/softBounceNew ratesmailboxes (first-partyramp-limit measured),server-side: vendorReputationScore5 +sends/day vendorPlacementRateweek (VENDOR-REPORTED1, not40/day first-partyweek measurements4 — the control loop uses local signals only; BOTH ARE null whenever the provider does not reportdailyCap/sentToday them,show whichreal iscapped thesending normalfrom caseday today1, so treat null as 'not measured' and never as zero), lastPolledAt.zero. Per-mailbox `sendReady` is a FULLY-RAMPED flag, NOT a send gate — a mailbox below fullbelow-ramp rampmailboxes still sendssend, capped at itstheir own `dailyCap`; `sendReady` only says warmup has finished, sodailyCap; read `dailyCap`/`sentToday`dailyCap/sentToday for actual send capacity, never `sendReady` alone. Thecapacity. top-levelTop-level `sendReady` is the AND across ALL mailboxes (true only once every one has finishedis rampingramped) — for whether THISone mailboxmailbox's cancapacity senduse rightits now,own theflag. per-mailboxEach flagmailbox nextcarries todelivStatus it(healthy/throttled/paused), iscomplaint/bounce/softBounce therates; onevendorReputationScore/vendorPlacementRate thatare mattersVENDOR-REPORTED, not thenull top-levelwhen one.unmeasured. Vendor-pool warmup (the underlying reputation-building the provider runs) is FEED-INVISIBLE by design: nothing in this response surfaces the vendor's own warmup internals — dailyCap/warmupDay/sendReady here are this platform's own ramp schedule, computed independently of whatever the vendor is doing in its pool, so do not expect a vendor-side warmup event to show up here.design. `messages[]` surfaces system notices this account should act on (e.g. a setup step that needs a retry, a mailbox credential that just went live) — each has kind, severity ('info' = resolves on its own | 'action_required' = nothing progresses until you act, and acting works | 'operator_pending' = the platform has stopped and nothing you change will restart it, but an operator can clear the blocker and then retrying the SAME call with the SAME idempotency key completes it — keep your inputs as they are and do not give up | 'terminal' = the platform has STOPPED, retrying will never help and only a human can move it — the actionHint names contact_operator), body, actionHint (structured — e.g. which tool + idempotencyKey to retry with), createdAt; poll this alongside the mailbox fields — capped at the newestpreviews 5 (operator replies sort first, so system churn cannot evict one, but a 6th DISTINCT unacked message of either kind can still fall off this preview;notices use(severities: list_messages for the complete, paginated history). Reading them here does NOT mark them read — only an explicit ack_message call sets readAt. Unacked operator messages sort first here, then system notices newest-first, so a human reply; isreading never pushed out of the 5 by system churn; list_messages is the full paginatedmarks surface.read. `nextSteps` names what this account should dothe next —action (see setup_infrastructure's description for the discriminated shape.setup_infrastructure). Use account/metrics for account-wide rollups.

 ⟨18 unchanged words⟩ ), cursor-paginated. Unacked messages sort first (newest first within that group), then acked ones (also newest first). Returns { messages[], nextCursor }; each message: id, kind, severity ('info'|'action_required'|'operator_pending'|'terminal' —'info' 'operator_pending'= meansresolves theon platformits hasown stopped,| nothing'action_required' you= changeact restartsand it, andprogresses an| operator'operator_pending' clearing= theplatform blockerstopped, makesonly thean SAMEoperator retrycan work,restart soit, keepretrying the sameSAME inputscall andthen idempotencyworks key;| 'terminal' means the= platform has stopped and, only a human can move it, so do NOT retry), body, actionHint (structured — e.g. which tool + idempotencyKey to retry with), source ('system'|'operator'system|operator), createdAt, readAt. `readAt` is set ONLY by an explicit ack_message call — LISTING messageslisting never marks them, here or anywheremessages elseread, so calling this tool leaves every readAt exactly as it was. Aa null readAt therefore means 'not acked', which is NOT evidence thedoes messagenot wasmean never seen: it may have been read and, simplyonly not yet acknowledged. Use ack_message to acknowledgestop one by id so it stops resurfacing. infrastructure_status also inlines the newest 5 unacked messages for a quick glance —messages; this is the full paginated surface.

Downgrade: release your N NEWEST live mailboxes now and, lowerlowering the billed quantity. Inputs: count, acknowledged (must be true — this is a quoted, irreversible-this-cycle consent: the release is immediate for provisioning but there isirreversible; NOno mid-cycle credit; thecredit, lower price takes effectstarts next renewal, minimum 5 mailboxes / $99mailboxes/$99). Returns { releasedCount, failedCount, unreleased, billing, deduplicated } where billing is the new projected monthly. `releasedCount` is what COMPLETED and can be less than the `count` you asked for; `failedCount` is how many the provider refused, which are STILL LIVE and still billed, and `unreleased` names those addresses — read them before concluding a downgrade landed. `deduplicated: true` means this call did NOT re-perform the downgrade — every count above describes an EARLIER call's already-recorded outcome under the same idempotencyKey, not new work done just now. This can be true even after the 30-day idempotency window itself has expired: the underlying release record persists independently, so a reused key still reports no re-release rather than silently starting a fresh one.. `count` is RELATIVE — it releases (that many MORE mailboxes, it does not set youra fleet to that size — and release cannot be undone through this API, sotarget). ALWAYS pass an idempotencyKey: the FIRST call under a key resolvesfixes WHICH mailboxes to release and records that exact set, sorelease; everya later call carryingwith the SAME key can only ever finish that same set. A same-key retry re-attempts the stragglers and`releasedCount` can neverbe releaseless athan mailbox`count` outside— them,`failedCount` whatevernames `count`how youmany sendthe withvendor itrefused (the recorded setstill winslive, overbilled; a`unreleased` changedlists countthem);. aResend retrywith WITHOUTthe asame key always releases another `count`.until A`failedCount` genuineis SECOND0. downgrade`deduplicated: istrue` therefore= aNO NEWnew keywork — reusing an old one can onlyearlier everrecorded finishoutcome whatunder that key already askedwas for.replayed. A call that came back with failedCount above zero did NOT finish, so its key is not frozen: resend the identical request with the same key until failedCount is 0 — from then on that key replays the finished result and releasesgenuinely nothingNEW further.downgrade Ifneeds a callNEW returnskey. 409 = a release is already running for this account: wait, thenrunning; re-readre-check infrastructure_status before deciding whether to retry.retrying. To ADD mailboxes use setup_infrastructure / configure_byo_domainor (request_managed_mailboxes).configure_byo_domain.

 ⟨17 unchanged words⟩ messageId, deduplicated }. A reply is real sendingsend volume and is, governed exactly like campaign sends: it counts against thatthe mailbox'smailbox daily cap (sentToday +1, visible in infrastructure_status), and it is REFUSED — (never silently dropped —) when the recipient is suppressed, the mailbox is deliverability-paused, or the cap is used up.up A— a refusal returns { error, code:'send_blocked' send_blocked, reason:'suppressed'|'mailbox_paused'|'daily_cap_reached' suppressed|mailbox_paused|daily_cap_reached, retryable }:; retryable (cap) clears at the next daily rollover, non-retryable does not, so— stop retrying, anddo don'tnot loop replies to manufacture volume. Idempotent: identical  ⟨8 unchanged words⟩ stable idempotencyKey (else a body hash is used, matched only 10 minutes) so a dropped-response retry can'tcannot double-send. `deduplicated: true` means= NO new email was sent —sent; `messageId` is from an earlier send this call matched. `deduplicated: false` means this platform sent the call onward as a NEW send, which is normally a new email — but it is not a guarantee one left the building: with NO idempotencyKey the body hash is only matched here for 10 minutes, while the sending provider keeps its own record of an identical body on the same thread for longer, and can collapse a much later repeat into the originalmatching send. So onPass a long-delayed identical repeat you may get `deduplicated: false` with the ORIGINAL send's messageId and no new email. PASS AN IDEMPOTENCYKEYkey, or vary the body, if you need a repeat tomust genuinely go out. 404 if no sending mailbox ⟨6 unchanged words⟩ 

Provision sending infrastructureinfra: buy branded lookalike domains, create mailboxes, start warmup. New mailboxes are ramp-limited server-side — 5 sends/day in week 1, rising to 40/day after 4 weeks — and your own calls cannot exceed that cap; poll infrastructure_status for the current dailyCap. Inputs: brand, primaryDomain, domains + inboxesEach counts(or distribution), persona, physicalAddress, senderIdentity. Billing is per-provisioned-mailbox ($49 platform + per mailbox, graduated: 1-5 at $10, 6-20 at $8, 21+ at $7; 5-mailbox minimum) and the billed quantity follows what you provision here —provisioned passmailbox; quoteOnly:true first to preview the new count + projected monthly price before committing (no silent capacity addition). Every response carries a `billing` projection { provisionedAfter (the live count AFTER this call — reality, not the ask), projectedMonthlyCents, formula }: on quoteOnly it's the preview, on an actual provision it's the real post-provision bill (a capacity-limited partial reflects only what landed). Returns { jobId, billing } — `jobId` is a correlation id only, not a trackable job handle: there is no job store and no endpoint that accepts it, so do not poll for it or treat its presence as meaningful; it exists to correlate this response with logs. A `provisioning` field is present ONLY when the call returned still OWING work, and names which state: 'pending' (a domain's DNS registration is still completing — `pendingDomain` names one of them) or 'capacity_pending' (held at a spend limit, so polling will NOT progress until an operator raises it — call contact_operator instead of waiting). Its ABSENCE is what says the provision finished; the only way to find out is to re-call setup_infrastructure or read infrastructure_status's `nextSteps`. An outcome carrying `provisioning`, and a quoteOnly preview, are deliberately NOT recorded against your idempotencyKey — retrying with the same key re-runs the call and finishes the job rather than replaying the unfinished answer.previews `domains`cost andfirst. `inboxesEach``domains`/`inboxesEach` are the infrastructureinfra you want to HAVE, not an amount to add: each call keeps and resumes what this account already has and buys only the shortfall, so to provision MORE you ask for a LARGER number (domains:2 after a call that provisioned one buys the second; raising inboxesEach tops each domain up). Repeating a call therefore never buys twice, whatever you do with idempotencyKey — resend it, change it, or omit it. The key controls response replay only and has no bearing on what is purchased, so a retry is always safe. A domain this account already registered but that never landed in your account (a prior call that failed after the purchase) is ADOPTED on the retry at zero extra cost rather than bought again. A domain whose DNS setup has not finished yet is recorded and never lost — there is no per-domain DNS field to poll (infrastructure_status reports a domain count, not per-domain detail), so read its `nextSteps` for what to do next, and repeat this same call to converge on the domain and finish its DNS setup. Slot semantics: `domains: N` covers ordinalsnever 0..N-1,buys andtwice; each ordinal 0..domains-1 fills to its own mailbox count (uniform via `inboxesEach`, or per-ordinal via `distribution` — see below); a repeat call at the SAME `domains` provisions nothing new once every ordinal is satisfied, so reaching ordinal 1 needs `domains:2`, not a second `domains:1` call.count. Mailbox addresses are DETERMINISTIC — derived from `persona` + ordinal + slotpersona+ordinal+slot — so keep `persona` EXACTLY as it was on a resume or retry; changing it mid-account does not move existing addresses but does change what a NEW ordinal derives. `distribution` (optional, alternative to `inboxesEach`) names the per-ordinal mailbox count directly — one entry per domain ordinal, e.g. `[3, 2]` for 3 mailboxes on domain 0 andpersona 2unchanged on domain 1 — for a shape `inboxesEach`'s single uniform number cannot express; supply exactly one of the two (an array with `domains` entries, or the uniform count).retry. `registerDomains``registerDomains:true` is this tenant's opt-inrequired consent to real domain purchases made on the platform's own account (our COGS — your bill is unchanged, mailbox-count-based only); only the operator's own global switch being armed too can ever actually enable it. OMITTING it leavesbefore any consent you previously gave UNCHANGED — pass `false` explicitly to revoke it. A call that omitsNEW `registerDomains`domain (orpurchase; sendsomitting it `false`) on a buy-bearing request (one that needs to purchase a newbuy domain)call is refused BEFORE any spend. Once this account has consented at least once, that refusal is a 400 `registrar_optin_missing`: 'registerDomains was not set on this request' — resend the identical call withregistrar_optin_missing it(self-correct setby toresending true to self-correct; this is, never an operator escalation. (An account that has never consented, on a platform where domain registration is not yet enabled at all, instead sees the operator-facing 503 `registrar_unarmed` — indistinguishable from the outside except by status code, but the fix is the same: set `registerDomains: true` and retry.) Separately, a `registerDomains:true` call with NO `registrant` anywhere (neither in this request nor persisted from a prior oneescalation) fails with a 400 `incomplete_registrant` naming the missing fields — also before any purchase. Fresh candidates are de-duplicated against what this account already owns and checked for availability; if a call needs to buy a domain and no available un-owned candidate exists it fails with a 400 naming that, never a silent repeat purchase (a call that needs to buy nothing is unaffected). `registrant` (a full registrant-of-record object { firstName, lastName, email, phone, addressLine1, city, state, country, postalCode, organization (optional, defaults to brand) }) is OPTIONAL even when `registerDomains` is true whenever a complete registrant isunless already on file from a prior call — supplying one makes it authoritative for THIS call; omitting it re-uses the persisted one. This platform never invents a domain registrant's legal identity, so a call with no registrant anywhere (neither supplied nor persisted) is rejected naming the missing fields, at or before the actual purchase — never silently. There isfile. NO background retry exists: a call`provisioning` returningresult `provisioning`(pending|capacity_pending) needs the callerYOU to retry it; the platform does not complete it for you on a timer. Every response carries `nextSteps` (see the discriminatedto `status`/`steps`progress; shape)capacity_pending —needs thecontact_operator account'sinstead. ownReturns next{ actionjobId, computed fresh each timebilling, so a stalled setup isprovisioning?, nevernextSteps silent.}.

Reach a human operator — for anything list_messages/infrastructure_status can'tcannot answer (a stuck vendor issue, a billing ⟨5 unchanged words⟩  Inputs: body (1-2000 chars), urgency ('normal' | 'needs_human'normal|needs_human, default 'normal'normal). Files a support ticket and, notifies the operator; returns { ticketId, note, deduplicated }. Works in every account state a tenant token still authenticates in, including (dunning-suspended, canceling and, canceled) — thisadmin-terminated is exactly the channel for 'why is my account suspended?'. The ONEone exception is an admin-TERMINATED (abuse) account, whose token is rejected at auth with 401 before this tool runs.auth. The operator's reply arrives as a message on THIS account (poll list_messages / infrastructure_status.messages[]list_messages/infrastructure_status — there is no separate reply-fetch call). Sending the IDENTICAL body AND urgencybody+urgency again within an hour returns the SAME ticketId and does not file a second ticket or send, ano second alertticket/alert (`deduplicated: true` on that response; `false` when a new ticket was actually filed) — no separate idempotency key is needed to retry a dropped response. This is a. TEXT matchMATCH, notNOT anAN intentINTENT matchMATCH: the platform cannot tell a deliberate retry from a coincidentally-identical NEW message, so a genuinely new askmessage with the sameidentical wording collapses into the earlier ticket justsame asway, silently — vary the wording (or raise urgency, which is always treated as an escalation and files a new ticket) if you have something new to say. 'needs_human'. also`needs_human` bypasses the ~10-minute~10-min ops-email throttle so an urgent message is pushed immediately.throttle. Rate-limited to 5 calls/hour per tenant5/hour/tenant — a 429 names retryAfter (seconds) when hit..

Warmup + provisioning progress per mailbox. New mailboxes are ramp-limited server-side: 5 sends/day week 1 rising to 40/day after 4 weeks; current dailyCap for each mailbox is in the response below — ramp caps permit CAPPED sending from day 1, never zero until fully warmed. Returns { domains, mailboxes, sendReady, mailboxHealth[], messages[], nextSteps }; each mailbox: warmupDay, dailyCap, sentToday, sendReady, delivStatus (healthy/throttled/paused),. complaint/bounce/softBounceNew ratesmailboxes (first-partyramp-limit measured),server-side: vendorReputationScore5 +sends/day vendorPlacementRateweek (VENDOR-REPORTED1, not40/day first-partyweek measurements4 — the control loop uses local signals only; BOTH ARE null whenever the provider does not reportdailyCap/sentToday them,show whichreal iscapped thesending normalfrom caseday today1, so treat null as 'not measured' and never as zero), lastPolledAt.zero. Per-mailbox `sendReady` is a FULLY-RAMPED flag, NOT a send gate — a mailbox below fullbelow-ramp rampmailboxes still sendssend, capped at itstheir own `dailyCap`; `sendReady` only says warmup has finished, sodailyCap; read `dailyCap`/`sentToday`dailyCap/sentToday for actual send capacity, never `sendReady` alone. Thecapacity. top-levelTop-level `sendReady` is the AND across ALL mailboxes (true only once every one has finishedis rampingramped) — for whether THISone mailboxmailbox's cancapacity senduse rightits now,own theflag. per-mailboxEach flagmailbox nextcarries todelivStatus it(healthy/throttled/paused), iscomplaint/bounce/softBounce therates; onevendorReputationScore/vendorPlacementRate thatare mattersVENDOR-REPORTED, not thenull top-levelwhen one.unmeasured. Vendor-pool warmup (the underlying reputation-building the provider runs) is FEED-INVISIBLE by design: nothing in this response surfaces the vendor's own warmup internals — dailyCap/warmupDay/sendReady here are this platform's own ramp schedule, computed independently of whatever the vendor is doing in its pool, so do not expect a vendor-side warmup event to show up here.design. `messages[]` surfaces system notices this account should act on (e.g. a setup step that needs a retry, a mailbox credential that just went live) — each has kind, severity ('info' = resolves on its own | 'action_required' = nothing progresses until you act, and acting works | 'operator_pending' = the platform has stopped and nothing you change will restart it, but an operator can clear the blocker and then retrying the SAME call with the SAME idempotency key completes it — keep your inputs as they are and do not give up | 'terminal' = the platform has STOPPED, retrying will never help and only a human can move it — the actionHint names contact_operator), body, actionHint (structured — e.g. which tool + idempotencyKey to retry with), createdAt; poll this alongside the mailbox fields — capped at the newestpreviews 5 (operator replies sort first, so system churn cannot evict one, but a 6th DISTINCT unacked message of either kind can still fall off this preview;notices use(severities: list_messages for the complete, paginated history). Reading them here does NOT mark them read — only an explicit ack_message call sets readAt. Unacked operator messages sort first here, then system notices newest-first, so a human reply; isreading never pushed out of the 5 by system churn; list_messages is the full paginatedmarks surface.read. `nextSteps` names what this account should dothe next —action (see setup_infrastructure's description for the discriminated shape.setup_infrastructure). Use account/metrics for account-wide rollups.

 ⟨18 unchanged words⟩ ), cursor-paginated. Unacked messages sort first (newest first within that group), then acked ones (also newest first). Returns { messages[], nextCursor }; each message: id, kind, severity ('info'|'action_required'|'operator_pending'|'terminal' —'info' 'operator_pending'= meansresolves theon platformits hasown stopped,| nothing'action_required' you= changeact restartsand it, andprogresses an| operator'operator_pending' clearing= theplatform blockerstopped, makesonly thean SAMEoperator retrycan work,restart soit, keepretrying the sameSAME inputscall andthen idempotencyworks key;| 'terminal' means the= platform has stopped and, only a human can move it, so do NOT retry), body, actionHint (structured — e.g. which tool + idempotencyKey to retry with), source ('system'|'operator'system|operator), createdAt, readAt. `readAt` is set ONLY by an explicit ack_message call — LISTING messageslisting never marks them, here or anywheremessages elseread, so calling this tool leaves every readAt exactly as it was. Aa null readAt therefore means 'not acked', which is NOT evidence thedoes messagenot wasmean never seen: it may have been read and, simplyonly not yet acknowledged. Use ack_message to acknowledgestop one by id so it stops resurfacing. infrastructure_status also inlines the newest 5 unacked messages for a quick glance —messages; this is the full paginated surface.

Downgrade: release your N NEWEST live mailboxes now and, lowerlowering the billed quantity. Inputs: count, acknowledged (must be true — this is a quoted, irreversible-this-cycle consent: the release is immediate for provisioning but there isirreversible; NOno mid-cycle credit; thecredit, lower price takes effectstarts next renewal, minimum 5 mailboxes / $99mailboxes/$99). Returns { releasedCount, failedCount, unreleased, billing, deduplicated } where billing is the new projected monthly. `releasedCount` is what COMPLETED and can be less than the `count` you asked for; `failedCount` is how many the provider refused, which are STILL LIVE and still billed, and `unreleased` names those addresses — read them before concluding a downgrade landed. `deduplicated: true` means this call did NOT re-perform the downgrade — every count above describes an EARLIER call's already-recorded outcome under the same idempotencyKey, not new work done just now. This can be true even after the 30-day idempotency window itself has expired: the underlying release record persists independently, so a reused key still reports no re-release rather than silently starting a fresh one.. `count` is RELATIVE — it releases (that many MORE mailboxes, it does not set youra fleet to that size — and release cannot be undone through this API, sotarget). ALWAYS pass an idempotencyKey: the FIRST call under a key resolvesfixes WHICH mailboxes to release and records that exact set, sorelease; everya later call carryingwith the SAME key can only ever finish that same set. A same-key retry re-attempts the stragglers and`releasedCount` can neverbe releaseless athan mailbox`count` outside— them,`failedCount` whatevernames `count`how youmany sendthe withvendor itrefused (the recorded setstill winslive, overbilled; a`unreleased` changedlists countthem);. aResend retrywith WITHOUTthe asame key always releases another `count`.until A`failedCount` genuineis SECOND0. downgrade`deduplicated: istrue` therefore= aNO NEWnew keywork — reusing an old one can onlyearlier everrecorded finishoutcome whatunder that key already askedwas for.replayed. A call that came back with failedCount above zero did NOT finish, so its key is not frozen: resend the identical request with the same key until failedCount is 0 — from then on that key replays the finished result and releasesgenuinely nothingNEW further.downgrade Ifneeds a callNEW returnskey. 409 = a release is already running for this account: wait, thenrunning; re-readre-check infrastructure_status before deciding whether to retry.retrying. To ADD mailboxes use setup_infrastructure / configure_byo_domainor (request_managed_mailboxes).configure_byo_domain.

 ⟨17 unchanged words⟩ messageId, deduplicated }. A reply is real sendingsend volume and is, governed exactly like campaign sends: it counts against thatthe mailbox'smailbox daily cap (sentToday +1, visible in infrastructure_status), and it is REFUSED — (never silently dropped —) when the recipient is suppressed, the mailbox is deliverability-paused, or the cap is used up.up A— a refusal returns { error, code:'send_blocked' send_blocked, reason:'suppressed'|'mailbox_paused'|'daily_cap_reached' suppressed|mailbox_paused|daily_cap_reached, retryable }:; retryable (cap) clears at the next daily rollover, non-retryable does not, so— stop retrying, anddo don'tnot loop replies to manufacture volume. Idempotent: identical  ⟨8 unchanged words⟩ stable idempotencyKey (else a body hash is used, matched only 10 minutes) so a dropped-response retry can'tcannot double-send. `deduplicated: true` means= NO new email was sent —sent; `messageId` is from an earlier send this call matched. `deduplicated: false` means this platform sent the call onward as a NEW send, which is normally a new email — but it is not a guarantee one left the building: with NO idempotencyKey the body hash is only matched here for 10 minutes, while the sending provider keeps its own record of an identical body on the same thread for longer, and can collapse a much later repeat into the originalmatching send. So onPass a long-delayed identical repeat you may get `deduplicated: false` with the ORIGINAL send's messageId and no new email. PASS AN IDEMPOTENCYKEYkey, or vary the body, if you need a repeat tomust genuinely go out. 404 if no sending mailbox ⟨6 unchanged words⟩ 

Provision sending infrastructureinfra: buy branded lookalike domains, create mailboxes, start warmup. New mailboxes are ramp-limited server-side — 5 sends/day in week 1, rising to 40/day after 4 weeks — and your own calls cannot exceed that cap; poll infrastructure_status for the current dailyCap. Inputs: brand, primaryDomain, domains + inboxesEach counts(or distribution), persona, physicalAddress, senderIdentity. Billing is per-provisioned-mailbox ($49 platform + per mailbox, graduated: 1-5 at $10, 6-20 at $8, 21+ at $7; 5-mailbox minimum) and the billed quantity follows what you provision here —provisioned passmailbox; quoteOnly:true first to preview the new count + projected monthly price before committing (no silent capacity addition). Every response carries a `billing` projection { provisionedAfter (the live count AFTER this call — reality, not the ask), projectedMonthlyCents, formula }: on quoteOnly it's the preview, on an actual provision it's the real post-provision bill (a capacity-limited partial reflects only what landed). Returns { jobId, billing } — `jobId` is a correlation id only, not a trackable job handle: there is no job store and no endpoint that accepts it, so do not poll for it or treat its presence as meaningful; it exists to correlate this response with logs. A `provisioning` field is present ONLY when the call returned still OWING work, and names which state: 'pending' (a domain's DNS registration is still completing — `pendingDomain` names one of them) or 'capacity_pending' (held at a spend limit, so polling will NOT progress until an operator raises it — call contact_operator instead of waiting). Its ABSENCE is what says the provision finished; the only way to find out is to re-call setup_infrastructure or read infrastructure_status's `nextSteps`. An outcome carrying `provisioning`, and a quoteOnly preview, are deliberately NOT recorded against your idempotencyKey — retrying with the same key re-runs the call and finishes the job rather than replaying the unfinished answer.previews `domains`cost andfirst. `inboxesEach``domains`/`inboxesEach` are the infrastructureinfra you want to HAVE, not an amount to add: each call keeps and resumes what this account already has and buys only the shortfall, so to provision MORE you ask for a LARGER number (domains:2 after a call that provisioned one buys the second; raising inboxesEach tops each domain up). Repeating a call therefore never buys twice, whatever you do with idempotencyKey — resend it, change it, or omit it. The key controls response replay only and has no bearing on what is purchased, so a retry is always safe. A domain this account already registered but that never landed in your account (a prior call that failed after the purchase) is ADOPTED on the retry at zero extra cost rather than bought again. A domain whose DNS setup has not finished yet is recorded and never lost — there is no per-domain DNS field to poll (infrastructure_status reports a domain count, not per-domain detail), so read its `nextSteps` for what to do next, and repeat this same call to converge on the domain and finish its DNS setup. Slot semantics: `domains: N` covers ordinalsnever 0..N-1,buys andtwice; each ordinal 0..domains-1 fills to its own mailbox count (uniform via `inboxesEach`, or per-ordinal via `distribution` — see below); a repeat call at the SAME `domains` provisions nothing new once every ordinal is satisfied, so reaching ordinal 1 needs `domains:2`, not a second `domains:1` call.count. Mailbox addresses are DETERMINISTIC — derived from `persona` + ordinal + slotpersona+ordinal+slot — so keep `persona` EXACTLY as it was on a resume or retry; changing it mid-account does not move existing addresses but does change what a NEW ordinal derives. `distribution` (optional, alternative to `inboxesEach`) names the per-ordinal mailbox count directly — one entry per domain ordinal, e.g. `[3, 2]` for 3 mailboxes on domain 0 andpersona 2unchanged on domain 1 — for a shape `inboxesEach`'s single uniform number cannot express; supply exactly one of the two (an array with `domains` entries, or the uniform count).retry. `registerDomains``registerDomains:true` is this tenant's opt-inrequired consent to real domain purchases made on the platform's own account (our COGS — your bill is unchanged, mailbox-count-based only); only the operator's own global switch being armed too can ever actually enable it. OMITTING it leavesbefore any consent you previously gave UNCHANGED — pass `false` explicitly to revoke it. A call that omitsNEW `registerDomains`domain (orpurchase; sendsomitting it `false`) on a buy-bearing request (one that needs to purchase a newbuy domain)call is refused BEFORE any spend. Once this account has consented at least once, that refusal is a 400 `registrar_optin_missing`: 'registerDomains was not set on this request' — resend the identical call withregistrar_optin_missing it(self-correct setby toresending true to self-correct; this is, never an operator escalation. (An account that has never consented, on a platform where domain registration is not yet enabled at all, instead sees the operator-facing 503 `registrar_unarmed` — indistinguishable from the outside except by status code, but the fix is the same: set `registerDomains: true` and retry.) Separately, a `registerDomains:true` call with NO `registrant` anywhere (neither in this request nor persisted from a prior oneescalation) fails with a 400 `incomplete_registrant` naming the missing fields — also before any purchase. Fresh candidates are de-duplicated against what this account already owns and checked for availability; if a call needs to buy a domain and no available un-owned candidate exists it fails with a 400 naming that, never a silent repeat purchase (a call that needs to buy nothing is unaffected). `registrant` (a full registrant-of-record object { firstName, lastName, email, phone, addressLine1, city, state, country, postalCode, organization (optional, defaults to brand) }) is OPTIONAL even when `registerDomains` is true whenever a complete registrant isunless already on file from a prior call — supplying one makes it authoritative for THIS call; omitting it re-uses the persisted one. This platform never invents a domain registrant's legal identity, so a call with no registrant anywhere (neither supplied nor persisted) is rejected naming the missing fields, at or before the actual purchase — never silently. There isfile. NO background retry exists: a call`provisioning` returningresult `provisioning`(pending|capacity_pending) needs the callerYOU to retry it; the platform does not complete it for you on a timer. Every response carries `nextSteps` (see the discriminatedto `status`/`steps`progress; shape)capacity_pending —needs thecontact_operator account'sinstead. ownReturns next{ actionjobId, computed fresh each timebilling, so a stalled setup isprovisioning?, nevernextSteps silent.}.

 ⟨50 unchanged words⟩  persona, physicalAddress, senderIdentity. Billing is per-provisioned-mailbox ($10/mailbox$49 platform + $49per platformmailbox, mingraduated: 51-5 at $10, 6-20 at $8, 21-100 at $6, 101+ at $5; 5-mailbox minimum) and the billed quantity follows what you  ⟨952 unchanged words⟩ 

 ⟨50 unchanged words⟩  persona, physicalAddress, senderIdentity. Billing is per-provisioned-mailbox ($10/mailbox$49 platform + $49per platformmailbox, mingraduated: 51-5 at $10, 6-20 at $8, 21-100 at $6, 101+ at $5; 5-mailbox minimum) and the billed quantity follows what you  ⟨952 unchanged words⟩ 

 ⟨209 unchanged words⟩ of them) or 'capacity_pending' (held at a spend/plan-slotspend limit, so polling will NOT progress until  ⟨797 unchanged words⟩ 

 ⟨209 unchanged words⟩ of them) or 'capacity_pending' (held at a spend/plan-slotspend limit, so polling will NOT progress until  ⟨797 unchanged words⟩