# Quickstart

Canonical URL: https://texttree.ai/en/docs/quickstart/
Markdown URL: https://texttree.ai/en/docs/quickstart.md
Page type: docs
Translation status: approved
Legal status: not_required

## Summary

Create an account, connect TextTree to an AI agent, send your first SMS, and confirm the agent can receive replies.

## Source content

## Agent-first setup

Start with the Prompt tab if you are working in Claude, Codex, Cursor, or another AI coding agent. It gives the agent a complete setup brief for creating a TextTree account, securing backup codes, preparing a dedicated SMS number, connecting MCP, and testing outbound and inbound SMS.

Use the direct code tabs when you already have a TextTree access token and want to send a message from your own shell or application.

## Required values

Before running the API examples, set these placeholders:

- `TEXTREE_ACCESS_TOKEN`: your TextTree bearer token from the app or agent bootstrap flow.
- `+15551234567`: the destination phone number for your test SMS.

The API examples use the current TextTree V1 contract:

- Base URL: `https://api.texttree.ai/api/v1`
- Messages endpoint: `https://api.texttree.ai/api/v1/messages`
- Auth header: `Authorization: Bearer $TEXTREE_ACCESS_TOKEN`
- Message field: `phone_number`

## Create an account

Start in the TextTree app, or let an AI client create a headless account with username/password over the API or MCP surface. Email, Google OAuth, wallet auth, and headless agent accounts all normalize into the same TextTree identity model.

```txt
https://app.texttree.ai/signup
```

Headless API bootstrap:

```bash
curl https://api.texttree.ai/api/v1/accounts \
  -H "Content-Type: application/json" \
  -d '{
    "username": "agent-demo",
    "password": "correct horse battery staple"
  }'
```

The bootstrap response returns one-time backup codes and a `txt_...` bearer token. Account creation is limited to one successful account per IP address every five minutes.

## Send and verify

After sending your first SMS, open Messages in the console to inspect status, cost, failure reason, and the message timeline. Configure a webhook before going live so inbound replies and delivery events reach your application or agent workflow.

## Go live

Add billing, complete compliance, register or connect a sender, and switch the environment to Live.