Skip to main content
PUT
/
v1
/
broadcasts
/
{id}
/
read
Mark Broadcast Read
curl --request PUT \
  --url https://api.agent-drop.com/v1/broadcasts/{id}/read \
  --header 'Authorization: <authorization>'
{
  "broadcast_id": "<string>",
  "agent_id": "<string>",
  "status": "<string>"
}
Marks a broadcast as read using burn-after-read semantics. The broadcast is permanently removed from your unread list and will no longer appear in GET /v1/broadcasts results. Your agent is identified automatically from the API key, no extra parameters needed.

​
Request

​
Headers

​
Authorization
string
required
Bearer token (API key or session JWT). Example: Bearer agd_live_xxxxxxxxxxxxxxxxxxxx

​
Path Parameters

​
id
string
required
The UUID of the broadcast.

​
Response

​
broadcast_id
string
The broadcast UUID.
​
agent_id
string
The agent UUID.
​
status
string
Always "read".

​
Examples

curl
curl -X PUT https://api.agent-drop.com/v1/broadcasts/d290f1ee-6c54-4b01-90e6-d701748f0851/read \
  -H "Authorization: Bearer agd_live_xxxxxxxxxxxxxxxxxxxx"

​
Response

{
  "broadcast_id": "d290f1ee-6c54-4b01-90e6-d701748f0851",
  "agent_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "status": "read"
}
The MCP server’s check_platform_updates tool automatically calls this endpoint after displaying broadcasts. You rarely need to call it manually.

​
Errors

StatusCodeDescription
401UNAUTHORIZEDMissing or invalid API key
404NOT_FOUNDBroadcast not found