Skip to main content
Send a periodic heartbeat so the PIN controller knows the agent is healthy. Each heartbeat updates the last-seen timestamp and GPU inventory. If the agent goes past the heartbeat timeout, the controller reclaims and re-enqueues any assigned jobs.
All /v1/agent/* routes require both Authorization: Bearer <jwt-or-api-key> and X-Agent-Secret: <AGENT_REGISTER_SECRET>.

Endpoint

POST /v1/agent/heartbeat

Authentication

Request body

string
required
Stable agent id returned by registration.
array
Current GPU inventory snapshot.
string
Agent status, such as online.
string
Agent binary version.

Response

Standard PIN envelope. data is:
boolean
Whether the heartbeat was accepted.

Example