Playground errors

This reference covers verified Toolswitch playground responses. It is not an API resale interface or a complete list of provider errors.

| HTTP | reasonKey | Meaning | | --- | --- | --- | | 401 | unauthenticated | Sign in again. | | 400 | invalid_input | Check the submitted inputs. | | 404 | endpoint_not_found | The requested endpoint was not found. | | 403 | path_params_unsupported | The playground does not support this tool's path parameters. | | 403 | over_playground_cap | The estimated request cost exceeds the playground limit. | | 403 | batch_disabled | This trial batch is unavailable under the current policy. | | 403 | billing_frozen | Billing is frozen for this account. | | 403 | user_blocked | This account is blocked from trials. | | 402 | insufficient_balance | The available balance cannot cover the reservation. | | 409 | idempotency_conflict | The request identifier has already been claimed. | | 429 | personal_quota_reached | Upstream treg tag_blocked or tag_spend_cap_reached maps to this key. | | 429 | service_unavailable | Other non-team-level treg errors map to this key. | | 503 | service_unavailable | The service is temporarily unavailable. |

The upstream header x-treg-error: 1 identifies a treg error. Team-level errors, including treg's insufficient_balance and platform_daily_cap_reached, are hidden behind HTTP 503 with service_unavailable; they do not mean that your Toolswitch balance is insufficient.

For unknown errors, see the upstream response or documentation; Toolswitch does not invent error definitions. A provider failure may appear inside the playground result rather than as a top-level reasonKey.