Put source-backed intelligence
inside the systems you already run.
Bring cited research into the tools where your team already works. Scope an enterprise integration around your research questions, source requirements, and delivery needs.
Integrations are scoped enterprise engagements. The examples below illustrate possible workflows, not a public API catalog or features included in every plan.
Configured teams can receive alerts and request intelligence in Slack channels.Make internal systems source-aware
Give your models, agents, and analysts structured events they can inspect against the underlying source record.
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 your integration can be scoped to do
Define the source events your system needs, the evidence to retain, and how the output will be used. Available research modules and deployment configuration determine the final scope.
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.
Start with the question your system needs to answer
These four examples begin with official sources and a defined analytical question. An enterprise pilot can test how source records, structured events, and available research context would fit your system. The request and response below are illustrative schemas, not executable public API documentation.
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"
}){
"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."
}Policy to FX
Bank of Japan monetary policy releasessource -> event -> rates/current-account channels -> macro and central-bank context -> agent answer
Energy Shock
EIA world oil transit chokepointssource -> event -> terms-of-trade and energy-import-bill channels -> CGE/macro context -> analyst frame
Sanctions Trade
OFAC sanctions programs and country informationsource -> event -> sanctions-access and supply-chain-cost channels -> trade anomalies -> MCP output
Defense AI & Autonomy Supply Chain
U.S. Department of Defense Replicator capability releasessource -> event -> defense-supply-chain and strategic-tech-capex channels -> trade/macro context -> Hodag validation frame
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.
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.
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
Test the fit against your own workflow
Bring a research question, an example input, and the output your team needs. We can define a bounded pilot and agree what useful, supportable results would look like.