Answers, documentation, and direct access to the team.
Search the knowledge base or browse by category.
Nuclir is built for teams making consequential technology, infrastructure, market, and research decisions that require current, attributable external intelligence.
An evaluation begins with a decision process your team already owns. The goal is to inspect coverage, source quality, context, and delivery against a real operating question.
Nuclir follows consequential change across technology, infrastructure, markets, and science, including compute, energy, logistics, climate, satellite observation, and quantum systems.
Nuclir retains source and timing with the record so users can inspect the evidence behind an answer and distinguish current evidence from uncertainty.
Teams use The Console for investigation and The API for integration. Webhooks deliver subscribed changes to systems that need to react as the underlying record changes.
Yes. Webhooks are designed to deliver signed, ordered change notifications to a configured endpoint, while the API supports current queries and historical retrieval.
Nuclir is designed to protect data in transit with post-quantum cryptographic standards. The security page describes the scope and implementation commitments in detail.
Customer-provided positions, schedules, and other scoped inputs remain separated from the shared intelligence model and are handled under the applicable product and data-processing terms.
Nuclir combines appropriate public records, licensed datasets, and observation sources. Source terms and data boundaries are assessed for each coverage area.
Contact Nuclir with the relevant use case and data category. The team can provide the applicable product, privacy, and data-processing information.
Access is scoped to the product surfaces, coverage, delivery patterns, and operational requirements relevant to an organization. Contact Nuclir to discuss an evaluation.
Nuclir is currently accessed through a direct evaluation and access process so the product can be aligned to the decision context and technical requirements.
The documentation explains the data model, delivery interfaces, and operating assumptions behind Nuclir. It is written for technical teams that need to understand how intelligence reaches a human workflow or a production system.
For product questions that cannot be answered by a general guide, contact the team with the relevant decision context. We will respond with the evidence and interface details that apply to that use.
Start with the interface or operating question in front of you, then move to the underlying documentation when you need detail.
Endpoints, response shapes, authentication, and the data model for systems integrating with Nuclir.
How subscribed changes are signed, ordered, retried, and handled by an endpoint.
Data boundaries, transport security, access controls, and the status of external assurance work.
Direct help for an evaluation, integration, data question, or operational issue.
Before an integration is designed, define the entity, change, or operating condition the receiving system needs to understand. That decision determines the right delivery pattern, whether a current query, monitored change, or historical record.
The API and The Console use the same underlying intelligence. A technical integration should therefore be able to reproduce and inspect the evidence a human user sees, rather than maintain a separate interpretation.
The team can help with an evaluation, integration, data question, or operating issue.
Contact our support team