textbee.dev valid

textbee

The open-source SMS gateway for developers, automations, and AI agents. Turn an Android phone you already own into an SMS gateway and send or receive text messages over a simple REST API, with no per-message gateway fees.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T10:03:11.939Z. Cached copy · Source on textbee.dev

# textbee

> The open-source SMS gateway for developers, automations, and AI agents. Turn an Android phone you already own into an SMS gateway and send or receive text messages over a simple REST API, with no per-message gateway fees.

textbee is two parts: an Android app running on a phone you own, and a REST API at https://api.textbee.dev that your code calls. Messages travel over the phone's existing carrier plan, so there is no per-message markup and no number to rent. The whole stack is MIT licensed and can be self-hosted.

Authentication: every request carries an x-api-key header holding an API key created in the dashboard at https://app.textbee.dev/dashboard.

Send an SMS:

curl -X POST "https://api.textbee.dev/api/v1/gateway/send-sms" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "message": "Your appointment is confirmed for Tuesday at 10am.",
  "recipients": [
    "+12025550123",
    "+12025550124"
  ]
}'

List messages:

curl "https://api.textbee.dev/api/v1/gateway/messages?limit=50&page=1" \
  -H "x-api-key: YOUR_API_KEY"

## API

- [API reference](https://textbee.dev/docs/api-reference): every public endpoint with parameters, request and response fields, error codes, and a curl example.
- [OpenAPI spec](https://textbee.dev/openapi.json): the same reference as machine readable OpenAPI 3, generated from the running API.
- [Full documentation in one file](https://textbee.dev/llms-full.txt): every docs page and the whole API reference as plain text.

## Documentation

- [Overview](https://textbee.dev/docs): textbee turns an Android phone you own into an SMS gateway. Learn how it works, pick a way to send and receive, and find every docs section.
- [Getting started](https://textbee.dev/docs/getting-started): Set up textbee in four steps: create an account, install the Android app, register your phone and send your first SMS from code.
- [Setting up textbee](https://textbee.dev/docs/getting-started/setting-up-textbee): Create a textbee account, install the Android app, connect the phone and grant permissions, then send your first SMS from the API.
- [Registering a device](https://textbee.dev/docs/getting-started/registering-a-device): Connect an Android phone to your textbee account with a QR code or an API key, name it, set a default device and check its heartbeat.
- [Reconnecting an old device](https://textbee.dev/docs/getting-started/reconnecting-an-old-device): Reconnect a phone to its existing textbee device with the Device ID, so its message history and settings stay in one place.
- [API keys and authentication](https://textbee.dev/docs/getting-started/api-keys): Authenticate textbee API calls with the x-api-key header: create, test, store, rotate and revoke API keys from the dashboard.
- [Sending SMS](https://textbee.dev/docs/sending-sms): Send SMS through your Android phone with the textbee API: single sends, bulk sends, scheduled sends, SIM choice and delivery tracking.
- [Sending SMS](https:/
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=textbee.dev · GET /v1/domain/textbee.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for textbee.dev:
1. POST https://agentwebmap.com/v1/sites/textbee.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://textbee.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/textbee.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/textbee.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.