Integrations
Every sponsor API is load-bearing in the workflow. This page shows what each one does, whether its key is configured, and the real request/response for every call made during the last incident response.
Configuration
| Service | Challenge | Env var | Status |
|---|---|---|---|
| SerpApi | Best AI Use Case | SERPAPI_API_KEY | CONFIGURED |
| Nutrient | Turn Documents Into Something People Actually Trust | NUTRIENT_API_KEY | CONFIGURED |
| name.com | Domain API Challenge | NAMECOM_API_TOKEN | CONFIGURED |
| Doctavian | Generate It Right. Sign It Tight. | DOCTAVIAN_API_KEY + _ACCESS_TOKEN | CONFIGURED |
| Foxit | Your Agent Shouldn't Sign That | FOXIT_CLIENT_ID | CONFIGURED |
| Xano | Rebuild a SaaS Tool You Hate | XANO_API_BASE | CONFIGURED |
| Gemini | (interpretation layer) | GEMINI_API_KEY | CONFIGURED |
CONFIGURED means a key is present, not that the call succeeded. Whether an API actually answered is decided by the run, and the ledger below is the record — each entry is tagged LIVE, LOCAL or DEMO SEEDED by what really happened. With no keys at all the full workflow still runs end to end on honest fallbacks and every screen stays usable.
Integration Activity Ledger
17 calls · 13 live · 4 fallback/seededOne row per real API touchpoint. LIVE = the sponsor API responded. LOCAL / DEMO SEEDED = honest fallback with the exact request we would have sent. Nothing here is fabricated.
Live web intelligence. AegisFlow runs one query per supplier plus market and disruption-news queries. Low or zero corroboration is treated as a negative signal, not ignored.
Document intelligence on both ends: text + field extraction from the six supplier PDFs on ingestion, and a PENDING-SIGNATURE watermark applied to the generated agreement before it reaches a human.
Supplier legitimacy from the domain system. A manufacturer claiming eight years of trading has a registered domain; if checkAvailability says its domain is still purchasable, nobody owns it — scored as absence of commercial footprint.
Turns the structured, evidence-backed decision payload into the Emergency Supplier Transition Agreement. The decision → payload → document chain is visible in the UI.
System of record for the tool we rebuilt — the disruption war-room spreadsheet. Normalized incident → supplier → claim tables plus an append-only audit_event stream.
Interpretation only — analyst summary and decision narrative. Every response is Zod-validated; facts and scores come from documents and deterministic computation, never the model.