> ## Documentation Index
> Fetch the complete documentation index at: https://docs.superdocs.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Request higher document/chat scale limits in one call — no email needed.

> Request a higher scale limit for your account in ONE call.

WHEN TO USE: after any 413 with error_code DOCUMENT_TOO_COMPLEX (a single
document crossed the standard per-document page limit) or SESSION_TOO_FULL
(the documents open in one chat crossed the standard per-chat limit). These
are stability limits, not hard caps: the platform supports larger
deployments, and limits are raised per account on request.

WHAT HAPPENS: the SuperDocs team is notified immediately with your account
identity and the numbers you send; limits are typically expanded within a
day and you are contacted at your account email. No email writing needed —
though hello@superdocs.app also works if you prefer.

ALTERNATIVES while you wait: split the file into smaller documents, upload
it as an attachment (reference/search, not editing), start another session
for additional documents (init_session), or close documents you no longer
need (close_session_document).



## OpenAPI

````yaml /openapi.json post /v1/limits/increase-request
openapi: 3.1.0
info:
  title: Universal Document AI API
  description: AI-powered document editing with multi-tenant organization support
  version: 2.0.0
servers: []
security: []
paths:
  /v1/limits/increase-request:
    post:
      tags:
        - v1
        - mcp
        - account
      summary: Request higher document/chat scale limits in one call — no email needed.
      description: >-
        Request a higher scale limit for your account in ONE call.


        WHEN TO USE: after any 413 with error_code DOCUMENT_TOO_COMPLEX (a
        single

        document crossed the standard per-document page limit) or
        SESSION_TOO_FULL

        (the documents open in one chat crossed the standard per-chat limit).
        These

        are stability limits, not hard caps: the platform supports larger

        deployments, and limits are raised per account on request.


        WHAT HAPPENS: the SuperDocs team is notified immediately with your
        account

        identity and the numbers you send; limits are typically expanded within
        a

        day and you are contacted at your account email. No email writing needed
        —

        though hello@superdocs.app also works if you prefer.


        ALTERNATIVES while you wait: split the file into smaller documents,
        upload

        it as an attachment (reference/search, not editing), start another
        session

        for additional documents (init_session), or close documents you no
        longer

        need (close_session_document).
      operationId: request_limit_increase
      parameters:
        - name: authorization
          in: header
          required: false
          schema:
            anyOf:
              - type: string
              - type: 'null'
            title: Authorization
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/LimitIncreaseRequest'
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      security:
        - HTTPBearer: []
components:
  schemas:
    LimitIncreaseRequest:
      properties:
        kind:
          type: string
          enum:
            - document_scale
            - session_scale
            - other
          title: Kind
          description: >-
            What you hit: 'document_scale' = a single document crossed the
            per-document page limit (413 DOCUMENT_TOO_COMPLEX); 'session_scale'
            = the documents open in one chat crossed the per-chat limit (413
            SESSION_TOO_FULL); 'other' = anything else (explain in note).
          default: document_scale
        attempted_pages:
          anyOf:
            - type: integer
              maximum: 10000000
              minimum: 0
            - type: 'null'
          title: Attempted Pages
          description: >-
            Approximate page count you were trying to work with (from the 413
            message).
        attempted_sections:
          anyOf:
            - type: integer
              maximum: 10000000
              minimum: 0
            - type: 'null'
          title: Attempted Sections
          description: >-
            Exact section count from the 413 detail (section_count /
            document_section_count), if you have it.
        filename:
          anyOf:
            - type: string
              maxLength: 255
            - type: 'null'
          title: Filename
          description: The file that hit the limit, if any.
        note:
          anyOf:
            - type: string
              maxLength: 2000
            - type: 'null'
          title: Note
          description: >-
            Anything else that helps us size your limits (workload, cadence,
            deadline).
      type: object
      title: LimitIncreaseRequest
      description: Body for request_limit_increase — the one-call limit-expansion request.
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
      type: object
      required:
        - loc
        - msg
        - type
      title: ValidationError
  securitySchemes:
    HTTPBearer:
      type: http
      scheme: bearer

````