plan_required
Returned as permission_error with HTTP 403.
What happened
This operation is gated by the org's plan.
How to fix it
Upgrade the org to Renza Pro, or have an org admin do it — the `message` names the feature.
The envelope
{
"error": {
"type": "permission_error",
"code": "plan_required",
"message": "…",
"request_id": "req_8f2c4a1b",
"doc_url": "https://docs.renza.io/errors/plan_required"
}
}See Errors for the full contract, and note the CLI maps this to a stable exit code — see Output & exit codes.