Company Quick Start

For now, the business-ready automation endpoint is the Threat check API. Use it to check Ethereum addresses before users sign transactions, list assets, or interact with contracts.

What is live today

Threat check API: live for automation.
RT monitoring API: not publicly available yet.
Scoring API: not publicly available yet.

Threat check API

GET /api/threat-check?address=0x…

POST /api/threat-check with JSON body { "address": "0x…" }

Supports Ethereum addresses; invalid input returns 400.

{
  "address": "0x0000000000000000000000000000000000000000",
  "outcome": "safe",
  "source": "spotblock_db"
}

Full API reference Explorer dataset source

Integration confidence signals

Deterministic response contract: output is always structured as address, outcome, source.
Strict input validation: malformed addresses fail fast with 400, reducing ambiguous downstream handling.
Shared intelligence source: API outcomes are backed by the same listings dataset as the public Explorer (source=spotblock_db).
Near-real-time usage: GET may include short private caching; design client logic for periodic re-checks on critical actions.
Chain scope: current production scope is Ethereum addresses.

Review the live component breakdown and trust snapshot in Explorer Capabilities.

SLA status

A public enterprise SLA is not published yet. The current endpoint is production-available and actively maintained, and teams that require contractual uptime/response commitments should contact SpotBlock before rollout.

Simple integration flow

User enters or selects an address in your app.
Your backend calls /api/threat-check.
Block, warn, or allow based on the returned outcome.