Proof
Docs

Wire Proof into your app

Written for your agent as much as for you. Keys are per workspace and early access is invite-gated; everything below works the moment you hold one.

The tag

<script src="https://proof.dorsr.com/p.js"
  data-key="YOUR_WRITE_KEY" defer></script>

One tag. Pageviews, sessions, clicks, Core Web Vitals, JS errors, outbound clicks, and marked 404s flow immediately, single-page-app route changes included, each under a governed contract. Dev hosts (localhost, private ranges) are ignored unless the tag carries data-dev.

Hand it to your agent

Paste this to Claude Code, Cursor, or any agent with shell access:

Wire Proof analytics into this app.

1. Add this tag to the root layout, once, in <head> or at the end of <body>:
     <script src="https://proof.dorsr.com/p.js" data-key="YOUR_WRITE_KEY" defer></script>
2. Mark the 404 page so missing paths are measured:
     <meta name="proof-not-found" content="1">
3. Deploy, load one page in a browser, then read the number back:
     curl -s -X POST https://proof.dorsr.com/api/ask \
       -H "x-proof-key: YOUR_AGENT_KEY" -H "content-type: application/json" \
       -d '{"question":"pageviews today"}'
4. For product events, call:
     window.proof.track("myapp.thing_happened", { plan: "pro" })
   then propose a contract for each event name through the propose door,
   so the owner can certify it.

The agent door

Four verbs over plain HTTP; an MCP server wraps the same four for Claude Code and Cursor and ships with early access. Ask in plain English:

curl -s -X POST https://proof.dorsr.com/api/ask \
  -H "x-proof-key: YOUR_AGENT_KEY" -H "content-type: application/json" \
  -d '{"question":"did yesterday's deploy hurt checkout?"}'

Emit actions (deploys are the canonical case; retries dedupe on the id):

curl -s -X POST https://proof.dorsr.com/api/collect \
  -H "content-type: application/json" \
  -d '{"write_key":"YOUR_WRITE_KEY","events":[{
        "name":"agent.action.deploy","source":"agent",
        "external_id":"deploy-9b1f04d","event_time":"2026-07-22T13:00:00Z",
        "properties":{"target":"myapp.com","commit":"9b1f04d","outcome":"success","actor":"agent:ci"}
      }]}'

Propose a contract for a new event; only certified metrics answer with high confidence:

curl -s -X POST https://proof.dorsr.com/api/propose \
  -H "x-proof-key: YOUR_AGENT_KEY" -H "content-type: application/json" \
  -d '{"kind":"event_definition","name":"myapp.thing_happened","version":1,
       "humanMeaning":"A user did the thing that matters.",
       "properties":{"plan":{"type":"string","required":false,"pii":false}}}'

Agents propose and never silently certify. Certification is a signature by the workspace owner, or by their agent under a named standing grant; either way the stamp records who signed.

Privacy defaults

First-party only, no third-party requests, no fingerprinting (a random id in your own cookie), id-looking path segments scrubbed before storage, click text masked under data-proof-mask, coarse country only. One switch silences the tag entirely:

window.proofConsent = false        // or set cookie: proof-consent=denied

Access

Proof is in invite-gated early access while it hardens on the founder's production apps. Follow the build to catch the open.