PIPES

Pipes: the kill switch for your agents

A pipe groups an agent (or agents) with the models they may use and a switch you can cut at any time. Cut a pipe and the gateway stops relaying that agent's new calls in seconds. RESTORE and traffic resumes, with no change to the agent.

The two states

Active — traffic flows

Cut — gateway stops relaying new calls. Reversible.

RESTORE flips the pipe back to Active. Your agent's URL and token are never reissued, so it resumes with no reconfiguration.

Cut and restore in the dashboard

Open Pipes in the sidebar (under GOVERN).
Click New pipe to create one with a name, workspace, and agent IDs.
Find the pipe and click CUT to stop its agents' new calls.
Click RESTORE to resume — nothing about the agent changes.

Every event (created, cut, restored) is shown in the pipe's audit feed with the actor and timestamp.

What a cut does and does not do

A cut does

Stop new calls from the pipe's agents at the gateway, within seconds.
Leave the agent's configuration untouched.

A cut does not

Revoke or rotate the upstream credential — it was never in the agent's hands.
Abort a call already in flight — that finishes; new calls are refused.

Cutting one pipe affects only that pipe's agents. Per-agent routing means no shared-key blast radius.

Via the API

# create a pipe
curl -X POST https://app.digitalpipe.net/api/pipes \
  -H "Cookie: session=YOUR_SESSION" \
  -H "Content-Type: application/json" \
  -d '{"name":"ecom-core","workspaceId":"acme-dev","agentIds":["agent-1"]}'

# cut it
curl -X PATCH https://app.digitalpipe.net/api/pipes/PIPE_ID \
  -H "Cookie: session=YOUR_SESSION" \
  -H "Content-Type: application/json" \
  -d '{"state":"cut"}'

# restore it
curl -X PATCH https://app.digitalpipe.net/api/pipes/PIPE_ID \
  -H "Cookie: session=YOUR_SESSION" \
  -H "Content-Type: application/json" \
  -d '{"state":"active"}'