Trust & evidence
Built to be checked, not just trusted.
looot is a gateway that sits between your agents and real provider accounts. Every guarantee below is something implemented in this codebase today, not a policy promise layered on top of it. The local demo runs on deterministic fixtures and needs no account or provider key. Production connections stay fail-closed until they're configured and approved.
Tenant isolation
Every workspace, credential, run, and audit record is scoped to its organization at the data layer. One tenant's connections and history are never reachable from another's.
Versioned operation contracts
Each route to a provider operation is pinned to a specific contract version. A provider changing its schema doesn't silently change what your integration receives — it requires an explicit new version.
Evidence, not claims
A connection is shown as tested only when a durable test receipt exists to back that claim. looot never marks a provider connected, verified, or tested from an inference — only from a real receipt on record.
Hash-chained audit log
Every recorded action links to the previous record's hash, so the sequence can be verified end to end. Payloads are digested and sensitive fields are redacted before anything is written.
Effect-aware retry
When a provider call ends in an uncertain state — timeout, dropped connection, ambiguous response — the waterfall does not blindly retry. It distinguishes outcomes that are safe to reattempt from ones that might already have taken effect, so a run doesn't get double-charged for a single real action.
Raw, canonical, and mapped output
Every run result carries the provider's raw response, a normalized canonical form, and an optional mapped shape — with field-level provenance recording where each mapped field actually came from.
What we don't claim
looot does not carry SOC 2 or any other third-party compliance certification, and we won't state one here. Nothing on this page is a claim about external audits, uptime, or scale — it describes mechanisms you can read in the source and verify against the audit log and connection receipts in your own workspace.
See it on your own workspace
The setup center lists every account, environment variable, and scope a connection needs, without ever printing a secret. The onboarding flow walks through connecting a provider and running the first fixture end to end.