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/axonflow:axonflow-otlp-ingest-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
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: Axonflow OTLP Ingest API
version: 11.1.0
contact:
name: AxonFlow Support
url: https://getaxonflow.com/support
license:
name: Business Source License 1.1
url: https://github.com/getaxonflow/axonflow/blob/main/LICENSE
description: 'Operations tagged OTLP Ingest across 2 of this provider''s published API definitions: axonflow-agent-api.yaml, axonflow-agent-openapi.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://agent.getaxonflow.com
description: Production (SaaS)
- url: https://axonflow.example.com
description: Self-hosted deployment (agent single entry point, ADR-024)
- url: http://localhost:8080
description: Local Development
tags:
- name: OTLP Ingest
description: 'OpenTelemetry OTLP/HTTP ingest for Claude Code (cowork) telemetry
(#2832). **Enterprise only** — community builds mount the routes but
return 501. Org/tenant identity always comes from the authenticated
license, never from OTLP resource attributes.'
paths:
/v1/metrics:
post:
tags:
- OTLP Ingest
summary: OTLP metrics ingest
description: 'OTLP/HTTP `ExportMetricsServiceRequest` ingest for Claude Code
telemetry. Content types: `application/x-protobuf` (default when
the header is empty), `application/protobuf`, or `application/json`;
anything else returns **415**. Success returns 200 with an OTLP
`ExportMetricsServiceResponse` in the request''s content type.
**Enterprise only** — community builds return **501** with
`{"error": {"code", "message"}}`. Org/tenant comes from the
authenticated license (Basic auth), never from OTLP resource
attributes.'
operationId: otlpIngestMetrics
parameters:
- $ref: '#/components/parameters/LicenseKey'
requestBody:
required: true
content:
application/x-protobuf:
schema:
type: string
format: binary
application/json:
schema:
type: object
additionalProperties: true
responses:
'200':
description: OTLP export response (matching request content type)
'400':
description: Malformed OTLP payload
'401':
$ref: '#/components/responses/Unauthorized'
'415':
description: Unsupported Content-Type
'501':
description: 'Cowork OTLP ingest is not in this deployment''s plane set: the Community
build, and the Enterprise build in a core-only deployment mode
(community, evaluation, community-saas). Both answer the same body.
'
content:
application/json:
schema:
$ref: '#/components/schemas/JSONError'
servers:
- url: https://agent.getaxonflow.com
description: Production (SaaS)
- url: https://axonflow.example.com
description: Self-hosted deployment (agent single entry point, ADR-024)
- url: http://localhost:8080
description: Local Development
/v1/logs:
post:
tags:
- OTLP Ingest
summary: OTLP logs ingest
description: 'OTLP/HTTP `ExportLogsServiceRequest` ingest for Claude Code
telemetry. Same content-type, auth, edition, and error semantics as
`POST /v1/metrics`.'
operationId: otlpIngestLogs
parameters:
- $ref: '#/components/parameters/LicenseKey'
requestBody:
required: true
content:
application/x-protobuf:
schema:
type: string
format: binary
application/json:
schema:
type: object
additionalProperties: true
responses:
'200':
description: OTLP export response (matching request content type)
'400':
description: Malformed OTLP payload
'401':
$ref: '#/components/responses/Unauthorized'
'415':
description: Unsupported Content-Type
'501':
description: 'Cowork OTLP ingest is not in this deployment''s plane set: the Community
build, and the Enterprise build in a core-only deployment mode
(community, evaluation, community-saas). Both answer the same body.
'
content:
application/json:
schema:
$ref: '#/components/schemas/JSONError'
servers:
- url: https://agent.getaxonflow.com
description: Production (SaaS)
- url: https://axonflow.example.com
description: Self-hosted deployment (agent single entry point, ADR-024)
- url: http://localhost:8080
description: Local Development
components:
schemas:
JSONError:
type: object
description: 'Middleware-written error envelope (auth middleware 401s, static
policy API errors). Source of truth:
`platform/agent/static_policy_api_handlers.go` (writeJSONError).
One exception on the system-policy routes: the v11 legacy policy
freeze answers with the same two keys and a STRING code - see the
`LegacyPolicyWriteFrozen` response.
'
properties:
error:
type: object
properties:
code:
type: integer
description: HTTP status code
message:
type: string
ErrorResponse:
type: object
description: 'Handler-written error envelope. Note the agent has a second error
envelope for middleware-written errors (see JSONError) — clients
should tolerate both shapes on 4xx/5xx.
'
properties:
success:
type: boolean
example: false
error:
type: string
description: Error message
parameters:
LicenseKey:
name: Authorization
in: header
required: true
description: 'OAuth2-style Basic authentication header.
Format: `Basic base64(clientId:clientSecret)`
- `clientId`: Your organization identifier (required)
- `clientSecret`: Authentication credential (optional for community mode)
Not required when `DEPLOYMENT_MODE=community`.
'
schema:
type: string
example: Basic bXktb3JnOkFYT04tVjIteHh4
responses:
Unauthorized:
description: 'Missing or invalid authentication. Handler-written 401s use the
`{success, error}` envelope; 401s written by the auth middleware
use the `{"error": {"code", "message"}}` envelope (JSONError).
'
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
example:
success: false
error: 'Authentication required: provide Authorization header with Basic auth (clientId:clientSecret)'
securitySchemes:
BasicAuth:
type: http
scheme: basic
description: "OAuth2-style Basic authentication using `clientId:clientSecret` credentials.\n\n**Header format:** `Authorization: Basic base64(clientId:clientSecret)`\n\n- `clientId` (required): Your organization/client identifier\n- `clientSecret` (optional): Authentication credential. Optional for community/self-hosted mode.\n\n**Example:**\n```bash\n# With clientSecret (enterprise)\ncurl -H \"Authorization: Basic $(echo -n 'my-org:AXON-V2-xxx' | base64)\" ...\n\n# Without clientSecret (community mode)\ncurl -H \"Authorization: Basic $(echo -n 'my-org:' | base64)\" ...\n```\n\n## Per-user identity behind a shared credential\n\nThis credential authenticates an ORGANIZATION or client, not a person.\nBehind one such credential can sit many human principals, each\noptionally forwarding a **per-user token** that proves who they are.\nWhere that token is read depends on the envelope: the `user_token`\nfield of the request body on `POST /api/v1/decide` and the four MCP\nREST routes, and the `X-User-Token` header on the MCP-server JSON-RPC\nplane. The two spellings are deliberately not interchangeable.\n\n**A presented per-user token that fails to validate is a refused\naccess attempt, not a legacy caller** (`401`, audited\n`user_token_rejected`). It is never downgraded to a shared service\nidentity, so revocation, expiry, algorithm pinning and signature\nchecks take effect on every plane that reads one.\n\n**Whether presenting a token is REQUIRED is a per-organization\nposture, `require_user_token`, and it is off by default (#3476).**\nWith it off, an enterprise caller that presents no token at all is\nserved under a synthetic org-scoped service identity\n(`<client-id>@axonflow.local`, role `service`), which is the correct\nanswer for an infrastructure gateway acting as a Policy Enforcement\nPoint with no end-user token to forward. With it on, that caller is\nrefused at AUTHENTICATION, before any policy is evaluated (`401`,\naudited `user_token_required`).\n\nThe posture exists because a policy that names a PERSON - a\nprincipal-scoped constraint or permission in the organization's typed\ndocument (PRD v11 §1.6) - is only meaningful if a caller cannot CHOOSE\nto arrive without an identity: with the posture off such a policy\nstill applies to everyone who presents a token, but a caller can\ndecline to present one and be decided as the credential\n(`subject_type=Client`). Governance segments (ADR-060) decide on no\nagent route since v11.0.0 (#4253). Two levers set it, and an explicit\nper-organization row wins over the deployment-wide default in EITHER\ndirection:\n\n- `organizations.require_user_token`, per organization, default\n `false`.\n- `AXONFLOW_REQUIRE_USER_TOKEN`, deployment-wide, default `false`.\n\nA posture change takes up to one cache window to become live\n(`AXONFLOW_REQUIRE_USER_TOKEN_TTL_SECONDS`, default 60 seconds,\nclamped to `[5, 600]`). A posture that cannot be READ resolves to\nREQUIRED rather than not-required, so a database outage cannot\nquietly switch the control off; a genuinely absent organization row\nis not a read failure and falls through to the deployment default.\n\n`POST /v1/chat/completions` is outside this guarantee: it mirrors\nOpenAI's wire shape and carries no per-user token field at all, so it\nkeeps the synthetic-identity fallback regardless of the posture.\nCommunity and community-SaaS deployments never reach any of the above.\n"
InternalServiceID:
type: apiKey
in: header
name: X-Internal-Service-ID
description: 'Internal-service (operator lane) credential — **part one of two**.
Must be sent together with `X-Internal-Service-Token`; either header
alone is not a credential.
This is the HMAC identity the Orchestrator and the Enterprise
customer-portal use to call agent endpoints without holding a
customer license. `apiAuthMiddleware` lifts both headers (plus an
optional `X-Tenant-ID` scope) into `AuthHints`
(`internalServiceHints` in `platform/agent/auth.go`) and
`Authenticate()` validates them before any mode-specific auth
(`platform/agent/authenticator.go:120-155`).
Value: the service id, `orchestrator-internal`.
⚠️ An invalid or expired token is **not** an error by itself — it
falls through to the deployment''s normal auth
(`platform/agent/authenticator.go:153-154`). Send the internal-service
headers on their own: paired with an `Authorization: Basic` header, a
stale token silently yields a *tenant*-scoped answer that looks like a
successful operator call.
'
InternalServiceToken:
type: apiKey
in: header
name: X-Internal-Service-Token
description: 'Internal-service (operator lane) credential — **part two of two**.
Must be sent together with `X-Internal-Service-ID`.
Format: `AXON-INTERNAL-{unix_ts}-{sig}`, where `sig` is the first 16
hex characters of HMAC-SHA256 over `orchestrator-internal:{unix_ts}`
keyed with `AXONFLOW_INTERNAL_SERVICE_SECRET`. Validated by
`platform/shared/serviceauth` within a 5-minute clock-skew window, so
it must be re-minted per session. See
`technical-docs/runbooks/RUNBOOK_CONNECTOR_CONFIGURATION.md` for the
exact minting snippet.
'
x-refined-from:
- axonflow-agent-api.yaml
- axonflow-agent-openapi.yml