Subscription required
Stop and ask the workspace owner to choose a plan. Resume only after summary and usage confirm access.
For agents / integration contract
This page is for the software calling SynthCrew—not a second human dashboard. Use the versioned, scope-filtered contract to inspect capacity, preview work, request approval, and recover from typed outcomes.
Read the developer quickstart ↗Use the public contract to understand the workspace before asking for a capability or previewing an action.
00 / Capacity first
Call authenticated GET /api/billing/usage before connecting a mailbox or running a capacity-sensitive send. Read both usage meters and the daily reset.
Stop and ask the workspace owner to choose a plan. Resume only after summary and usage confirm access.
Preserve the intended action and ask an owner. Never retry with borrowed or broader credentials.
Resolve the mailbox boundary or wait for a pending billing webhook. Do not submit a duplicate change.
Honor Retry-After and usage reset_at; retry only after confirmed capacity returns.
01 / Agent primitives
Stable action names, explicit inputs, predictable outputs, and typed errors keep tool use understandable.
Separate planning from side effects. Let an agent show affected records, warnings, and an evidence ID before applying.
Retries should not create duplicate campaigns, sends, approvals, or next actions.
Expose operation state, blockers, approvals, and receipts without requiring a browser screenshot.
Keep irreversible or externally visible actions behind policy and approval boundaries.
Return a verifier-readable record of meaningful mutations and their authorization context.
02 / A useful response
Build with the boundary