Radiant Intel™
Event Intelligence API

Primary-source event intelligence
for internal AI workflows.

Scope source-backed policy, trade, regulatory, macro, and strategic-technology events for your agents, quant workflows, and analyst tools. Enterprise integrations can return structured objects with citations, enrichment metadata, and bounded transmission context.

Slack integration

Bring Radiant Intel into Slack.

Route alerts and request intelligence from the channels where your team already works. Slack support brings primary-source monitoring, geopolitical risk movement, and analyst-ready briefings into the team workflow.

Existing users can enable Slack from the Radiant Intel app.

Slack use cases
Commands, alerts, and team visibility

Alerts in channel

Route monitored developments, RGRI movement, and priority alerts into the Slack channels your team already watches.

Commands for requests

Request intelligence from Slack when a question comes up in the workflow instead of moving the conversation to another tool.

Shared team context

Keep briefings and follow-up discussion visible to the analysts, policy leads, and decision-makers who need the same context.

Built for teams that need fewer context switches, faster shared context, and a clearer path from signal to decision.

Make internal systems source-aware

The wedge is not another report format. It is curated, source-grounded event data your models, agents, and analysts can inspect.

Source-backed event objects

Start from the atomic unit your systems can reason over: a timestamped event with source authority, citations, tags, jurisdiction, status, confidence, and novelty.

Transmission hypotheses

Connect policy artifacts to macro channels and strategic-tech channels, from current-account pressure to defense supply chains, procurement demand, and autonomy capex.

Agent-ready context

Package the prompting guide, source trail, model hooks, and analyst caveats needed for internal AI systems to use the event responsibly.

What's available

Enterprise/API work is scoped around machine-usable event intelligence. The target unit of analysis is a single source-backed intelligence_event; reports remain available as downstream surfaces.

Intelligence Events

Scope source-backed policy, regulatory, sanctions, central bank, energy, geopolitical, defense procurement, export-control, and strategic-tech events by geography, sector, tag, and event type.

Market Transmission

Frame how a source event may propagate through current-account, terms-of-trade, rates, capital-flow, risk-premium, defense-supply-chain, procurement-demand, or strategic-tech-capex channels.

MCP-Style Agent Tools

Map approved Radiant capabilities into callable tools for event search, source context, transmission framing, scenario requests, anomaly context, and macro context.

RGRI Scores

Use Radiant geopolitical risk signals and sub-scores as one context layer beside event-level evidence and citations.

Alerts & Monitoring

Design signed event-created, updated, quarantined, or retracted messages for internal systems where webhook delivery is part of the enterprise scope.

Reports & Briefings

Generate citation-rich narrative outputs when a human-readable report is the right surface, using events as the underlying context.

Enterprise Demo Pack

Four source-backed workflows, one event primitive

Enterprise pilots can be anchored in real official-source workflows: policy to FX, energy shock, sanctions trade, and defense AI/autonomy supply chains. Each demo is designed to show the same chain from source artifact to event object, enrichment, research context, API response, MCP-style tool output, and analyst decision frame.

Illustrative request shape
event_intelligence.search({
  geographies: "Japan,Singapore",
  eventTypes: "central_bank,strategic_tech_policy,defense_procurement",
  channels: "rates_expectations,defense_supply_chain,strategic_tech_capex",
  lookbackDays: 7,
  output: "event_schema"
})
Illustrative response schema
{
  "object": "intelligence_event",
  "status": "schema_example",
  "eventType": "<approved enterprise taxonomy>",
  "primarySource": {
    "name": "<official source name>",
    "authority": "<source authority>",
    "url": "<primary source URL>"
  },
  "affectedAssets": ["<asset or exposure tag>"],
  "transmissionHypotheses": [
    {
      "channel": "<approved transmission channel>",
      "modelHooks": ["<available research module>"],
      "confidence": "<scored when model-backed>"
    }
  ],
  "caveat": "Decision support only; not trading advice."
}
Source-backed demo tracks

Policy to FX

Bank of Japan monetary policy releases

source -> event -> rates/current-account channels -> macro and central-bank context -> agent answer

Energy Shock

EIA world oil transit chokepoints

source -> event -> terms-of-trade and energy-import-bill channels -> CGE/macro context -> analyst frame

Sanctions Trade

OFAC sanctions programs and country information

source -> event -> sanctions-access and supply-chain-cost channels -> trade anomalies -> MCP output

Defense AI & Autonomy Supply Chain

U.S. Department of Defense Replicator capability releases

source -> event -> defense-supply-chain and strategic-tech-capex channels -> trade/macro context -> Hodag validation frame

MCP Agent Connector

Let your agents query source-grounded events

Building an internal AI system? Enterprise work can map Radiant event search, source context, transmission framing, trade scenarios, anomaly context, and macro context into callable tools through the same scoped API layer.

Your orchestration layer keeps control. Radiant Intel supplies the curated primary-source context, enrichment metadata, model hooks, and caveats your system needs before it reasons over a policy or market question.

The result: your system can ask which policy or strategic-tech events may matter for currency risk, defense supply chains, autonomy adoption, or macro exposure, then inspect the source trail behind the answer.

How it works
01
Your agent identifies a need
"What policy or defense-autonomy events this week could matter for Japan currency risk or supply-chain exposure?"
02
It calls Radiant Intel as a tool
Your agent invokes an approved enterprise tool with geography, event type, channel, and lookback parameters.
03
Radiant returns source-backed events
The response includes source authority, citations, status, tags, confidence, novelty, affected assets, and suggested downstream use.
04
Your system asks for context
A follow-up transmission-framing call maps the event to current-account, rates, capital-flow, or risk-premium channels.

Multiple ways to integrate

REST API

Pull event intelligence on demand once the enterprise schema is scoped. Standard JSON responses preserve citations, source metadata, enrichment fields, affected assets, quality metadata, and model hooks.

Webhooks

For delivery integrations, push material source events and status changes into your systems with signed messages, retry expectations, delivery records, and replay requirements.

Slack

Deliver alerts into Slack channels and request intelligence from the flow of team discussion.

MCP Tools

Map Radiant Intel into Claude, Codex, or your internal agent stack as approved tools for event search, source context, research evidence, and bounded explanation.

Internal Validation Packs

Run private validation packs, including Hodag paper-fund decision frames, before promoting a track into wider enterprise workflows.

Frequently asked questions

Enterprise access uses scoped Bearer tokens tied to your organization. Sandbox credentials can be limited by endpoint, geography, and rate limit.

Enterprise event endpoints are scoped to return structured JSON with source citations, authority metadata, tags, affected assets, enrichment fields, confidence or quality metadata where available, and suggested downstream use. Reports and briefings remain available as narrative outputs.

For Enterprise/API work, the target unit of analysis is the intelligence_event: a durable, source-backed, versioned record that internal AI, quant, macro, delivery, and reporting workflows can consume.

Professional is designed for app access, reports, and public or RGRI-style surfaces. The full event feed, MCP-style tools, webhooks, custom schemas, and integration support are Enterprise/API features.

For approved pilots, we map Radiant capabilities to typed tools your orchestration layer can invoke. Tool outputs preserve citations, confidence or quality metadata where available, novelty, and caveats.

Rate limits depend on your plan. Enterprise customers get dedicated throughput with custom SLAs. Contact us to discuss your volume requirements.

Yes. We can provision a constrained sandbox with sample event objects, selected tool calls, and a private validation pack. Hodag-style internal paper workflows can be used to validate usefulness without exposing client process.

Yes. Radiant Intel supports Slack commands and alerts, so users can request intelligence and receive monitored developments in the channels where their teams already work.

Plug your internal AI into source-backed events

Give your agents and analysts a structured event feed with citations, enrichment metadata, strategic-tech context, and bounded transmission analysis.