# OneShot Agent SMS Send

> OneShot Agent SMS Send is a paid API for AI agents from win.oneshotagent.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-11).

Send an SMS message to a specified phone number via the OneShot Agent platform, billed per-message via x402.

## Facts

- Endpoint: POST https://win.oneshotagent.com/v1/tools/sms/send?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/oneshot-agent-sms-send-46fa06c9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ZUyN2tN2mkis5d36lIEh3

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability oneshot-agent-sms-send-46fa06c9 -d '<json body>'
```

Example prompt: Send a text message to +1-415-555-0198 saying 'Your appointment is confirmed for tomorrow at 3pm — see you then!'

## When to prefer this

Use this endpoint when an AI agent needs to send a single, programmatic SMS to a known phone number and can handle x402 micropayment authentication. Prefer it over email when the recipient is more reliably reached by text, or when immediacy matters. It fits well within agentic workflows that already use OneShot's ecosystem (enrichment, email, browser automation) and need a complementary SMS leg. Not suited for bulk SMS blasts or carrier-grade high-volume messaging.

## Known failure modes

- Invalid or unformatted phone number in 'to' field — message not delivered
- Missing or invalid x402 payment header — 402 Payment Required returned with quote
- Message body too long or empty — rejected before dispatch
- Recipient number is on a do-not-contact list — delivery fails silently or with error
- Polling request_id not found or expired — 404 from status endpoint
- Insufficient USDC balance or payment signature invalid — 402 or 401 returned

## How this service works

Tools, payments, and compute orchestration for autonomous AI agents.

## Authentication

- **`x402Payment`** — paid tool endpoints use the [x402 payment protocol](https://x402.io).
  First call returns `402 Payment Required` with a quote; sign and resend the request
  with `Authorization: <signed payment header>` and `X-Quote-ID: <quote_id>`.
- **`agentId`** — free read-only endpoints accept `X-Agent-ID: <wallet>` (0x… address).
- **`soulKey`** — soul marketplace seller dashboard uses `Authorization: Bearer soul_…`
  (issued by `POST /v1/soul/register`).
- **`acpBearer`** — Stripe ACP checkout sessions use a separate bearer token plus the
  `API-Version: 2026-01-30` header.

## Async tools & polling

Most tool endpoints return `202 Accepted` with `{ request_id, tool, status }`. Poll
`GET /v1/requests/{id}` (with the same `X-Agent-ID`) to retrieve the final result.
A WebSocket fallback is available at `wss://<host>/v1/requests/subscribe`.

## Pricing

See [docs.oneshotagent.com/pricing](https://docs.oneshotagent.com/pricing) for the full
table. Per-call costs for this environment, rendered from the same config the routes bill from:

| Tool | Cost |
|---|---|
| Web search | $0.001 |
| Web read | $0.002 |
| Research | $0.01 |
| Person enrichment | $0.005 |
| Email verification | $0.001 |
| Deep research (person) | $0.05 |
| Social profiles | $0.50 |
| Local business search | $0.01 |
| Commerce search | $0.002 |
| LinkedIn history sync | $0.02 per bounded run |
| LinkedIn reply | $0.02 per message |
| LinkedIn profile view | $0.01 per view |
| LinkedIn post reaction | $0.01 per reaction |
| Email send | quote-based; service fee from $0.005 per send |
| SMS send | $0.0035 per segment per recipient |
| Voice call | $0.35/minute + $5.00 number registration on the first call |
| Browser task | quote-based; minimum $0.005 |
| Website build | quote-based; from $1.00 |
| Compute goal | quote-based; minimum budget $1.00 + 20% platform fee |

## Error format

`{ "error": "<machine_code>", "message": "<human readable>", "details": <optional> }`.
Validation errors include a `details` field with the failing field paths.

## Output

Returns a JSON object with a receipt_id (unique receipt UUID), request_id (async job UUID), tool name ('sms'), and status ('processing'). Because the endpoint returns 202 Accepted, the agent must poll GET /v1/requests/{request_id} with its X-Agent-ID header to confirm final delivery status.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "to": {
   "type": "string"
  },
  "message": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "tool": "sms",
  "status": "processing",
  "receipt_id": "rcpt_uuid",
  "request_id": "uuid"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/oneshot-agent-sms-send-46fa06c9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from win.oneshotagent.com](https://www.zero.xyz/host/win.oneshotagent.com/llms.txt)