Developer surface

PulseTrace + Probe agent

Check from inside your own network.

Run a PulseTrace agent inside a VPC, on-prem or behind a VPN to monitor internal services the public probe fleet cannot reach. The agent registers with a scoped token, reports health and version, and runs the same monitor types as the fleet.

Set it up in three steps

1Infrastructure → Agents → New agent: name it, pick the environment, copy the enrolment token.
2Run the agent container with that token somewhere that can reach the targets — the exact command, with your token filled in, is shown on the Agents page.
3On any monitor, choose the agent as a region. Results land on the same timeline as public probes.

Start monitoring free Read the docs

Agents page

● eu-internal-1     healthy   v1.4.2   last heartbeat 12s ago
● us-vpc-a          healthy   v1.4.2   last heartbeat 9s ago
○ dc-legacy         offline   v1.3.0   last heartbeat 3d ago

Questions about Probe agent

What does the agent need outbound?

Only HTTPS to the PulseTrace API. It initiates every connection; nothing needs to be opened inbound.

More developer surfaces

MCP serverLet Claude, Cursor and your own agents run your monitoring.REST APIEverything the dashboard does, as JSON.OpenAPI importTurn a spec into a monitor per endpoint.