Integrations
Loop Engine Cloud (hosted HTTP API)
What this is
The OSS Loop Engine (this site, @loop-engine/* on npm) defines the runtime model: states, signals, guards, transitions, and events. Loop Engine Cloud is Better Data’s managed deployment that exposes the same execution contract over HTTPS with tenancy, API keys, connectors, and product entitlements.
- Developers & integrations → HTTP API at
https://loops.betterdata.co(Bearer JWT for first-party services,le_API keys for external automation). - Operators → the Automation rail at
app.betterdata.co/automation(same loops conceptually; product UX does not use engine marketing names in the nav).
Canonical reference
The versioned, route-by-route contract (request/response shapes, errors, connectors, baseline routes, key management) is maintained in the monorepo alongside the apps/hosted-loops implementation:
Loop Engine Cloud HTTP API reference (source)
That file is the developer contract for paths under /api/v1/*. Update pull requests that change route handlers should update apps/hosted-loops/docs/api.md in the same change-set when the public JSON contract moves.
Related OSS docs
- HTTP adapter — webhook-style outbound adapter from the OSS runtime; not the same as Loop Engine Cloud ingress.
- Architecture — core Loop Engine concepts reused by the hosted service.
Pricing
Commercial packaging is described on the product site (do not hardcode prices in integration guides): betterdata.co/pricing.