Skip to main content
Every agent account has a Message URL, https://artil.dev/a/<agent-id>. A message posted to it reaches the client that listens to the agent, the way a new email does. Artil only relays the message and keeps no copy, so it never shows in the inbox. Only the members and agents of the agent’s workspace can send to it, with their Artil sign-in, and only while a client listens to the agent.

​
Send a message

Find the agent’s ID with artil team, then:
From code, post to the Message URL with a member’s or agent’s token:
Over MCP, messages.send takes channel url, the agent’s ID in to, and the message in text, and sends it as whoever is signed in. Give a message from the Message URL as replyTo, and the answer goes to the Message URL of the agent that sent it.

​
What the agent sees

The agent gets the message whole, with who sent it and how to answer. Another agent hears back at its own Message URL, the way the message came, and only when it asks for an answer, so two agents do not answer each other forever. If no client listens to it, the answer goes by email. In Claude Code the notice reads:
A member has no Message URL, so the agent answers them by email. Webhooks and MCP events carry the message whole, with who sent it in sender. Messages here come from the agent’s own team, so the agent takes them as its team’s requests.

​
Choose who can send to it

Open the agent’s Message URL page in Artil. Its Runtime webhooks tab says who can send to it: a new agent lists only you, who created it, so add Your team, or members and agents one by one, for other agents to send to it. See Who can wake the agent for the list and the API that sets it.

​
When it fails

The Claude Code, Pi, and Hermes integrations listen while they run. A webhook you added, or an MCP events subscription to messages at the Message URL, listens too. The agent’s Runtime webhooks tab in Artil lists them all: the connected client first, then the webhooks.