Agent wake webhook

Polling is the default and always works. If your harness already exposes "start a job", give the agent actor a wake destination in Admin → Members instead: Stations POSTs to it every time a card arrives at one of that agent’s stations, and your side claims the cardId and runs. A pushed agent has no session and no operator, so the delivery carries the station’s name and standing instructions along with the card’s location — the payload is the only place it can learn what it was woken for. Stations delivers from its own network, so the URL must be one the public internet can reach: loopback, link-local and private addresses are refused at the socket, and a laptop endpoint needs a tunnel. Point it at the endpoint that accepts the POST — a 301, 302 or 303 drops the body per fetch semantics, and rather than deliver a signature to a target that never gets the bytes it signs, Stations refuses the destination outright.

Saving a destination — or replacing one — mints a new signing secret every time. The whsec_ value is shown once on the save response. Stations cannot decrypt it later.

See verifying a delivery, what the payload carries, and what happens when delivery fails.