OmniRisk API

Overview

The OmniRisk API gives you programmatic access to real-time risk scores, market signals, wallet analysis, and on-chain data across eight blockchain networks. Every response is JSON. Every request requires an API key.

Supported chains

Pass the chain identifier as the chain query parameter or path segment.

Getting Started

{
  "chain": "eth",
  "address": "0x1f9840a85d5af5bf1d1762f925bdaddc4201f984",
  "score": 72.4,
  "label": "caution",
  "signals": [
    { "id": "low_liquidity",       "severity": "medium", "weight": 0.28 },
    { "id": "whale_concentration", "severity": "high",   "weight": 0.41 }
  ],
  "meta": {
    "name": "Uniswap",
    "symbol": "UNI",
    "price_usd": 7.31,
    "market_cap_usd": 5510000000
  },
  "cached_at": "2026-05-20T10:14:00Z"
}

// HTTP 429 — rate limit exceeded
{
  "error": {
    "code": "RATE_LIMITED",
    "message": "You have exceeded 60 requests per minute. Upgrade to Pro for higher limits.",
    "docs_url": "https://omnirisk.io/developer/docs#errors"
  }
}

Authentication

All endpoints (except GET /v1/health) require the x-api-key request header.

x-api-key: ri_live_<id>.<64-hex-chars>

Key format

Keys are prefixed ri_live_ followed by a short opaque identifier, a dot, and 64 lowercase hex characters. Store them in environment variables — never commit them to version control or expose them in client-side browser code.

Key rotation

Call POST /v1/developer/api-keys/{keyId}/rotate. The old key remains valid for 24 hours so you can update downstream services without downtime.

Security checklist

• Store keys in environment variables (OMNIRISK_API_KEY)
• Never pass the key as a URL query parameter — it appears in server logs
• Never expose keys in client-side JavaScript bundles
• Rotate keys immediately if you suspect a leak
• Use one key per service to enable granular revocation

Rate Limits

Rate-limit response headers

Every response includes these headers:

Error Reference

All errors use HTTP semantics and a consistent JSON body at error.code.

Agentic & LLM Integration

OmniRisk publishes machine-readable documentation so that AI agents, coding assistants, and autonomous tools can discover and call the API without any manual setup.

How AI agents should use the API

1. Fetch https://omnirisk.io/llms.txt for a fast summary of available capabilities.
2. For full context, load https://omnirisk.io/llms-full.txt — it contains every endpoint description, parameter, and example response.
3. Retrieve the API key from the environment variable OMNIRISK_API_KEY — never hardcode it.
4. Set x-api-key: ${OMNIRISK_API_KEY} on every request.
5. Respect X-RateLimit-Remaining and back off on 429 RATE_LIMITED using the Retry-After header value.

OpenAPI tool integration example

Pass the OpenAPI spec URL to any compatible SDK or agent framework:

# LangChain (Python)
from langchain.tools import OpenAPISpec, APIOperation
spec = OpenAPISpec.from_url("https://omnirisk.io/openapi.json")

# OpenAI function calling — generate schema from spec
# Speakeasy / Stainless — point at https://omnirisk.io/openapi.json
# Postman — import → OpenAPI 3.1 → paste URL

GitHub Repository

The public API documentation repository contains integration examples, a full README, and a changelog. Open an issue there for bugs or feature requests.

Download the full README (PDF-ready Markdown) for offline reference or to share with your team: