Human Signal Index
Documentation

API

Human Signal Index public API reference: live read-only endpoints for published and aggregate intelligence, rate limits, response format, and the planned authenticated API.

Human Signal Index exposes a small set of read-only, public-safe API endpoints today. They require no authentication, are rate-limited, and return only published or aggregate data — never internal notes, identities, or unpublished content. A fuller authenticated API — with API keys, webhooks, and official SDKs — is planned; those parts are marked Coming Soon below.

Available now — public read endpoints

These endpoints are live. They are read-only (GET), require no authentication, are rate-limited, and return only published or aggregate, public-safe data.

  • GET /api/public/intelligence — Platform metrics, the latest published signals, and recent public activity. Returns { ok, metrics, latestSignals, activityFeed }.
  • GET /api/public/trust — Trust overview metrics, the review pipeline, the public correction log, and platform health. Returns { ok, metrics, pipeline, corrections, health }.
  • GET /api/public/transparency — Aggregate trust, forecast accuracy and calibration, narrative status counts, and source health. Returns { ok, trust, forecasts, narratives, sources }.
  • GET /api/public/marketplace — The published marketplace catalog; supports ?slug= for one product and ?q= to search. Returns { ok, featured, trending, newest, categories, totalProducts }.

Response format

Every endpoint returns JSON shaped as { "ok": true, ... }. Successful responses are cacheable (Cache-Control with stale-while-revalidate). On an internal error the endpoints degrade to a valid empty body instead of failing, so integrations stay resilient.

Rate limits

Public endpoints currently allow 60 requests per minute per client. Remaining quota is reported in the x-ratelimit-limit and x-ratelimit-remaining response headers; exceeding the limit returns HTTP 429 with a retry-after header. Higher, per-API-key limits are planned.

Authentication

The public read endpoints above require no authentication. Authenticated access for private data and higher rate limits is planned and will use issued API keys. Protected platform endpoints are not part of the public API.

API keys

Coming Soon

Self-service API key issuance and management are planned.

Authenticated & write endpoints

Coming Soon

Programmatic access to private workspaces and write operations is planned.

Webhooks

Coming Soon

Outbound webhooks are planned.

SDKs

Coming Soon

Official client SDKs are planned. No SDK package is published yet.

Examples

Coming Soon

Worked examples will be added alongside the authenticated API.