Developers & Integrations · REST API and MCP Connector

Integrate svEye Intelligence Into Your Workflow

There are two ways to bring svEye's global event intelligence into your own environment: call the Public API directly from your systems, or connect Claude through the svEye MCP Connector — no code required.

Explore the svEye Public APISet up the MCP Connector
✦
Ask Claude about this page
→
Copies a ready-made prompt · opens a new Claude chat
TWO WAYS TO INTEGRATE · ONE INTELLIGENCE LAYER
12 LANGUAGES · HOURLY REFRESH
svEye Public API

REST calls from your own code and systems.

POST /v1/search/events
{ "entity_ids": ["foxconn"], "impact_type": "business_risk" }

Returns raw events, summaries, entities and taxonomies as structured data.

svEye MCP Connector

Natural-language questions in Claude — no code.

What high-severity risk events involve Foxconn in the last 30 days?

Returns investigations, briefings and monitoring answers — every claim linked to its source article.

reuters.com · 22 Jul
nikkei.com · 18 Jul
+ 9 sources
SAME DATA · SAME SOURCES · SAME HOURLY REFRESH
Prototype in Claude → productionize with the API

Illustrative request and answer — the connector and the API read the same continuously crawled OSINT corpus, refreshed hourly.

For developers, data teams and advanced enterprise users

svEye Public API

The svEye Public API provides programmatic access to the same intelligence data available in the svEye application — delivered in a format designed for developers, data teams, and advanced enterprise users.

Integrate global events, semantic summaries, entities, and taxonomies directly into your own systems, workflows, and analytics environments.

Events

Discrete, timestamped occurrences classified against a three-level taxonomy.

Summaries

Narrative synthesis across a cluster of articles, with sentiment and co-mentioned entities.

Entities & taxonomies

Companies, legal entities, locations, commodities and industries with their event schema.

Explore the API documentation →
api.semantic-visions.com/docs
EXAMPLE REQUEST
GET /v1/summaries
curl -X GET \ "https://api.semantic-visions.com/v1/summaries" \ -H "Authorization: Bearer $SV_TOKEN" \ -G --data-urlencode "entity_ids=tsmc" \ --data-urlencode "from=2026-01-01"
RESPONSE
{ "summaries": [ { "entity": "TSMC", "sentiment": "negative", "impact_type": "business_risk", "sources": 27 } ] }
12 LANGUAGES · HOURLY REFRESH
Full reference →
For analysts and teams working with AI assistants — no code required

svEye MCP Connector for Claude

Connect Claude directly to svEye's OSINT intelligence. Ask questions in plain language and get risk and opportunity events, narrative summaries, and multi-tier supply chain maps — every answer backed by verifiable source articles.

DIB-style investigation

Investigate any company or supplier

Sanctions exposure, legal trouble, financial distress, ESG violations, cyber incidents, supply chain disruption.

Entity briefing

Summarize recent developments for an entity

“Summarize key supply disruption events for TSMC in Q1 2026.”

Continuous monitoring

Monitor your watchlist

“What new high-severity events have come in since yesterday?”

Network exposure

Map exposure through supply chains

OSINT-derived supplier relationships, up to three tiers deep.

How it works
STEP 01

Create a service account

In your svEye account, open the API tab and generate a dedicated credential pair.

STEP 02

Add the svEye connector in Claude

Add svEye as a connector and authenticate with those credentials.

STEP 03

Ask

Claude queries svEye live and cites its sources in every answer.

Decision helper

Which one is for you?

At a glance
svEye Public API
svEye MCP Connector
Best for
Data teams and developers building custom pipelines, dashboards, and internal tools
Analysts, risk and procurement teams working in Claude
How you use it
REST calls from your own code and systems
Natural-language questions — no code
Typical output
Raw events, summaries, entities, taxonomies as structured data
Investigations, briefings, and monitoring answers with cited sources
Setup
API credentials + engineering integration
Service account + one-time connector setup (~5 minutes)

Both run on the same intelligence layer — continuously crawled open-source content in 12 languages, refreshed hourly. Use them together: prototype an investigation in Claude, productionize it with the API.

Get started

Two paths. One intelligence layer.

Start with the REST API, or connect Claude in about five minutes. Same data, same sources, same hourly refresh.

Explore the API docsSet up the MCP Connector