Documentation

Mercur gives a process on your machine a public HTTPS endpoint, and keeps a record of every request that arrived at it. You point a webhook provider, a teammate or an agent at a URL, and you can read exactly what they sent.

What works today

Mercur is in alpha, and the docs only describe what is built:

• HTTP endpoints. A public URL per endpoint, with three run modes: record requests, forward them to a local port, or both.
• A macOS desktop app that carries traffic to your machine. Forwarding needs it.
• The browser console can create endpoints and record requests, but it cannot forward traffic to your machine.
• WebSocket and raw TCP are on Solo and Team. Subscribe from pricing (workspace owners). Guest and Free stay HTTP-only.

There is no Windows or Linux build and no command line client.

Two ways in

Reference

• Limits — what each plan allows and what happens when you reach a cap.
• Security and data retention — what is stored, for how long, and how to restrict who can reach an endpoint.
• Troubleshooting — every error the relay returns, and its cause.