## Schedule a post and prove it landed

One task, told three ways. Every column ends at the same state: the destination is **verified live** only after A1 Lane reads the post back from the platform.

| Step | Web app | Assistant | API |
| 1. Connect a channel | Connect page → Bluesky (handle + app password) or Mastodon (instance + token). | “Which accounts are connected?” → `list_accounts` | `POST /api/v1/workspaces/{ws}/accounts` |
| 2. Draft the post | Compose → caption, pick the destination → Save draft. | “Draft a post: A weekend outside.” → `create_draft` | `POST /api/v1/workspaces/{ws}/posts` with `mode: draft` |
| 3. Schedule it | On the draft → Schedule → Sat 09:00. | “Schedule it for Saturday 9am.” → `schedule_draft` | `PUT /api/v1/workspaces/{ws}/posts/{id}` with `scheduled_at` |
| 4. Prove it landed | Post page → the receipt for each destination. | “Did it go out?” → `get_verification_status` | `GET /api/v1/workspaces/{ws}/posts/{id}` → each destination's status |

### All three end here

Sample The receipt every column above arrives at — a stored specimen, not a checked post.

Delivery receiptSample

## A weekend outside

 Mastodon · @northcoast@mastodon.example

FieldAsked forWhat came back
Scheduled
Sat 09:00 PT
Sat 09:01 PT✓
Visibility
Public
Public✓
Title
A weekend outside
Matches✓

Verified live — read back from Mastodon
Checked Sat 09:01 PTREAD BACKVERIFIED

The full call sequence with its arguments is in [Assistant setup](/docs/agents#worked-example); every route and tool links back here from the [MCP reference](/docs/mcp).

---
HTML version: https://a1lane.ai/docs/schedule-and-prove
Tool surface: v1.3, generated from the running server