# Talk to your own agent from your phone

> Talk to your own agent from your phone: 0 companies fully do it, 19 with a limit, 42 carry the tag. Every listing in Messaging APIs with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/messaging.personal-agent-channel/
- Markdown: https://www.anchorterminal.com/niches/messaging.personal-agent-channel/index.md (~1,900 tokens)
- Slim: https://www.anchorterminal.com/niches/messaging.personal-agent-channel/index.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/messaging.personal-agent-channel/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 19 | 42 | 14 | 15 |

## What counts as done

A message from the owner's phone reaches the running agent and its reply arrives in the same chat, including after a restart of the agent.

Measured, for our own tests: the message reaches the agent within 10 seconds, and the owner's account has no ban or restriction over 30 days.

How agents ask for it: let me message my agent on Telegram; control Claude Code from my phone; text my assistant on iMessage; have my agent ping me when it's done

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **360dialog WhatsApp API + MCP (360dialog GmbH)**: Official Cloud API route, so no unofficial-client ban, and the Inbox API's GET /api/v1/messages/ lets a restarted agent read what it missed. Needs a business number at €49 or more a month, Premium for the Inbox, and Meta onboarding first.
- **AWS End User Messaging (Amazon Web Services, Inc.)**: SNS to SQS lets a sleeping agent pull messages it missed without a public URL, but the owner must first register a 10DLC or toll-free number (about 15 days for toll-free) to text their own phone.
- **Bandwidth Messaging API + MCP (Bandwidth Inc.)**: listMessages with messageDirection=INBOUND lets an agent pull texts without a public URL, but SMS from a registered number needs a sales-onboarded account; the free Build trial allows it for 30 days to your own number only.
- **Bird API + MCP (Bird B.V.)**: MCP Events push inbound SMS or WhatsApp to an MCP client through mcp.bird.com, and webhook replay covers downtime. The owner still needs a registered SMS sender or a connected WhatsApp number, and there is no Telegram.
- **ClickSend SMS API + MCP (ClickSend Pty Ltd)**: GET /v3/sms/inbound with mark-as-read gives a pull loop that survives a restart without a public URL, but this is SMS from a ClickSend number, with sender rules per country and no published polling limits.
- **Infobip API + MCP (Infobip Ltd)**: Pulling inbound messages works without a public URL, so a restarted agent can catch up; but the owner needs a business sender on SMS or WhatsApp, and how long unpulled messages are kept wasn't readable.
- **Kudosity (Known Pty Ltd)**: GET /v2/sms and GET /v2/whatsapp/messages with direction filters let an agent read what arrived while it was down, without a public URL. It is a business sender on AU, NZ and UK SMS, priced from 8 cents AUD a part.
- **Linq (Linq App Inc.)**: The owner texts a Linq line from their own iMessage, and a restarted agent can read the thread back by API, but live delivery is by webhook to a public URL with retries for only 30 minutes.
- **Photon (Something Great Inc.)**: The owner texts a shared-pool iMessage number on the Free plan, the SDK holds an outbound connection so no public URL is needed, and catchUp recovers missed events after a restart. acc-64 shows recovery failing silently, and the terms limit free use to evaluation.
- **Plivo API (Plivo Inc.)**: Polling the Message list for inbound works without a public URL, but texting yourself on a US number needs a 10DLC campaign or toll-free verification first, and the API allows 300 requests per 5 seconds.
- **Sendblue (Round One, Inc.)**: The owner texts a free shared line from their own iMessage, and the messages list lets a restarted agent read what arrived; live inbound needs a public webhook, and acc-59's 20-second latency exceeds the 10-second bar.
- **Sinch Messaging APIs + MCP (Sinch AB (publ))**: The Conversation API includes a Telegram Bot channel, and GET messages or fetch-last-message lets an agent read what arrived while it was down. Live inbound still needs a public webhook, and it adds a vendor between the owner and Telegram.
- **Telegram Bot API (Telegram Messenger Inc.)**: getUpdates long polling needs no public URL and stores updates 24 hours across a restart; acc-45 to acc-47 run this daily. But acc-48 saw sleeping sandboxes miss messages, acc-56 a 409 polling loop fixed only by token rotation, and acc-57 per-bot outages with no status page.
- **Telnyx API + MCP (Telnyx LLC)**: SMS to your own phone works once 10DLC is registered, but inbound arrives only by webhook to a public URL, with 3 retries and a failover URL; there is no pull API for missed inbound.
- **Twilio API + MCP (Twilio Inc.)**: The Messages list can be polled for inbound without a public URL, and acc-51 used the WhatsApp sandbox for phone control of Claude Code. Texting yourself by SMS needs 10DLC, which acc-01 could not get approved for one number.
- **Vonage Messages API + MCP (Vonage Holdings Corp.)**: WhatsApp or SMS to a Vonage number works, but inbound is webhook-only to a public URL, and the Messages API spec has no message list to recover what arrived during a restart.
- **Wati (Clare.AI Limited)**: GET /api/ext/v3/conversations/{target}/messages lets an agent read what arrived without a public URL, but this is a business WhatsApp inbox from £49 a month, and the terms bar automated tools from accessing Wati.
- **WhatsApp Business Platform (Cloud API) (Meta Platforms, Inc.)**: The official route avoids the unofficial-client bans of acc-52 and acc-58, but inbound is webhook-only to a public HTTPS URL (acc-69 hit a rejected .dev domain), and Meta's terms admit general-purpose AI assistants only where law requires.
- **YCloud (YCloud International Pte. Ltd.)**: A business WhatsApp number the owner can message on the free plan, but inbound is webhook-only, with no pull API to recover messages after a restart.

- not this job: Prelude (DING SAS): Prelude is a verification and business-notification API; inbound needs a public webhook and there is no consumer chat channel or pull API for an owner's own agent.

## What stops agents finishing

- WhatsApp bans a personal number used by an unofficial client
- a sleeping sandbox holds no polling connection, so messages never arrive
- messages sent while the agent restarts are dropped and cannot be fetched again
- per-bot Telegram outages with no status page

## Around it

After: personal-assistants.chat-remote-control, agent-harnesses.always-on-assistant.

## Where this comes from

Weight 14 of 100 in Messaging APIs: 15 of 69 accounts; the dominant agent-builder use on Hacker News (Telegram bots around Claude Code, OpenClaw channels); most use Telegram or unofficial WhatsApp rather than a paid listing

As data: https://www.anchorterminal.com/api/v1/use-cases/messaging.personal-agent-channel.json, or the MCP tool get_use_case with id messaging.personal-agent-channel. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
