Atune API documentation
Atune API Authentication
Atune's documented public discovery endpoints are deliberately read-only and require no authentication. GET /api/v1/capabilities and GET /api/v1/platforms may be called directly by agents, scripts, and the official Atune CLI. The OpenAPI document describes this public surface and does not declare an authentication scheme.
Public endpoints
Clients should send Accept: application/json and identify themselves with an appropriate User-Agent. Public endpoints are rate limited and may return HTTP 429. They never expose customer monitor configurations, results, account records, subscription details, or private prompts.
Account-specific access
Atune web sessions are intended for the first-party application and are not a public developer authentication mechanism. Do not copy browser tokens or cookies into agents, command-line tools, or third-party integrations. API keys and OAuth are not yet generally available; any future authenticated API will document scopes, rotation, revocation, rate limits, and retention before launch.
Integration support
Contact support@atune.cc to discuss commercial or account-specific integration requirements. Include the intended use case, required data, expected request volume, and security constraints, but do not include credentials or sensitive customer data in the initial email.