Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
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/amplitude:amplitude-site-content-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.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: Amplitude Public Site content API
version: '2026-10-05'
summary: Event ingestion, analytics, taxonomy, export, async DSAR jobs, and agent-readable site content APIs for Amplitude.
description: 'Amplitude is a digital analytics platform covering product analytics, experimentation, session replay, web analytics, and CDP capabilities.
This document describes the public HTTP surface most useful to programmatic clients and AI agents:
- **Ingestion** (`api2.amplitude.com`) — send events. Authenticated with a project API key in the request body.
- **Analytics, Taxonomy, Export, Cohorts** (`amplitude.com/api`) — read and manage project data. Authenticated with HTTP Basic using a project API key and secret key.
- **DSAR** (`amplitude.com/api/2/dsar`) — export a user’s data. Authenticated with HTTP Basic using the organization API key and organization secret key, not project credentials.
- **Site content** (`amplitude.com`) — Markdown and index representations of amplitude.com pages, for retrieval-augmented and agent use.
For conversational access to Amplitude data, prefer the Amplitude MCP server (`https://mcp.amplitude.com/mcp`, OAuth 2.0) over these REST APIs. For public documentation, use the read-only Docs MCP server (`https://amplitude.com/docs/api/mcp`).
The full catalog of Amplitude’s agent-callable resources is published at https://amplitude.com/.well-known/ai-catalog.json.
Endpoint coverage here is deliberately limited to documented, stable endpoints. See https://amplitude.com/docs/apis for the complete reference, including the Experiment, Attribution, Lookup Table, and User Privacy APIs.'
termsOfService: https://amplitude.com/terms
contact:
name: Amplitude Support
url: https://amplitude.com/support
license:
name: Amplitude Terms of Service
url: https://amplitude.com/terms
servers:
- url: https://amplitude.com
description: Analytics REST host (default / US data residency)
- url: https://analytics.eu.amplitude.com
description: Analytics REST host (EU data residency)
tags:
- name: Site content
description: Agent-readable representations of amplitude.com pages. Public, unauthenticated, read-only.
externalDocs:
url: https://amplitude.com/llms.txt
paths:
/{pagePath}.md:
get:
tags:
- Site content
operationId: getPageMarkdown
summary: Get any amplitude.com page as Markdown
description: Append `.md` to any amplitude.com page path to get a Markdown rendering of its main content. Public and unauthenticated.
security: []
parameters:
- name: pagePath
in: path
required: true
description: Page path without the leading slash, for example `pricing` or `blog/some-post`.
schema:
type: string
example: pricing
responses:
'200':
description: Markdown rendering of the page.
content:
text/markdown:
schema:
type: string
'400':
$ref: '#/components/responses/SiteContentBadRequest'
'404':
content:
text/markdown:
schema:
$ref: '#/components/schemas/ApiError'
description: No published page exists at that path. See https://amplitude.com/llms.txt for the available pages.
'500':
$ref: '#/components/responses/SiteContentServerError'
'508':
description: Request loop detected — the page was already being rendered as Markdown.
content:
application/json:
schema:
$ref: '#/components/schemas/SiteContentError'
/llms.txt:
get:
tags:
- Site content
operationId: getLlmsTxt
summary: Site index for LLMs
description: Categorized index of amplitude.com pages with titles and descriptions, following the llms.txt convention.
security: []
responses:
'200':
description: Plain text index.
content:
text/plain:
schema:
type: string
'500':
description: The index could not be generated.
content:
text/plain:
schema:
$ref: '#/components/schemas/ApiError'
/llms-full.txt:
get:
tags:
- Site content
operationId: getLlmsFullTxt
summary: Expanded site index for LLMs
security: []
responses:
'200':
description: Plain text index with expanded page content.
content:
text/plain:
schema:
type: string
/.well-known/ai-catalog.json:
get:
tags:
- Site content
operationId: getAiCatalog
summary: Agentic Resource Discovery catalog
description: Catalog of Amplitude’s agent-callable resources — MCP servers, skills, and APIs — per the Agentic Resource Discovery specification.
security: []
responses:
'200':
description: ARD catalog document.
content:
application/json:
schema:
type: object
/openapi.json:
get:
tags:
- Site content
operationId: getOpenApiDocument
summary: This document
security: []
responses:
'200':
description: OpenAPI description of Amplitude’s public APIs.
content:
application/json:
schema:
type: object
components:
responses:
SiteContentBadRequest:
description: No page path was supplied.
content:
application/json:
schema:
$ref: '#/components/schemas/SiteContentError'
example:
type: https://amplitude.com/errors/missing_parameter
title: Missing required parameter
status: 400
code: missing_parameter
detail: No page path was supplied. Append .md to a page path, for example /pricing.md.
hint: Request a page path, for example https://amplitude.com/pricing.md.
documentation_url: https://amplitude.com/openapi.json
SiteContentServerError:
description: The Markdown rendering could not be generated. Retryable.
content:
application/json:
schema:
$ref: '#/components/schemas/SiteContentError'
example:
type: https://amplitude.com/errors/rendering_failed
title: Markdown rendering failed
status: 500
code: rendering_failed
detail: The Markdown rendering of /pricing could not be generated.
hint: Retry the request. If it keeps failing, fetch the page as HTML without the .md suffix.
documentation_url: https://amplitude.com/openapi.json
instance: /pricing
schemas:
SiteContentError:
type: object
description: Error response from the amplitude.com site content endpoints. Fields follow RFC 9457 problem details, extended with `code` and `hint`. Served as `application/json`.
required:
- type
- title
- status
- code
- detail
- hint
- documentation_url
properties:
type:
type: string
format: uri
description: URI identifying the problem type.
title:
type: string
description: Short, human-readable summary of the problem type.
status:
type: integer
description: HTTP status code, repeated in the body.
code:
type: string
description: Stable machine-readable identifier. Branch on this rather than on `title` or `detail`, which may be reworded.
enum:
- missing_parameter
- page_not_found
- loop_detected
- rendering_failed
detail:
type: string
description: What went wrong with this specific request.
hint:
type: string
description: How to resolve it — whether to fix the request, look elsewhere, or retry.
documentation_url:
type: string
format: uri
instance:
type: string
description: Path of the request that failed, when known.
ApiError:
type:
- object
- string
description: Shared description of existing error bodies, not a new wire envelope. JSON APIs may return optional code/error fields or an errors array; other endpoints return text or Markdown. Fields are optional and clients must use the HTTP status and Content-Type. Endpoint-specific details may be present.
properties:
code:
type: integer
description: HTTP status code, repeated in the body.
error:
type: string
description: Human-readable error description.
examples:
- Invalid request path
- Missing request body
- Invalid JSON request body
- Request missing required field
- Invalid event JSON
- Invalid API key
- Invalid field values on some events
missing_field:
type: string
description: Request-level required field that is missing.
events_with_invalid_fields:
type: object
description: Maps field names to the indexes of the events that failed validation.
events_with_missing_fields:
type: object
description: Maps field names to the indexes of the events missing them.
eps_threshold:
type: integer
description: Current events-per-second threshold for the project.
throttled_devices:
type: object
description: Maps device IDs to their current events-per-second rate.
throttled_events:
type: array
items:
type: integer
description: Indexes of events that were throttled.
silenced_devices:
type: array
items:
type: string
description: Device IDs Amplitude has silenced.
silenced_events:
type: array
items:
type: integer
description: Indexes of events whose device was silenced.
exceeded_daily_quota_devices:
type: object
description: Maps device or user IDs to their daily event count, for those over quota.
errors:
type: array
items:
type: object
properties:
message:
type: string
additionalProperties: true
description: Taxonomy API error details.
additionalProperties: true
securitySchemes:
orgApiKeyAndSecretKey:
type: http
scheme: basic
description: DSAR uses HTTP Basic with the org API key and org secret key, as documented in the DSAR request examples.
apiKeyAndSecretKey:
type: http
scheme: basic
description: 'HTTP Basic authentication. Username is the project API key, password is the project secret key. Both are found in Amplitude under Settings → Projects → General. Credentials must be base64 encoded.
This scheme is project-scoped and all-or-nothing: a key pair grants every operation on its project. There is no narrower grant. When an agent needs least-privilege access, prefer the MCP server and its `mcpOAuth` scopes over these keys.'
mcpOAuth:
type: oauth2
description: 'OAuth 2.1 authorization code flow with PKCE, used by the Amplitude MCP server at `https://mcp.amplitude.com/mcp`.
Endpoints and scopes here mirror the authorization server metadata at https://mcp.amplitude.com/.well-known/oauth-authorization-server, which is authoritative. Clients may be registered dynamically (RFC 7591) at `https://mcp.amplitude.com/register`; public clients are supported.
Scopes bound the token but do not widen it — every call is additionally enforced against the permissions of the Amplitude user who approved the grant. Request the narrowest scope that covers the task.
For EU data residency, substitute `https://mcp.eu.amplitude.com`.'
flows:
authorizationCode:
authorizationUrl: https://mcp.amplitude.com/authorize
tokenUrl: https://mcp.amplitude.com/token
refreshUrl: https://mcp.amplitude.com/token
scopes:
mcp:read: Read charts, dashboards, cohorts, experiments, feature flags, events, properties, and session replays.
mcp:write: Create and modify dashboards, notebooks, experiments, cohorts, and metrics.
offline_access: Issue a refresh token so the agent can act after the user closes the browser. Omit for one-shot interactive tasks.
externalDocs:
description: Amplitude API reference
url: https://amplitude.com/docs/apis
x-api-versioning:
scheme: per-api-path
documentVersionScheme: date
description: API families use independent path namespaces (for example /2/httpapi, /api/2/dsar and /api/5/cohorts). Batch and site-content paths are unversioned. The namespace number is not a shared release number or a semantic-version guarantee.
deprecationPolicy:
status: not-verified
description: No company-wide REST retirement notice period or sunset dates are asserted by this document. SDK maintenance policy does not establish REST API lifecycle policy.