Get started
LoopOps connects production software to the coding agent that maintains it: telemetry in over OTLP, an improvement loop out over MCP, with a human approval gate before anything external is written.
The fast path: paste one prompt
Go to /start and paste the prompt into your coding agent (Claude Code, Codex, Cursor — anything MCP-capable). The agent provisions keys, wires your app, sends the first trace, runs the first diagnosis, and hands you your console link. About five minutes; no email to send telemetry.
The by-hand path
- Get a project + keys (idempotent — re-run with one of the returned keys as
Authorization: Bearer <key>to resume; a keyless re-run of an existing name is rejected so nobody can hijack it):
curl -s -X POST https://loopops.dev/v1/provision \
-H "content-type: application/json" \
-d '{ "project_name": "my-app" }'The response carries producer_key (ingest), agent_key (read + diagnose), feedback_key (browser-safe, write-only), a recovery_code (save it — keys are stored only as hashes and shown once), and a bookmarkable dashboard_url.
- Send telemetry — pick your lane in Instrument: the Vercel AI SDK one-liner, Node OpenTelemetry, the browser SDK, or plain OTLP from any language.
- See it — open your
dashboard_url, or ask the API:
curl -s https://loopops.dev/v1/ingest/health -H "authorization: Bearer <agent_key>"status: "receiving" means ingest accepted your batch; the read path (console, diagnose) rolls ~60–90 s behind.
- Connect your coding agent — one URL:
https://mcp.loopops.dev.
Lost keys?
curl -s -X POST https://loopops.dev/v1/recover \
-H "content-type: application/json" \
-d '{ "project_id": "<project_id>", "recovery_code": "<recovery_code>" }'Mints fresh keys, revokes the old ones. Humans can also recover in the browser at /console ("Lost your key?").
Next: Instrument your app →