ModulesAI ModuleAuthentication

Authentication & Security Protocol

To ensure isolated, zero-trust ingestion across our distributed systems, Antarctica.io requires strict HTTP Header authentication on all data-streaming routes.

Our systems validate tokens via Edge gateways before the request payload is even parsed, guaranteeing extreme latency protection.

Header Injection

All telemetrics shipped to https://otm-api.antarctica.io/ are required to employ Standard Bearer Token Authentication. The payload must be transported across TLS 1.2+ encrypted channels.

POST /v1/telemetry/usage HTTP/1.1
Host: otm-api.antarctica.io
Authorization: Bearer ant_sk_XXXXXXXXXXXXXXXXXXXX
Content-Type: application/json

Essential Headers

HeaderDescriptionConstraint
AuthorizationThe static secret key generated from the unified dashboard, prefixed by Bearer.Required
Content-TypeStrictly required to notify our JSON parser. Must be application/json.Required
Idempotency-KeyA custom V4 UUID string ensuring that dropped network retries do not duplicate analytics.Optional (Highly Recommended for Production)

Authentication Lifecycle & Policies

1. Zero-Trust Access

A provisioned API key permits write-only access to your organization’s specific telemetry bucket. An attacker attempting to read configurations or past logs using this ingestion key will receive a 403 Forbidden response.

2. Handling Rejections

If the Edge network fails to cryptographically map your secret, the pipeline will immediately drop the request returning an HTTP 401 Unauthorized with the following rigid diagnostic format:

{
  "message": "Authentication failed",
  "errorType": "AuthError",
  "statusCode": 401
}

3. Immediate Revocation

In the event your key is compromised—such as an accidental commit into public version control—navigate directly to the AI Module Configurations tab on your Launch Dashboard and delete the token. All active Edge nodes instantly synchronize key revocations globally within ~1.5 seconds.

SetupRate Limiting