sigiro hosted telemetry API

REST detected 2026-10-01

Details

URL: https://sigiro.com
Spec: https://sigiro.com/openapi.json
Docs: https://sigiro.com/docs/reference

Authentication

OAuth 2.0 + OAuth 2.0 Authorization: Bearer <credential> discovered

OAuth 2.0 oauth2

OAuth 2.0 — self-onboarding

Point your MCP client at the server URL and approve access in the browser. The server accepts a Client ID Metadata Document (CIMD), so the client authenticates with its own hosted URL as the client_id — nothing to register.

Sigiro Agent Auth delegated JWT jwt discovered Get key ↗

Authorization: Bearer <credential>

When software needs its own delegated identity for hosted Sigiro, integrate the official Agent Auth guide. First sign in to Sigiro (sigiro signup or sigiro auth login), then let the @auth/agent SDK discover Sigiro at https://sigiro.com/.well-known/agent-configuration, dynamically register the host, and start delegated approval with connectAgent. A human approves the device-style verification flow once in the browser, after which the SDK stores the host and agent Ed25519 keys and can mint short-lived JWT bearer tokens with signJwt for audience https://sigiro.com and requested capabilities such as telemetry:ingest.

Better Auth OAuth access token oauth2 declared

Authorization: Bearer <credential>

Use the Better Auth/OAuth API to sign in and obtain an OAuth access token for the hosted service. Organizations are the tenants. Send it as Authorization: Bearer <oauth-access-token> for OTLP and API requests. Self-hosted Open mode needs no credential.