REST API

Base URL

https://api.aixbt.tech

Version 2 endpoints use the /v2 prefix.

Authentication

Send API keys in the x-api-key header:

curl "https://api.aixbt.tech/v2/projects?limit=5" \
  -H "x-api-key: YOUR_API_KEY"

Each endpoint in the generated API reference states whether it is public or authenticated. Scope and account-access requirements are called out where they apply. Public reference endpoints include clusters, chains, and intel categories. GET /v2/topics also exposes the current top-25 Topics feed without authentication.

Create and revoke keys in Integrations.

API key info

GET /v2/api-keys/info returns the authenticated key's id, name, type, scopes, and expiresAt. expiresAt is "never" when the key does not expire.

curl "https://api.aixbt.tech/v2/api-keys/info" \
  -H "x-api-key: YOUR_API_KEY"

Frontier Reports

GET /v2/topics/:id/report returns a published report's title, summary, Markdown body, canonical URL, publication time, and cited sources. It requires an account-backed key with the projects scope and Frontier Reports access. Generation state and raw evidence are not part of the response.

Response contracts

Most v2 data endpoints use an envelope with status and data. Paginated endpoints also return pagination; some public responses include meta with an account access link.

{
  "status": 200,
  "data": [],
  "pagination": {
    "page": 1,
    "limit": 50,
    "totalCount": 0,
    "hasMore": false
  }
}

The envelope is not universal:

GET /v2 returns service metadata: name, version, and status.
POST /v2/recipes/validate returns the validation result directly.
POST /v2/recipes/execute returns the recipe engine state directly.

Error bodies are endpoint-specific. Use the HTTP status and the documented response schema; consume code only where the endpoint advertises it. The generated API reference is the contract for parameters, request bodies, success responses, and errors.

Historical data access

Beginning August 17, 2026, self-serve API credentials can retrieve a rolling 30 days of proprietary AIXBT history. The boundary applies to intel (including activity and citations), historical project state, momentum and rank series, project neighbors, authenticated Topic history, and recipe steps that read those datasets. Current project and reference metadata remains available.

Affected responses include the active policy:

{
  "meta": {
    "history": {
      "archiveAccess": false,
      "enforced": true,
      "lookbackDays": 30,
      "earliestAvailableAt": "2026-07-18T12:00:00.000Z",
      "enforcementAt": "2026-08-17T00:00:00.000Z"
    }
  }
}

Without an explicit start date, the server returns only data in the available window. An explicit timestamp before earliestAvailableAt returns 403 with code HISTORY_WINDOW_EXCEEDED; it is not silently clamped. Credentials with the archive-history entitlement are uncapped. Contact support@aixbt.tech for archive access.

This is an access window, not a storage-retention policy. Price candles and project metrics are third-party market series with endpoint-specific windows, so the proprietary 30-day boundary does not apply to them.

Rate limits

Key-specific limits are shown in Integrations. Responses report the applicable minute and daily windows:

X-RateLimit-Limit-Minute
X-RateLimit-Remaining-Minute
X-RateLimit-Reset-Minute
X-RateLimit-Limit-Day
X-RateLimit-Remaining-Day
X-RateLimit-Reset-Day

A rate-limited request returns 429, Retry-After, and the RATE_LIMIT_EXCEEDED code.

Pagination and filtering

Paginated list endpoints use page and limit. Where multi-value filters are supported, comma-separated values use OR logic within one parameter; separate filter parameters use AND logic. Endpoint-specific exceptions are documented in the reference.

curl "https://api.aixbt.tech/v2/projects?names=eth,btc&chain=base&limit=25" \
  -H "x-api-key: YOUR_API_KEY"

Legacy endpoint sunset

GET /v2/signals and GET /v2/signal-categories sunset on 2026-07-15. Use GET /v2/intel and GET /v2/intel-categories. The deprecated /v2/grounding compatibility alias is separate and is not covered by this sunset.

On this page