Explorer API

Read tokenomics changes and run a monitoring watchlist with a scoped exchange key.

The Explorer API exposes the data behind Compliance Explorer to exchange integrators. With a scoped key you can stream tokenomics change revisions and run your own Disclosure Monitoring watchlist from code — watching assets, reading detected changes and pulling the notification inbox.

Base URL

https://explorer-api.bluprynt.com

Key concepts

Term	Meaning
Exchange key	A bx_live_… bearer token Bluprynt issues per integrator. Scoped, rate-limited, revocable.
Scope	A permission on the key: tokenomics:read, monitoring:read, watchlist:write.
Watchlist	Your set of watched registry assets. Monitoring and notifications cover only what you watch.
Change	A detected difference on a watched asset — a disclosure field edit, register move, sanctions listing, and so on.
Tokenomics revision	A verified change to an asset’s tokenomics — unlocks, emissions, allocations, control — with issuer and on-chain evidence.

Endpoints

Eight routes are key-callable. Everything else — the full registry read surface — serves the public explorer frontend, not keys.

Endpoint	Scope	Returns
GET /tokenomics/changes	tokenomics:read	Tokenomics revisions across your watchlist.
GET /assets/{id}/tokenomics/changes	tokenomics:read	Tokenomics revisions of one asset.
GET /me/watchlist	monitoring:read	Your watchlist with limit and usage.
POST /me/watchlist	watchlist:write	Watch a registry asset.
PATCH /me/watchlist/{id}	watchlist:write	Pause/resume monitoring, edit the note.
DELETE /me/watchlist/{id}	watchlist:write	Stop watching.
GET /me/monitoring/changes	monitoring:read	Detected changes on your watchlist.
GET /me/notifications	monitoring:read	Your notification inbox.

The three watchlist:write routes change your watchlist. Everything else is read-only.

Authenticate

Bluprynt issues exchange keys by arrangement — ask [e-mail]. Send the key as a bearer token:

curl -s "https://explorer-api.bluprynt.com/me/watchlist" \
  -H "Authorization: Bearer bx_live_your_key_here"

A route answers only when your key holds its scope. See Authentication and scopes.

Check the service

Two routes need no key:

curl -s https://explorer-api.bluprynt.com/health
# {"status":"ok","info":{},"error":{},"details":{}}

curl -s https://explorer-api.bluprynt.com/openapi.json | jq .info.title
# "Compliance Explorer Registry API"

Response envelope

Key-callable routes wrap their payload:

{
  "data": { "…": "the route payload" },
  "meta": { "request_id": "req_…", "fetched_at": "2026-10-07T20:00:00.000Z" },
  "errors": []
}

Errors instead carry a stable code — see Errors.

In this section

Authentication and scopes

Key format, scopes, and the route-to-scope table.

Pagination

Backlog pages and feed cursors.

Tokenomics changes

Revision classes, filters and the field reference.

Watchlist and monitoring

Watch → change → notification, with a worked example.

Polling guidance

There are no webhooks — poll efficiently with cursors.

Errors

The full code table.

Rate limits

Per-key budgets and the 429 response.

Looking for the public KYI record and badges instead? That’s the Public API — a separate service with raw-key auth.