Documentation
Connect Threat Landscape intelligence to your analysts, tools and AI agents. Both the Intelligence API and IOC API are available over REST, TAXII 2.1 and MCP.
REST API
Context and indicators
Authentication, the Intelligence API, the IOC API, filtering and pagination.
Read REST docs →TAXII 2.1
TIP and SIEM sync
Discovery, collections, incremental polling and STIX object filtering.
Read TAXII docs →MCP Server
AI agent access
Connect Claude, Codex or your own agent to live threat intelligence.
Read MCP docs →OpenCTI
Official connector
Stand up OpenCTI with the official Threat Landscape connector.
Read OpenCTI guide →Quickstart
API access starts with Team. Once you have a key, query the Intelligence API directly:
curl 'https://api.threatlandscape.io/rest/v1/stix_bundles?select=bundle_id,title,threat_actors,malware_names&order=api_created_at.desc&limit=1' \
-H "apikey: YOUR_THREATLANDSCAPE_API_KEY"The same key works for the IOC API, TAXII and MCP. Keep it server-side. Do not put it in browser code, public repositories or logs.
Choose an interface
| Interface | Best for | Start |
|---|---|---|
| REST | Custom integrations, enrichment, dashboards and scripts. | REST API docs |
| TAXII 2.1 | TIPs, SIEMs and tools that already speak TAXII. | TAXII docs |
| MCP | Claude, Codex and agent workflows that need threat context. | MCP docs |
| OpenCTI connector | Syncing intelligence into an OpenCTI knowledge graph. | OpenCTI guide |
Related guides
- OpenCTI connectors — how the connector works.
- OpenCTI TAXII feeds — the no-connector path.
- Threat intelligence feed integration — planning the pipeline.
- SIEM and SOAR integration — ingestion patterns.