Two-credit provider pricing
Proton uses two credits per successfully completed account under the current MailMaker pricing structure.
MAILMAKER PROVIDER
Proton account provisioning inside a multi-provider workflow.
Request Proton tasks without adding another subscription or separate operational dashboard to your stack.
Only successful Proton accounts consume credits. A failed item is guaranteed to use zero credits, and any temporary reservation returns automatically.
Guarantee details →BUILT FOR
Where Proton fits.
- Privacy-product QA workflows
- Provider diversity in test environments
- Task-based automation through the API
Results stay tied to the order
Every Proton request keeps its provider, quantity, credit usage, status history, and result count associated with one task ID.
Privacy-oriented coverage still needs secure operations
Selecting Proton does not automatically secure exported credentials. Define the approved recipient, access-controlled destination, logging exclusions, retention period, and deletion owner before the task begins. Keep raw results out of support tickets and observability systems.
Measure Proton work without copying secrets
Operational reports need the task ID, state, requested count, successful count, failed count, duration, and credit use—not passwords or recovery data. Route account results directly to the restricted destination chosen for the workflow.
Make deletion a verifiable end state
The Proton workflow is not finished when the export is downloaded. Record when the approved purpose ends, who confirms that temporary copies were removed, and which metadata may remain for billing or task audit without preserving raw credentials.
Failed-account credit protection
Only successfully completed Proton accounts consume credits. Every item reported as failed is guaranteed to use zero credits; if 2 credits were reserved during processing, the reservation returns to the workspace automatically. A partial task is charged only for successful output.
Plan Proton volume with real acceptance criteria
A representative pilot uses the real configuration, export format, owner, and downstream destination. At 2 credits per successful account, 10 completed results use 20 credits and 100 use 200. Scale only after the receiving workflow accepts the pilot and returned credits have been reconciled.
Keep the final record explainable
Preserve the Proton task ID with requested, successful, and failed counts, actual credits used, credits returned, result owner, and export destination. If a replacement is approved, include only the unresolved quantity instead of repeating the completed portion of the original task.
PROTON QUESTIONS
Clear answers before an order starts.
What does a Proton account cost in MailMaker?−
The current rate is two credits per successfully created Proton account.
Can Proton task status be retrieved through the API?+
Yes. Store the task ID and retrieve its explicit state until the Proton order completes, partially completes, or fails.
What happens when a Proton account fails?+
The failed item consumes zero credits. Any credit reservation for that item is returned automatically, while successful items in the same task remain valid and chargeable.
Should I validate Proton before ordering in bulk?+
Yes. Use a representative pilot with the real result owner, export format, and downstream destination before increasing quantity.
Review the cost. Run the task.
Start with Proton selected and keep every result tied to a visible order.
Create Proton accounts →