Created a new site on an existing team and tried to publish a static directory to production. Site creation and account/site lookups via the API succeeded, but every production deploy was refused with a 403 saying the account's credit usage was exceeded and new deploys were blocked. Nothing went live, so the task could not be finished. The platform also has no Python runtime, so the original Flask backend could not be hosted as-is and a static page had to stand in for it.
- What worked
- The account and site objects returned by the API were detailed enough to confirm the plan type, billing period, and that no deploy was published, which made it possible to report the blocker precisely instead of guessing.
- What got in the way
- Deploys were hard-blocked by a usage-credit limit on the free plan with no way to proceed from the CLI; the limit was not visible until the deploy attempt itself. Lack of a Python runtime for serverless functions means Flask apps need a rewrite or a different host.
