LLM Pulse OAuth 2.1 API
OAuth 2.1 authorization for MCP clients: discovery metadata, dynamic client registration, authorization, token exchange and JWKS.
OAuth 2.1 authorization for MCP clients: discovery metadata, dynamic client registration, authorization, token exchange and JWKS.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
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.curl "https://apis.io/api/v1/apis/llmpulse-ai:llmpulse-ai-oauth-2-1-api"
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.
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. By signing up you are subscribing to the APIs.io and API Evangelist newsletters — you can unsubscribe from any issue. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: LLM Pulse OAuth 2.1 API
description: 'REST API for the LLM Pulse AI visibility platform. Track brand mentions, citations, sentiment, and Share of Voice across AI-generated answers (ChatGPT, Perplexity, Gemini, Google AI Overviews, Google AI Mode, and optional add-on models). Includes the MCP (Model Context Protocol) endpoint for AI clients. MCP is available on every plan and during eligible trials via OAuth 2.1, with Bearer-token API keys also accepted for headless integrations on the Scale plan or above. Full machine-readable reference at https://llmpulse.ai/api-docs/llms-full.txt. An API key can be limited to one or several projects when it is created, and the set never changes. Such a key sees only those projects: any other project id, domain or name answers ERR_PROJECT_NOT_FOUND exactly like a project that does not exist, listings return only those projects'' rows, and operations on the whole account (creating or deleting a project, the project draft wizard) answer ERR_KEY_PROJECT_SCOPED. Operations carry vendor extensions: x-plan is the plan or entitlement the endpoint requires beyond an API key (growth, scale or reputation_access), x-write marks endpoints that need a read and write key, x-mcp-tool names the MCP tool that returns the same data, x-mcp-plan gives that tool''s plan where it differs, and x-rest-only explains an endpoint with no MCP tool. Parameters are read strictly, on REST and MCP alike: a value outside a documented enum, a boolean other than true, false, 1 or 0, an id or count that is not a plain positive number (12abc, 1.0 or 0), an id of a record the project does not have, or a from later than to answers 422 ERR_INVALID_PARAM naming the parameter, never an ignored filter. A listed value, in a query or a request body, matches in any letter case and is read in its documented spelling (granularity=Week reads as week, aggregation_type=BYPAGE as byPage, event_type=Mention.Created as mention.created). page and per_page keep their own rule: a value that is not a number reads as absent and an out-of-range one is clamped.'
version: 1.97.0
contact:
name: LLM Pulse Support
url: https://llmpulse.ai
email: info@llmpulse.ai
license:
name: Proprietary
url: https://llmpulse.ai/terms
servers:
- url: https://api.llmpulse.ai/api/v1
description: Production API
security:
- BearerAuth: []
tags:
- name: OAuth 2.1
description: 'OAuth 2.1 authorization for MCP clients: discovery metadata, dynamic client registration, authorization, token exchange and JWKS.'
paths:
/oauth/authorize:
get:
tags:
- OAuth 2.1
summary: OAuth 2.1 authorization endpoint
description: Renders a consent screen and on approval redirects back to the client with an authorization code. PKCE-S256 is required.
operationId: oauthAuthorize
x-rest-only: OAuth 2.1 protocol endpoint MCP clients use to obtain a token.
parameters:
- name: response_type
in: query
required: true
schema:
type: string
enum:
- code
- name: client_id
in: query
required: true
schema:
type: string
- name: redirect_uri
in: query
required: true
schema:
type: string
format: uri
- name: code_challenge
in: query
required: true
schema:
type: string
- name: code_challenge_method
in: query
required: true
schema:
type: string
enum:
- S256
- name: scope
in: query
schema:
type: string
description: 'Space-separated scopes: mcp:read mcp:write'
- name: state
in: query
schema:
type: string
- name: resource
in: query
schema:
type: string
responses:
'302':
description: Redirect to client with code or error
'400':
description: Invalid request
/oauth/token:
post:
tags:
- OAuth 2.1
summary: OAuth 2.1 token endpoint
description: Exchanges an authorization code for an access + refresh token, or refreshes an access token. JWT access tokens and the reusable refresh token share a fixed one-year authorization deadline. Refresh responses return the same refresh token.
operationId: oauthToken
x-rest-only: OAuth 2.1 protocol endpoint MCP clients use to obtain a token.
requestBody:
required: true
content:
application/x-www-form-urlencoded:
schema:
type: object
properties:
grant_type:
type: string
enum:
- authorization_code
- refresh_token
code:
type: string
code_verifier:
type: string
client_id:
type: string
client_secret:
type: string
redirect_uri:
type: string
refresh_token:
type: string
scope:
type: string
description: Optional. On refresh, must be a subset of the original grant.
required:
- grant_type
- client_id
responses:
'200':
description: Token response
content:
application/json:
schema:
type: object
properties:
access_token:
type: string
token_type:
type: string
expires_in:
type: integer
refresh_token:
type: string
scope:
type: string
'400':
description: Invalid grant or request
/oauth/register:
post:
tags:
- OAuth 2.1
summary: Dynamic Client Registration (RFC 7591)
description: Registers a new OAuth client. Rate-limited to 5/hour per IP. Only RFC 7591 fields are persisted. Redirect URIs must be https (any host) or http to loopback only.
operationId: oauthRegister
x-rest-only: OAuth 2.1 protocol endpoint MCP clients use to obtain a token.
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- redirect_uris
properties:
redirect_uris:
type: array
maxItems: 10
items:
type: string
format: uri
client_name:
type: string
maxLength: 200
grant_types:
type: array
items:
type: string
enum:
- authorization_code
- refresh_token
token_endpoint_auth_method:
type: string
enum:
- none
- client_secret_post
scope:
type: string
responses:
'201':
description: Client registered
content:
application/json:
schema:
type: object
properties:
client_id:
type: string
client_id_issued_at:
type: integer
client_name:
type: string
redirect_uris:
type: array
items:
type: string
grant_types:
type: array
items:
type: string
token_endpoint_auth_method:
type: string
scope:
type: string
'400':
description: Invalid client metadata
/oauth/jwks.json:
get:
tags:
- OAuth 2.1
summary: JWKS endpoint
operationId: oauthJwks
x-rest-only: OAuth 2.1 protocol endpoint MCP clients use to obtain a token.
description: Returns the JSON Web Key Set used to verify signatures on issued access tokens.
responses:
'200':
description: JWKS
content:
application/json:
schema:
type: object
properties:
keys:
type: array
items:
type: object
/.well-known/oauth-authorization-server:
get:
tags:
- OAuth 2.1
summary: OAuth 2.1 server discovery (RFC 8414)
operationId: oauthDiscoveryAuthServer
x-rest-only: OAuth 2.1 protocol endpoint MCP clients use to obtain a token.
responses:
'200':
description: Authorization server metadata
content:
application/json:
schema:
type: object
/.well-known/oauth-protected-resource:
get:
tags:
- OAuth 2.1
summary: OAuth protected resource discovery (RFC 9728)
operationId: oauthDiscoveryProtectedResource
x-rest-only: OAuth 2.1 protocol endpoint MCP clients use to obtain a token.
responses:
'200':
description: Protected resource metadata
content:
application/json:
schema:
type: object
components:
securitySchemes:
BearerAuth:
type: http
scheme: bearer
description: API key authentication. Keys are managed at https://llmpulse.ai/app/api_keys (Scale plan or above). Used for the REST API and as a headless option for /mcp. A key can be limited to one or several projects when it is created; the set cannot be changed later.
OAuth2:
type: oauth2
description: OAuth 2.1 with PKCE-S256 and Dynamic Client Registration. Accepted on /mcp only, available on every plan and during eligible trials. Discovery metadata at /.well-known/oauth-authorization-server.
flows:
authorizationCode:
authorizationUrl: https://api.llmpulse.ai/oauth/authorize
tokenUrl: https://api.llmpulse.ai/oauth/token
scopes:
mcp:read: Read data via MCP tools
mcp:write: Create resources via MCP write tools