Envelop Operators API

openapi: 3.2.0
info:
  title: Fast Operators API
  version: 0.1.0
tags:
- name: Operators
paths:
  /v2/operators/{operator_address}:
    get:
      summary: 'EnvelopV2: LP managers an address operates, across chains (public)'
      description: 'Every EnvelopV2 LP manager this address is an active operator of, on any indexed chain.


        Public endpoint - no `Authorization` header required.


        ```json

        [

        {

        "chain_id": 42161,

        "manager_address": "0x60723973abf3bbc2ce7eb4400b728390d55e264b",

        "allowed_since_block": 487466603,

        "indexed_to_block": 487500000

        }

        ]

        ```


        The reverse of `/v2/managers/{chain_id}/{manager_address}/operators`, and the question

        that has no on-chain answer at all: asking the chain would mean walking every manager

        of every network, and the per-manager enumeration reverts on the deployed clones

        anyway. "Where else is this key still authorised" is what an operator bot and whoever

        is rotating a key need, and today nothing can answer it.


        `indexed_to_block` is per row, not per response: the chains are indexed by independent

        grabbers, so one number for the whole answer would have to be the slowest of them and

        would understate every other chain. `allowed_since_block` is the grant currently in

        force; a re-grant moves it forward.


        Ordered by `(chain_id, manager_address)`. Not paginated: the result is bounded by the

        number of managers that ever granted this address.


        An empty array is a real answer - this address holds no active grant on any chain whose

        LP handlers are on - and revocations are already folded out, so a row here means the

        grant stands as of that row''s `indexed_to_block`. The address is not validated: an

        address that never appears in any log is indistinguishable from a malformed one, and

        both are honestly "no active grants". `500` if the set of indexed chains cannot be

        read, or if none of them can say how far it has been walked; that, not an empty array,

        is the "index cannot answer" state. A chain that cannot state its cursor is dropped

        from the search rather than contributing rows with a null `indexed_to_block`.


        Sources: `public.lp_events` (decoding view over `public.raw_lp_manager` - the

        OperatorSet logs) and `public.event_state` (which chains are indexed, and how far).'
      operationId: v2_operator_managers
      parameters:
      - name: operator_address
        in: path
        required: true
        schema:
          type: string
          title: Operator Address
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Operators
components:
  schemas:
    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:
    APIKeyHeader:
      type: apiKey
      in: header
      name: Authorization
    JwtAccessBearer:
      type: http
      scheme: bearer
    HTTPBasic:
      type: http
      scheme: basic