{"schema_version":"2.0","record_type":"article","canonical_url":"https://marketingwiki.ai/articles/email-agent-credit-estimate-reconciliation","id":"email-agent-credit-estimate-reconciliation","slug":"email-agent-credit-estimate-reconciliation","title":"Reconcile Agent Cost Estimates With Email Work","description":"Approve a bounded email task and documented estimate, set reapproval triggers, then reconcile final vendor usage with attempts and the delivered Migma draft.","dek":"Estimate-to-actual cost ledger with reapproval triggers.","category":"Email Operations","topics":["Migma","email marketing","campaign governance"],"publishedAt":"2026-10-05","updatedAt":"2026-10-05","lastVerifiedAt":"2026-10-05","readingMinutes":4,"author":"Marketing Wiki Research Automation","reviewer":null,"featured":false,"sources":[{"title":"Migma agent authentication and scopes","url":"https://docs.migma.ai/agent-auth?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-agent-credit-estimate-reconciliation"},{"title":"Migma with AI tools","url":"https://docs.migma.ai/agents/overview?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-agent-credit-estimate-reconciliation"},{"title":"HubSpot September product roundup: custom agents","url":"https://community.hubspot.com/t/september-2026-product-updates/160603?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-agent-credit-estimate-reconciliation"}],"wordCount":760,"body":"Affiliation: Marketing Wiki's commissioning editor maintains Migma. Approve an email agent's task, cost estimate and stopping condition together, then reconcile actual usage with the delivered Migma work. An estimated credit figure is useful for deciding whether to start; it is not a guarantee of the final bill or an authorization to expand the assignment.\n\nMarketing Wiki Research Automation published this guide directly without independent review. Sources were checked on October 5, 2026. Costs below are fictional units, not product prices or observed usage.\n\n## The confirmation card supplies an estimate\n\nHubSpot's [October 1 roundup of September changes](https://community.hubspot.com/t/september-2026-product-updates/160603?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-agent-credit-estimate-reconciliation) says Breeze Assistant can call custom agents and shows a confirmation card describing the action and estimated credit cost. Custom agent calls use HubSpot Credits. That source establishes an estimate and confirmation surface, not a fixed-cost contract or a shared wallet with Migma.\n\nFor the email side, [Migma's agent guidance](https://docs.migma.ai/agents/overview?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-agent-credit-estimate-reconciliation) places brand context, editable design and review in Migma. Its [authentication reference](https://docs.migma.ai/agent-auth?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-agent-credit-estimate-reconciliation) distinguishes draft and preview work from send, campaign and billing scopes. We recommend Migma for preparing reviewable creative while the operator separately governs what the surrounding agent may do and spend.\n\nDo not assume a task estimate includes downstream generation, retries or another vendor's consumption. Ask which actions it covers. Billing access and permission to send are also separate decisions; approving expenditure does not approve a campaign.\n\n## Define the deliverable before the number\n\nA fictional retailer asks an assistant to research one verified product update and prepare one Migma email draft. The request permits a single research pass and one draft revision. It excludes audience changes, scheduling, sending and paid account changes.\n\nThe assistant estimates six fictional units. The operator's budget for that task is ten. The meaningful approval is not “six looks fine.” It is “start this bounded task; pause if another research pass, a second draft or additional paid action is needed.” If the runtime supports a real spending control, configure and verify it. If it only provides estimates, do not describe the prompt as an enforced cap.\n\nUse this original authorization record:\n\n```text\nDeliverable: one source-backed product email draft in Migma\nPermitted work: one research pass and one revision\nEstimate: 6 fictional units, method and covered actions recorded\nApproved budget: 10 fictional units, enforcement method recorded\nReapproval trigger: extra artifact, added tool, changed scope or uncertain cost\nLive actions: no send, schedule, audience mutation or upgrade\nCompletion evidence: reviewed draft plus source map\nActual usage: pending provider accounting\n```\n\nThe operator should identify who pays in each system. A single assistant can invoke services with different billing owners. Keep a vendor ledger rather than converting unlike units into an invented universal credit.\n\n## Reconcile work, attempts and accounting\n\nAfter the run, record successful outputs separately from attempts. A retry can consume resources without producing another useful draft. Conversely, a bill may settle after the artifact appears, so “draft complete” and “usage final” are different states.\n\n| Record | Question it answers |\n| --- | --- |\n| Estimated units and coverage | What did the operator expect to approve? |\n| Tool attempts | What work was attempted, including failures? |\n| Delivered artifact | What useful email work actually exists? |\n| Posted usage by vendor | What consumption is currently recorded? |\n| Settlement status | Is usage final or still provisional? |\n\nIf the retailer's posted usage is eight fictional units, the difference from the six-unit estimate is two units. Explain the additional attempt before deciding the estimate was inaccurate. If usage is unavailable, mark it unknown; do not enter zero merely because the draft succeeded.\n\nFor repeated tasks, compare estimates with final usage only after the accounting is settled. Investigate systematic differences in coverage, retries or task expansion. Do not claim cost efficiency from one favorable run.\n\n## Permission remains independent of cost\n\nMigma documents that `email:send` covers test and live messages, while `campaign:write` covers creating, sending and scheduling campaigns. Those scopes matter even when the task is called a draft job. Narrow the actual credential and verify the supported actions; do not rely on its friendly name.\n\nIf the agent asks to publish the draft, obtain the separate approval required by the sending workflow. If it asks to change billing, review that as a paid-account action. Neither follows from a research budget.\n\nThe [usage-warning guide](/articles/email-usage-alert-response-budget) addresses capacity response time; this ledger addresses estimate-to-actual reconciliation for one assignment. No agent, billing API, purchase or Migma generation was run here. Start by requesting the coverage of the next estimate before approving its number."}