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

# Preview the context window a model resolves to.

> Returns the effective limit and its authoritative `source`: `override` (this
org configured it), `default` (AgentEye's built-in table), or `unknown` (no
limit known, so no context-fill percentage is computed). Deliberately does
not consult the cache, so it reports the true source rather than a cache hit.

The model id travels in the `model` QUERY parameter, not the path, so ids
containing `/` need no percent-encoding.



## OpenAPI

````yaml /reference/openapi.json get /settings/model-context-windows/resolve
openapi: 3.1.0
info:
  title: AgentEye API
  description: >-
    The AgentEye observability API.


    Every path below is relative to `/v1` on your deployment's dashboard origin
    — e.g. `https://app.example.com/v1/sessions`. Authenticate with a scoped API
    key as a bearer token.


    Organization scoping: a key belongs to one organization and acts on it
    automatically. An instance-scoped key selects one per request with the
    `X-AgentEye-Org` header; without it, such a key resolves to the default
    organization, so set it explicitly on a multi-org deployment.
  license:
    name: MIT
    identifier: MIT
  version: 0.0.1-beta.77
servers:
  - url: /v1
    description: This deployment
security:
  - api_key: []
tags:
  - name: Events
    description: Ingest and query the event store.
  - name: Sessions
    description: Agent sessions and their evaluations.
  - name: Evaluations
    description: Evaluation results and re-runs.
  - name: Dashboards
    description: Dashboards and their tiles.
  - name: Queries
    description: Saved SQL and ad-hoc query execution.
  - name: Keys
    description: Mint and manage scoped API keys.
  - name: Users
    description: Dashboard members and access.
  - name: Settings
    description: Operational settings and context-window overrides.
  - name: Permission sets
    description: Named permission roles.
  - name: Alerts
    description: Alert rules and their recipients.
  - name: Issues
    description: Open, triage, assign and resolve issues.
  - name: Audits
    description: Recurring audits and their findings.
  - name: Usage
    description: Organization usage and billing windows.
  - name: Health
    description: Liveness.
  - name: Auth
    description: Describe the key you are calling with.
paths:
  /settings/model-context-windows/resolve:
    get:
      tags:
        - Settings
      summary: Preview the context window a model resolves to.
      description: >-
        Returns the effective limit and its authoritative `source`: `override`
        (this

        org configured it), `default` (AgentEye's built-in table), or `unknown`
        (no

        limit known, so no context-fill percentage is computed). Deliberately
        does

        not consult the cache, so it reports the true source rather than a cache
        hit.


        The model id travels in the `model` QUERY parameter, not the path, so
        ids

        containing `/` need no percent-encoding.
      operationId: resolve_model
      parameters:
        - name: model
          in: query
          description: The model id to resolve, e.g. `anthropic/claude-sonnet-4`.
          required: true
          schema:
            type: string
      responses:
        '200':
          description: The effective `context_window` and its `source`.
        '400':
          description: '`model` is missing or empty.'
        '401':
          description: Missing, unknown, or disabled key.
        '403':
          description: The key lacks `settings:read`.
      security:
        - api_key: []
components:
  securitySchemes:
    api_key:
      type: http
      scheme: bearer
      description: >-
        A scoped AgentEye API key. Mint one in the dashboard under Settings →
        API keys, or with `POST /v1/keys`. Each endpoint names the permission it
        requires; a key without it gets 403 and a `required_permission` field
        naming what was missing.

````