Build on DataGauge

Send your first event and read a number back, in about five minutes.

• QuickstartIntegrate DataGauge from a bash script, no dependency, in under 5 minutes. Send your first event, read your numbers back, and rehearse in test mode before going live.

Thin wrappers for the few runtimes where the plain curl call needs help.

• OverviewFor most stacks the curl example is the SDK. SDKs exist only where a runtime actively fights the simple fire-and-forget path, one per execution model.
• @datagauge/edgeDataGauge for serverless & edge runtimes: event sends ride the platform's waitUntil so they survive the response.
• @datagauge/convexDataGauge for Convex. track() schedules a registered internalAction transactionally with your mutation: rollback sends nothing, commit guarantees the send.
• @datagauge/clientDataGauge for client & offline runtimes: a durable queue with pluggable storage, idempotent replay, and server-side clock-skew correction. Ship a public key.
• @datagauge/nodeDataGauge for short-lived processes: a synchronous buffer with one explicit flush before exit. No timers, no daemon threads, no surprises.

Every endpoint, credential, and scope across the ingest, read, and control planes.

• POST /v1/eventsAppend-only event ingestion: one object or an array, idempotency, timestamp skew correction, and the exact-money payment path.
• POST /v1/objectsMutable subscription state, upserted with last-write-wins semantics. The source of MRR.
• GET /v1/metrics/*The read API: the same numbers the dashboard shows, for your own pricing pages, admin panels, and investor updates.
• Billing webhooksMRR and revenue with zero product code: paste your Stripe or Polar signing secret and point the biller at your endpoint.
• Control APICreate apps, mint and revoke keys, set webhook secrets over HTTP, so an agent can run the whole loop without touching the dashboard.
• MCP serverPoint Claude, Cursor, or any MCP client at mcp.datagauge.dev and let an agent read your numbers directly. Read-only, no install, always current.

How keys are scoped, how test and live environments stay isolated, and why the numbers you read back are trustworthy.

• Keys & scopingTwo kinds of key, one hard rule: money is server-authoritative. Public keys ship in binaries and can never write revenue. Plus test mode: sk_test_/pk_test_ keys and dg_test_ tokens run in a fully isolated test environment.
• Why the numbers are rightThe only thing a metrics product sells is trust in the numbers. Here is what that means mechanically.