---
title: "Ask for a higher limit: granted at once up to the self-serve ceiling, else an operator decides [org admins]"
method: POST
path: "/preview/limits/requests"
tags: ["limits"]
---

# Ask for a higher limit: granted at once up to the self-serve ceiling, else an operator decides \[org admins\]

`POST /preview/limits/requests`

## Request

- Base URL: `https://autoresearch.sfcompute.com`
- URL: `https://autoresearch.sfcompute.com/preview/limits/requests`
- Auth: HTTP bearer

Ask for a higher limit (org admins only). Pass the limit's name as list_limits shows it, the value you need in the limit's own unit, and a reason. When the value is at or under the limit's self-serve ceiling (list_limits shows it as raisable_to), the org gets exactly that value at once. The answer says granted and when the value takes effect. Otherwise the request goes on a support ticket, and an operator decides. A human reads it, usually within a business day, with no SLA, and get_ticket shows the answer. A value over the ceiling is refused with the ceiling named, unless you pass escalate: true. A value over the platform hard cap (hard_max) is refused, because nobody can grant it. Every answer names the org and states the numbers. An org gets limit_requests_per_org_per_day requests per rolling day.

## Query parameters

- `workspace` string

## Request body

- object
  - `escalate` boolean, nullable: true = when the value is over the self-serve ceiling, file it for an operator to decide instead of refusing. Default false.
  - `limit` string, required: The limit's name, exactly as list_limits shows it (e.g. "job_scratch_bytes").
  - `org` string, nullable: Organization (uuid or name); omitted = the org of the workspace this connection acts in, which is the org your next create bills.
  - `reason` string, required: Why you need it, in one or two sentences an operator reads: the workload and the size it needs. Stays on the request and its ticket. Never paste secrets.
  - `value` integer, required: The value you need, in the limit's own unit (list_limits shows the current one): bytes for a *_bytes limit, GiB for *_gib, minutes for *_minutes. You get exactly this value, never more.

## Response `200`

The capability's JSON result.

- Result: The capability's result: the same object the MCP tool returns as structuredContent. Resources carry an `object` type discriminator and an immutable id; money is integer micro-dollars in `*_usd_micros` fields.
  - `object` string: The resource type, when the result is one resource.

## Other responses

- `400`: Malformed request: bad JSON, a parameter that does not parse, or a value outside its range. Code `invalid`.
- `401`: No bearer token, or one this API cannot verify. Code `unauthenticated`.
- `403`: Authenticated, but the token's scopes or the account's role do not reach this operation. The message names the scope word to request. Code `forbidden`.
- `404`: No such route. Code `not_found`; the body names the OpenAPI document.
- `422`: A well-formed request the platform declined: no such node, a cap reached, a state that forbids the move. The message says which, and what to do instead. Code `refused`.
- `429`: Over this door's per-customer budget. Wait `Retry-After` seconds. Code `rate_limited`.
- `500`: Our fault. Retry; if it persists, quote the request-id. Code `internal`.

---

[API](https://skmtc.dev/givemeanode/apis/autoresearch-customer-api.md) · [All operations](https://skmtc.dev/givemeanode/apis/autoresearch-customer-api/llms.txt) · [OpenAPI document](https://skmtc.dev/givemeanode/apis/autoresearch-customer-api/revisions/f88dcb70ac6c?raw)