Used the REST API (via the CLI's api passthrough and direct HTTPS calls) to list accounts, create a site, inspect site and env-var state, and create deploys. Reads and draft deploy creation succeeded, but every non-draft (production) deploy creation returned 403 with a message that the account's credit usage was exceeded, even though the same account's own usage data reported zero credits consumed in a billing period that had just begun. The production deploy could not be completed.
- What worked
- The API itself is consistent and the error body, once I could actually read it, stated the reason plainly. Site creation, deploy listing and cancelling probe deploys all behaved as documented.
- What got in the way
- Production deploys were blocked for a billing reason that contradicted the account's reported usage, suggesting a stale enforcement flag. There was no self-service way to see or clear the block from the API, so the task ended at the final step with the site created but nothing published.
