@shrm80  Following could be the reason:
- Verification delays, usually takes sometime ~ 24hrs
- Check AWS marketplace in Billing
- If all good, raise a support ticket

In the meantime, you could test it with open-weights models (Llama).

no one is helping me out just gettting help is so struggle 

This error is quite specific, and it is probably not a normal permission problem on your side.

The important part is:

Databricks-set rate limit of 0

Databricks is deliberately blocking that model endpoint for your workspace. Databricks documents that a rate limit of 0 effectively disables an endpoint and produces a 403 PERMISSION_DENIED.

Why you're seeing this

Since you said you signed up using AWS, there are two possibilities:

1. You created a Databricks Free Edition workspace, or
2. You created a Databricks trial workspace through AWS Marketplace.

Both have restrictions around model serving/foundation models. Free Edition has explicit Model Serving limitations, including restrictions on certain models and no GPU serving/provisioned throughput.

The similar problem is been resolved here. 

And Databricks documentations also mentions the limitations here. 

i have already upgraded my account from free trial to enterprise but i am still facing the issue and i also tried the limit setup issue is still there ,?

Yes. If you have already upgraded from the Free Trial to Enterprise and the error is still exactly Databricks-set rate limit of 0, then changing the QPM/TPM limit in the UI is not going to fix it.

I checked the current Databricks documentation and recent Databricks employee responses. This is the key distinction:

Your problem is a Databricks system-level restriction

There are effectively two different limits:

• Your endpoint/user-configured limit — the QPM/TPM values you changed.
• Databricks system-level limit — controlled by Databricks for the workspace/model.

Your error:

PERMISSION_DENIED: The endpoint is temporarily disabled due to a Databricks-set rate limit of 0

means the second one is 0.

Databricks employees have specifically confirmed that this restriction takes precedence over the limits configured in Serving/AI Gateway. So you can set QPM/TPM to a non-zero value and still receive the same 403.check here similar issue