Developers
Everything on this site is available as JSON. Public reads need no key and allow any origin; account routes take a personal key. Every item carries url — the original publisher — and that attribution must stay on anything you republish. Spec: openapi.json (OpenAPI 3.1).
curl
curl 'https://api.noevika.com/incidents?sector=healthcare&limit=5'
Python · noevika_client.py
from noevika_client import Noevika
nv = Noevika() # or Noevika(api_key="nvk_…")
nv.search("ivanti")
nv.organisation("Change Healthcare")TypeScript · noevika.ts
import { Noevika } from './noevika';
const nv = new Noevika();
await nv.search('ivanti');
await nv.threatActor('qilin');Your keys — sign in to see them
Send a key as X-Api-Key: nvk_… or Authorization: Bearer nvk_…. Keys raise /incidents page size to 500 and unlock the /me/… routes. Usage is counted per key per day.
AI assistants (MCP)
Remote connector: https://api.noevika.com/mcp (Streamable HTTP; add an X-Api-Key header for account tools). Local-only clients: uvx noevika-mcp (PyPI). Ten tools: search_incidents, get_incident, organisation_timeline, threat_actor, directory, cve_context, trends, watchlist, watch, vendors. Connector guide.
Reference
Loading the spec…
Terms of use
- Free, for any purpose, for the first six months at least; the record itself stays free.
- Keep the attribution: every item links to its original publisher, and so must yours.
- No leak-site content is served and none may be inferred from the record.
- Be reasonable with volume; a key gets higher limits. Contact hello@noevika.com for bulk history.