People searching “osiris ai” usually want the open-source OSINT platform published at osirisai.live and on GitHub as simplifaisoul/osiris—not a closed SaaS chatbot. Public docs describe it as aggregating aviation, maritime, seismic, conflict, cyber, CCTV, weather, news and related feeds onto one WebGL map, with the same data exposed as plain HTTP JSON under /api. Checked against https://osirisai.live/docs and the README on 2026-10-14.
OI (“the AI in OSIRIS”) is optional: Assist and Forecast run on a model key you bring (OpenAI, Anthropic, Gemini, OpenRouter, Groq, DeepSeek, xAI, Mistral, Qwen). Docs say the key stays in the browser, is sent in headers for your run, and is not stored on the server. There is also an MCP endpoint at https://osirisai.live/api/mcp for agents.
Name collision note: osirisai.com markets “OSIRIS AI — Drone OS”, which is a different product surface from the open-source map dashboard. This guide focuses on the osirisai.live / simplifaisoul/osiris stack that dominates “osiris ai” SERP titles on 2026-10-14.
Searchers often arrive with intents like “OSIRIS AI live”, “OSIRIS AI app”, “OSIRIS CCTV”, or “OSIRIS ai open source”. The practical answer is the same stack: open the hosted map, toggle layers, call public GET APIs, or clone the MIT repo. OI prediction and Assist are extras on your own model budget—not required to use flights, cameras, or earthquake layers.
Architecturally, docs describe a Next.js client with MapLibre GL for WebGL rendering and Next.js API routes that normalize upstream formats, rate limits, and CORS. That boundary is why curl examples work against /api/* without a privileged “internal” tier for the public feeds. Optional RECON scanning is delegated to a separate backend and fails closed when SCANNER_KEY is unset.
If you only need counters for monitoring, /api/stats fans out to heavy feeds and returns small JSON (flights, sats, cctv, weather, incidents, etc.). For subdomain enumeration without touching the target, /api/osint/certs?domain=wikipedia.org uses certificate transparency. Always re-check response.ok—upstream outages are treated as normal.
This site is not affiliated with simplifaisoul, osirisai.live, or osirisai.com. We do not host OSIRIS, store your model keys, or provide support. Upstream feeds can lag, rate-limit, or go down; conflict layers are not a substitute for official sources. Active recon tools must only be used lawfully. Prices, Patreon funding, and star counts change—verify on GitHub and the vendor site.
Word-of-mouth guides and third-party write-ups can lag behind the repo. Prefer osirisai.live/docs and the GitHub README for install flags, keyboard shortcuts, and responsible-use notes. This notes site may trail releases by days.
