find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/beatra-ai:beatra-ai-mcp-device-authorization-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  title: agent_service (api) MCP Device Authorization API
  version: 0.1.0
tags:
- name: mcp-device-authorization
paths:
  /.well-known/oauth-authorization-server:
    get:
      tags:
      - mcp-device-authorization
      summary: Device Authorization Server Metadata
      operationId: device_authorization_server_metadata__well_known_oauth_authorization_server_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                additionalProperties: true
                type: object
                title: Response Device Authorization Server Metadata  Well Known Oauth Authorization Server Get
  /oauth/device_authorization:
    post:
      tags:
      - mcp-device-authorization
      summary: Oauth Device Authorization
      operationId: oauth_device_authorization_oauth_device_authorization_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /oauth/token:
    post:
      tags:
      - mcp-device-authorization
      summary: Oauth Device Token
      operationId: oauth_device_token_oauth_token_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /oauth/device/revoke:
    post:
      tags:
      - mcp-device-authorization
      summary: Oauth Device Self Revoke
      description: 'Device-side uninstall: a Device Token revokes its own connection.


        Authenticated by the token itself — a token can only ever revoke the

        connection it belongs to, so there is nothing else to authorize. The

        response never carries identifiers; the caller already knows who it is.'
      operationId: oauth_device_self_revoke_oauth_device_revoke_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /device:
    get:
      tags:
      - mcp-device-authorization
      summary: Device Entry
      operationId: device_entry_device_get
      responses:
        '200':
          description: Successful Response
          content:
            text/html:
              schema:
                type: string
  /device/lookup:
    post:
      tags:
      - mcp-device-authorization
      summary: Device Lookup
      operationId: device_lookup_device_lookup_post
      responses:
        '200':
          description: Successful Response
          content:
            text/html:
              schema:
                type: string
  /device/activate/{device_authorization_id}:
    get:
      tags:
      - mcp-device-authorization
      summary: Device Activation
      operationId: device_activation_device_activate__device_authorization_id__get
      parameters:
      - name: device_authorization_id
        in: path
        required: true
        schema:
          type: string
          title: Device Authorization Id
      responses:
        '200':
          description: Successful Response
          content:
            text/html:
              schema:
                type: string
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
  /device/activate/{device_authorization_id}/decision:
    post:
      tags:
      - mcp-device-authorization
      summary: Device Activation Decision
      operationId: device_activation_decision_device_activate__device_authorization_id__decision_post
      parameters:
      - name: device_authorization_id
        in: path
        required: true
        schema:
          type: string
          title: Device Authorization Id
      responses:
        '200':
          description: Successful Response
          content:
            text/html:
              schema:
                type: string
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
components:
  schemas:
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
            - type: string
            - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
      - loc
      - msg
      - type
      title: ValidationError
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError