A community reply cannot lift the limit - that trust-tier change is Databricks-side only - but a few things that may help.
What is happening: pay-per-token Foundation Model endpoints are gated to PAYABLE_VERIFIED workspaces. Attaching a card does not always flip the tier right away; it typically moves after the account clears identity verification and has had at least one settled billing cycle of real (non-credit) usage. Trial credits alone do not satisfy the "payable" gate, so you stay on TRIAL_VERIFIED and every pay-per-token endpoint shows a rate limit of 0.
Workarounds that do not depend on the tier change:
- External model endpoint. Register your own OpenAI / Anthropic / Google API key as a served entity in Model Serving. You still call the unified /serving-endpoints API and get the AI Gateway features (rate limits, usage tracking), but billing goes to that provider rather than through the gated Databricks pay-per-token path. This works on any tier.
- Provisioned throughput endpoint instead of pay-per-token, if you specifically need an open model hosted on Databricks. You pay for allocated capacity directly, and it is a different path from the pay-per-token trust-tier gate. More expensive at low volume, but usable today.
- If you need GLM specifically, check whether the pay-per-token GLM endpoint is even offered in your workspace region - availability varies by region and an unavailable model can also surface as a 0 limit.
Escalation: since standard Support closed it, the route that tends to work is Account Console > Contact us / billing support (billing questions are handled without a support contract), or your Databricks account rep if you have one. It is also worth tagging a community moderator here - trust-tier tickets can sometimes be routed internally from the forum.