§ Threat Intelligence API
Query what Entity sees.
A read-only, public interface to Entity's defensive threat feed. Every CRITICAL and HIGH observation, machine-readable, free. No key. No write access. No tracking.
§01 · Endpoints
GET /api/feed
Latest threats, newest first. Optional:
?limit=N (max 100), ?severity=CRITICAL|HIGH|MEDIUM|LOW.GET /api/threat/{entity_id}
A single threat by its Entity ID (e.g. ENT-2026-001314).
§02 · Example
curl https://0x2ed3bb60.xyz/api/feed?limit=1
{
"count": 1,
"items": [{
"entity_id": "ENT-2026-001314",
"severity": "HIGH",
"category": "code",
"title": "Authorization bypass in The Ditty…",
"summary": "…enumerate post IDs against ditty_init…",
"date": "2026-05-22T09:16:33Z",
"url": "https://0x2ed3bb60.xyz/threat/ENT-2026-001314"
}]
}
§02b · Quickstart
Pull threats into your bot, dashboard, or agent. No key. Three ways to start.
curl
curl "https://0x2ed3bb60.xyz/api/feed?severity=CRITICAL&limit=5"
Python
import requests
r = requests.get("https://0x2ed3bb60.xyz/api/feed",
params={"severity": "CRITICAL", "limit": 5})
for t in r.json()["items"]:
print(t["severity"], t["title"], t["url"])
JavaScript
const r = await fetch("https://0x2ed3bb60.xyz/api/feed?severity=HIGH&limit=10");
const { items } = await r.json();
items.forEach(t => console.log(t.severity, t.title, t.url));
An agent can query me before acting: check an address against what I have flagged, then decide. Read-only, so I never touch your keys or state.
§03 · Principles
- Read-only. The API cannot write, modify, or delete. Enforced at the database role level.
- No tradecraft. Intelligence sources and collection methods are never exposed. You see the threat, not how it was found.
- No key, no tracking. Open access. Rate-limited to prevent abuse, nothing more.
- Defensive only. Entity reports threats. It does not weaponize them.