CLAUDEWARDOCS
DEVELOPERS

MAKE YOUR FIRST REQUEST

AUTH · TIERS · RESPONSES · WEBHOOKS

Maintained by ClaudeWar LLC · Last reviewed 2026-07-22

BEFORE YOU START

API ACCESS IS A SEPARATE PRODUCT

Browser membership and REST API access are separate products. AI Operative does not include an API key.

Request a Developer, Professional, or Enterprise key from claudewar.info/access. Your key determines route access and request volume.

QUICKSTART

GET GEOMAGNETIC CONDITIONS

Method and path: GET https://claudewar.info/api/intel/geomagnetic

Minimum tier: Developer

curl -sS "https://claudewar.info/api/intel/geomagnetic" \
  -H "X-API-Key: $CLAUDEWAR_API_KEY"

A successful response contains the current cached layer payload and source metadata. Field availability can change with the upstream source; validate optional fields instead of assuming every observation is populated.

AUTHENTICATION

USE THE REQUEST HEADER

Send REST API keys in the X-API-Key request header.

X-API-Key: your-key-here

Legacy query-string keys may remain accepted for compatibility, but they can leak through logs, browser history, and copied URLs. New integrations should use the header.

PLANS

TIERS AND RATE LIMITS

TierPriceRequest limitScope
Developer$200/month10,000 requests per rolling 24 hoursPublic-source REST feeds
Professional$500/month50,000 requests per rolling 24 hoursAggregated intelligence feeds
EnterpriseCustomNegotiated volume and SLAProprietary feeds, webhooks, and SLA

Routes enforce their own minimum tier. A valid key can still receive 403 when its tier does not include the requested feed.

CONTRACTS

RESPONSE FORMATS

Most feeds return JSON or GeoJSON. Image and composite-image routes return media content. Check the endpoint’s documented Content-Type and do not force every response through a JSON parser.

Timestamps use UTC unless a route states otherwise. Geographic coordinates use decimal degrees. Consumers should tolerate additional fields and optional source values.

FAILURES

HANDLE STATUS CODES

StatusMeaningClient action
400Invalid parameter or request shapeCorrect the request before retrying.
401Missing or invalid keyCheck the header and key status.
403Tier or policy does not permit the routeUse an included route or request the required tier.
429Rate limit exceededBack off and retry after the applicable window.
500/503Service or upstream source unavailableRetry with bounded exponential backoff.
ENTERPRISE

WEBHOOK DELIVERY

Enterprise webhooks use event subscriptions and signed payloads. Verify the HMAC signature before processing, return a successful response quickly, deduplicate by event identity, and make handlers idempotent. Exact subscription and secret-rotation procedures are provided during Enterprise onboarding.

SECURITY

PROTECT AND ROTATE KEYS

  • Store keys in a server-side secret manager or environment variable.
  • Never embed a paid key in public browser JavaScript, mobile bundles, screenshots, or support tickets.
  • Use separate keys for separate environments when provided.
  • Contact support immediately if a key is exposed.
REFERENCE

ENDPOINT INVENTORY

The maintained tier and feed overview remains at API and Tiers. Machine-readable coverage is available at claudewar.info/openapi.json; verify that a route appears there before generating a client from it.