Three ways in. All of them are the same HTTP call underneath.
Send your first error
Five minutes, one HTTP call — in curl, PHP, WordPress, Node, the browser, Python, Go, Java, Rust or OpenTelemetry.
API reference
Every endpoint a client sends to: its keys, its answers and its limits.
Build your own client
Six rules, one small implementation in six languages, and what each field buys you.
Browser client
JavaScript errors from real visitors — our script, or twenty lines of your own.
Connect your AI agent
codesafe speaks MCP: one command and Claude Code, Claude Desktop or Cursor can read your errors and act on them.
OpenTelemetry
Already instrumented? Point a collector at codesafe and skip the client entirely.
Which one do I need?
- Running WordPress? Install the plugin, paste a key, done — nothing else on this page applies.
- Running PHP or Node? Use the drop-in client, or write the twenty lines yourself.
- Already instrumented with OpenTelemetry? Point the collector's logs pipeline at codesafe.
- Anything else — Python, Go, Java, Rust, .NET? One POST, a key in a header, JSON in the body.
- A CMS with no client yet — TYPO3, Drupal, Shopware, something in-house? Write to us. We build the client and integrate it; you do not pay for the plumbing.
The rules every client follows
- Fire and forget. Reporting may never slow or break the app that reports.
- One second, hard. A codesafe instance that is down costs your users nothing.
- Never retry what may have arrived. Only an unopened connection or a
429/503goes once more, off the request path. - Redact first. Passwords, tokens and cookies never leave the box.
- Batch, then flush. PHP sends once after the response; a long-running process every second or two.
There is no SDK you must use and no vendor lock to accept. The WordPress client is public and is a working reference implementation of everything on these pages.