Skip to main content
API and MCP generation use your existing Podcastor credits and subscription benefits. There is no separate API balance or channel-specific price multiplier. Equivalent work follows the same credit checks, charges, refunds and storage rules as the Web app.

​
Podcastor plans

Monthly plan-card snapshot from podcastor.ai/pricing, checked September 14, 2026. Prices are in USD.
The live page’s comparison table differs from its plan cards for some prices and Trial credits. This snapshot uses the monthly cards. Check the current plan and checkout for the amount and benefits that apply to your purchase.
Paid plans offer access to all listed TTS models. Video Starter and Creator Pro include access to all listed video models. Creator Pro advertises a 10% creation discount. Model availability and allowances follow the active subscription. Quota summary returns the selected Space owner’s plan and shared Web credit balance.

​
Estimate a generation

  1. Read quota summary for the current plan, included credits and remaining balance.
  2. Select your voices, models and project settings. Audio generation, voice or avatar creation, images and video rendering can incur their existing Web charges.
  3. After preparing the project, call Render credit check for its render estimate.
  4. Submit the render only after reviewing the estimate. A render estimate does not include all earlier script, audio or asset generation and does not reserve credits.
The marketing page’s approximate audio/video minutes are examples of what a plan can produce, not a fixed per-minute API tariff. Cost depends on the selected models, content and active plan.

​
Project and task pricing

The saved project type, selected host and Space owner’s plan determine rendering prices. The current render rules are shared by Web, API and MCP: A solo Podcast uses the standard rate unless its selected host is a pet or cartoon, which uses the FunCast rate. Save the final host and presentation settings before requesting a render estimate. The server derives the pricing category from the project; create_from is not a public price selector. Motion generation uses the configured Web price for its model, duration and resolution. A multi-camera request can create multiple charged motions. Same-screen avatar photo generation also includes the existing image-splitting charge; ordinary background and cover images do not create split host assets. These asset-generation charges are separate from the final render estimate. Task billing origins are assigned by the server, so clients do not send from_for_pay or task_from.

​
Credit and storage lifecycle

  • Subscription credits do not carry over to the next subscription cycle.
  • Top-up credits do not expire, but require an active subscription to use.
  • Annual subscriptions issue their annual credits upfront; see the live pricing page for annual purchase amounts.
  • Taxes, where applicable, are shown at checkout.
  • API and MCP outputs use the same project storage and plan retention as Web outputs. They do not receive an extra storage allocation.
Retries and failures follow the existing operation’s compensation rules. A client timeout alone does not prove that generation failed or that a charge was refunded. Read task status before retrying.