What problem does it solve? During an OSINT investigation, agents must decide which external tool (browser automation, social-media collection, account discovery, academic access) fits each task, and avoid routing to integrations that are unconfigured or failing. ## Core Features & Use Cases - Routing decision tree: Maps investigation needs (deleted-post tracking, username discovery, corpus analysis, DOI lookup) to the right integration such as Junkipedia, Maigret, Apify, Arbiter, or Unpaywall. - Preflight-gated selection: Checks integrations/preflight.py output and only routes to integrations with green status, falling back to core verbs or local tool indexes otherwise. - Evidence-grounded output handling: Enforces saving raw responses to the case directory, citing access methods, and treating Maigret results as unverified leads only. - Use Case: An agent needs to track how a claim spread across platforms; it consults the routing table, confirms Junkipedia is green via preflight, reads its integration.md, and executes the documented API calls. ## Quick Start Ask the agent which external integration should handle tracking a deleted social post and have it check preflight status before routing.
