Arcads API Pricing and Credits: What to Verify Before Automation

If you are searching for Arcads API pricing, separate two questions: what your current Arcads plan charges for generation, and what your automation is allowed to create. The referenced Arcads API documentation explains credentials and endpoints but does not publish a universal per-request price. Arcads' MCP documentation states that video generation consumes credits from an active subscription and points users to the billing dashboard for plan, upgrade, and top-up details.

That makes the live billing view—not a copied number in an integration—the authoritative cost source. This checklist gives an automation a safe boundary even when plan pricing changes.

The two official checks

1. Review the Arcads AI API documentation for current credential, authorization, and endpoint details.
2. Confirm the active plan and remaining credits in the Arcads billing dashboard. The Arcads MCP documentation explicitly says generation consumes plan credits and requests fail without an active subscription or remaining credits.

A pricing-safe preflight

1. Record the plan, remaining-credit reading, and timestamp immediately before enabling generation.
2. Use a read-only product-list request to verify authentication and select valid product IDs before any write.
3. Write down the requested video count, the current credit cost per unit shown in the account, and a hard retry ceiling.
4. Require an approval payload containing the exact batch size and maximum permitted credit consumption.
5. Attach an idempotency key to the business request so retries cannot create a second paid job.
6. Poll an existing job with a bounded schedule. A timeout must stop safely, not submit again.
7. Stop when the credit reading is missing, stale, or below the approved reserve.

Use a formula, not a stale price

For an approved batch, calculate: planned credits = approved units × current per-unit credit cost. Then calculate a separate retry allowance. The automation may proceed only when planned credits plus the retry allowance stays below both the account balance and the written approval ceiling.

Do not silently substitute an old public price, infer credits from a previous invoice, or treat HTTP retries as permission to create another generation job.

Acceptance test before production

• A missing approval produces zero generation requests.
• A duplicate business request returns the existing job reference.
• A batch above the written ceiling is rejected before generation.
• An unknown or insufficient credit balance fails closed.
• A successful test records the approved quantity, selected product, job ID, and final status without exposing credentials.

Need a concrete boundary for your workflow? Use FlowPatch's private Arcads API scope generator or review the $299 fixed-scope Patch Pilot. The first $149.50 milestone is due only after written scope acceptance.

Try the calculation

Use the free Arcads credit safety calculator to check a batch, replacement allowance, reserve, and remaining-credit headroom in your browser. No entered value is submitted or saved.

FlowPatch is independent and is not affiliated with or endorsed by Arcads. Verify current plan and credit details in your own Arcads account. Updated August 31, 2026.