Open app

Instrument Your Code

No install ceremony, no pre-made key. Paste this prompt into Claude Code — or any coding agent — and it instruments the signal that matters, requests its own API key, and hands you a dashboard link. You approve two things along the way: the metric list and the key.

Set up Plexus telemetry in this project.

1. Fetch https://plexus.company/agent.md and follow it as your reference.
2. Install the SDK: pip install plexus-python (Python). For other languages, send telemetry over plain HTTP as described in the reference.
3. Read the codebase and propose 5-10 metrics/events worth tracking — latency and errors on external calls, throughput, lifecycle, key domain events. Show me the list (file:line, metric, why) and wait for my approval.
4. Request an API key: POST https://app.plexus.company/api/auth/claim with {"name":"<project-name>"}. Give me the verification_url to open in my browser, then poll GET https://app.plexus.company/api/auth/claim/<device_code> every 5s until approved.
5. Save the key as PLEXUS_API_KEY in the gitignored env file and add an empty entry to .env.example. Never hardcode or commit it.
6. Instrument the approved list with px.send()/px.event() under source id "<kebab-project-name>". Never block the hot path or throw from telemetry.
7. Run it so at least one real point ships, then give me my dashboard link: https://app.plexus.company/dashboards?quick=<source-id>.

What the agent does

  1. Fetches plexus.company/agent.md — the canonical machine-readable integration reference — and follows it.
  2. Installs the SDK: plexus-python for Python projects; other languages POST to the ingest endpoint directly per the reference.
  3. Proposes 5–10 metrics/events with file:line and rationale, then waits for your approval before touching code.
  4. Mints its own key via the device-code claim flow: it POSTs to https://app.plexus.company/api/auth/claim, gives you a verification_url to open, and polls GET /api/auth/claim/<device_code> until you approve. The key lands in your gitignored env file as PLEXUS_API_KEY — never hardcoded, never committed.
  5. Instruments the approved list with px.send()/px.event(), ships at least one real point, and ends with your dashboard link: https://app.plexus.company/dashboards?quick=<source-id>.

That's the whole on-ramp. To view and operate what you've instrumented (queries, dashboards, monitors), open the Plexus app and ask its built-in AI.