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

# Discover the MCP authorization server (compatibility alias)

> API-prefixed compatibility alias for the canonical RFC 8414 metadata path.



## OpenAPI

````yaml /api-reference/openapi.json get /credits/mcp/oauth/.well-known/oauth-authorization-server
openapi: 3.1.0
info:
  title: Locus Pro API
  description: >-
    Production is live at https://api.paywithlocus.com/api. Stage remains
    available for evaluation and integration testing at
    https://api.stage.paywithlocus.com/api; credentials, balances, and tenant
    data are isolated by environment. Embedded prepaid credits over the Locus
    pay-per-use catalog. Money and top-up amounts use exact decimal strings (up
    to 6dp). Every burn requires an Idempotency-Key header. Management routes
    accept a tenant secret key or authorized dashboard session as shown per
    operation. Widget routes accept an end-user JWT alone; when a publishable
    key is present it must belong to the JWT's tenant. MCP uses OAuth 2.1
    Authorization Code with PKCE by default and also accepts the explicitly
    documented tenant secret key, end-user JWT, or scoped agent connection
    compatibility credentials. Burns accept the execution credentials shown per
    operation. Publishable keys never authorize management or burns by
    themselves.
  version: 0.6.0
servers:
  - url: https://api.paywithlocus.com/api
    description: Production
  - url: https://api.stage.paywithlocus.com/api
    description: Stage — evaluation and integration testing
security:
  - secretKey: []
tags:
  - name: Authentication
    description: Email-verified self-serve account creation and dashboard identity
  - name: Tenants
    description: Tenant profile, keys, and settings (dashboard session or secret key)
  - name: Workspace members
    description: Invite-only human workspace membership and role administration
  - name: Catalog
    description: Enable/disable APIs and set markups
  - name: Custom APIs
    description: >-
      Available when enabled for the workspace. Enterprise BYOK providers and
      schema-backed custom actions
  - name: End users
    description: End-user accounts, tokens, and allocations
  - name: Top-ups
    description: Locus-hosted checkout top-ups and quotes
  - name: Ledger
    description: Burn/top-up history and earnings
  - name: Webhooks
    description: Signed events, delivery inspection, and replay
  - name: Burn
    description: Metered pay-per-use calls
  - name: Travel routing
    description: >-
      Available when enabled for the workspace. Multi-provider flight search,
      no-dispatch planning, and feedback
  - name: MCP
    description: Stateless Streamable HTTP transport and MCP tool-result contracts
  - name: Okibi Identity
    description: >-
      Available when enabled for the workspace. Okibi identity verification and
      scoped native CLI credential bootstrap
  - name: Widget
    description: End-user JWT surface; a matching publishable key is optional
  - name: Agent-native onboarding
    description: >-
      Self-registration, human Stripe funding handoff, and restricted account
      setup for headless agents
  - name: Agent connections
    description: Scoped, expiring, revocable credentials for agent execution
  - name: Capability routing
    description: Outcome-level web search and research across eligible catalog providers
paths:
  /credits/mcp/oauth/.well-known/oauth-authorization-server:
    get:
      tags:
        - MCP
      summary: Discover the MCP authorization server (compatibility alias)
      description: >-
        API-prefixed compatibility alias for the canonical RFC 8414 metadata
        path.
      responses:
        '200':
          description: Authorization-server metadata
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/McpAuthorizationServerMetadata'
      security: []
components:
  schemas:
    McpAuthorizationServerMetadata:
      type: object
      required:
        - issuer
        - authorization_endpoint
        - device_authorization_endpoint
        - token_endpoint
        - registration_endpoint
        - revocation_endpoint
        - response_types_supported
        - response_modes_supported
        - grant_types_supported
        - token_endpoint_auth_methods_supported
        - revocation_endpoint_auth_methods_supported
        - code_challenge_methods_supported
        - scopes_supported
        - authorization_response_iss_parameter_supported
        - resource_parameter_supported
        - client_id_metadata_document_supported
      properties:
        issuer:
          type: string
          format: uri
        authorization_endpoint:
          type: string
          format: uri
        device_authorization_endpoint:
          type: string
          format: uri
        token_endpoint:
          type: string
          format: uri
        registration_endpoint:
          type: string
          format: uri
        revocation_endpoint:
          type: string
          format: uri
        response_types_supported:
          type: array
          items:
            type: string
          example:
            - code
        response_modes_supported:
          type: array
          items:
            type: string
          example:
            - query
        grant_types_supported:
          type: array
          items:
            type: string
            enum:
              - authorization_code
              - refresh_token
              - urn:ietf:params:oauth:grant-type:device_code
        token_endpoint_auth_methods_supported:
          type: array
          items:
            type: string
          example:
            - none
        revocation_endpoint_auth_methods_supported:
          type: array
          items:
            type: string
          example:
            - none
        code_challenge_methods_supported:
          type: array
          items:
            type: string
          example:
            - S256
        scopes_supported:
          type: array
          items:
            type: string
            enum:
              - mcp:read
              - mcp:execute
              - offline_access
        authorization_response_iss_parameter_supported:
          type: boolean
          const: true
        resource_parameter_supported:
          type: boolean
          const: true
        client_id_metadata_document_supported:
          type: boolean
          const: true
      additionalProperties: false
  securitySchemes:
    secretKey:
      type: http
      scheme: bearer
      description: Tenant secret key (lcr_…). Server-side only.

````