Integrations

9 technologies, each with a visible job. Live means the real service answered; fallback means a labelled local stand-in is doing the job; missing means nothing is. The API is not answering, so no technology is claimed live.

0 live9 fallback0 missingData plane: checking…
  • Amplitude + Statsig

    Fallback (labelled)

    Amplitude records match, review, approve and remedy-confirmed events and the funnel per matcher variant. Statsig holds the gates (prepare the remedy automatically or ask first; FDA devices on or off) and the matcher experiment.

    Without it: No measured outcome, and no controlled rollout of a new matcher.

    State: Fallback: local event log and static gate config.

  • Superlinked SIE

    Fallback (labelled)

    Reads label and receipt text and matches product text against notices.

    Without it: Labels and receipts go unread.

    State: Fallback: regex identifier extractor.

  • Guild.ai

    Fallback (labelled)

    Control plane: runs the crews with scoped credentials, denies send and buy without an approval token, and fires the tracking cron.

    Without it: Agents would hold raw credentials with no boundary.

    State: Fallback: a local policy engine with the same rules.

  • Airbyte

    Fallback (labelled)

    Open-source connectors that ingest receipts, secondhand listings and the recall feeds (CPSC JSON, NHTSA campaigns).

    Without it: No automatic receipts, listings or recall feeds.

    State: Open-source connectors, running locally (PyAirbyte, in-process). Without a connected source it falls back to seed evidence.

  • Arcee

    Fallback (labelled)

    Remedy reasoning and plain-English explanation; the router picks the cheapest model that meets the quality bar.

    Without it: Every step runs on one costly model.

    State: Fallback: template text.

  • Cognee

    Fallback (labelled)

    The household memory graph and the corrections the person makes.

    Without it: Corrections and household context are forgotten.

    State: Fallback: in-process graph.

  • Firedrill

    Fallback (labelled)

    Simulated worlds and personas as a release gate.

    Without it: Failures are found by real families.

    State: Connected via MCP server and CLI when available; otherwise the local runner (the scenarios on /evals run in your browser).

  • SingleStore

    Fallback (labelled)

    System of record: cases, evidence references, the hash-chained audit trail, vectors and live analytics. Our notice index (the curated notices with their source versions) is searched in SingleStore.

    Without it: No durable case file, no replay, and no searchable notice index.

    State: Fallback: in-memory store, labelled as simulated.

  • Persona

    Fallback (labelled)

    Verifies the person once; a Relay live_human_presence claim rides on every remedy send and every staged purchase.

    Without it: A bot could file refunds.

    State: Fallback: verification stays pending and is never auto-passed.

Stripe is used in TEST mode only, behind the approval gate. It is a payment rail, not one of the nine.