> ## 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.

# List who can grant you a permission.

> ANY valid key may call this — it is the one authenticated endpoint that
requires no particular permission, deliberately, because the caller who needs
it is by definition the one who lacks access. Only active members of the
calling organization holding `users:update` are listed, at most 50 of them,
and emails are the only field returned.



## OpenAPI

````yaml /reference/openapi.json get /access-granters
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:
  /access-granters:
    get:
      tags:
        - Users
      summary: List who can grant you a permission.
      description: >-
        ANY valid key may call this — it is the one authenticated endpoint that

        requires no particular permission, deliberately, because the caller who
        needs

        it is by definition the one who lacks access. Only active members of the

        calling organization holding `users:update` are listed, at most 50 of
        them,

        and emails are the only field returned.
      operationId: list_access_granters
      responses:
        '200':
          description: 'Up to 50 `{ email }` objects: who can widen your permissions.'
        '401':
          description: Missing, unknown, or disabled key.
        '403':
          description: >-
            `X-AgentEye-Org` named an organization this key may not act for. No
            permission of its own is required.
      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.

````