# FTSOBest x402 and Watchdog API

> Machine-readable discovery for scoped wallet automation, prepaid credits, watches, alerts and notification recipients.

## Documentation
- [Credits user documentation](https://ftso.app/docs/credits/overview)
- [Watchdog user documentation](https://ftso.app/docs/watchdog)
- [Human documentation](https://ftso.app/docs/machine-api/overview)
- [OpenAPI 3.1](https://ftso.app/api/x402/openapi.json)
- [Watchdog webhook schema v2](https://ftso.app/x402/schemas/watchdog-webhook-v2.schema.json)
- [API catalog](https://ftso.app/.well-known/api-catalog)
- [Live pricing and signal catalog](https://ftso.app/api/x402/pricing)

## Authentication
1. POST /api/x402/auth/challenge with wallet, scopes and an optional label.
2. Sign the exact returned EIP-4361 SIWE message.
3. POST /api/x402/auth/token with message and signature.
4. Send the returned token as Authorization: Bearer <token>.
5. List or revoke tokens through /api/x402/auth/tokens.

## Contract
- x402 v1: x402Version 1, proprietary ftsobest-prepaid-router scheme; not x402 V2 exact. Standard x402 payment clients cannot pay through their standard flow.
- Scopes: read, write, spend; read is always included.
- Errors: JSON objects contain error and a stable code listed by OpenAPI.
- Rate limits: honor HTTP 429 and Retry-After.
- Idempotency: use Idempotency-Key where OpenAPI declares it; replay the same key with the same body.

## MCP (read-only)
- Endpoint: https://ftso.app/api/mcp (Streamable HTTP, stateless, JSON responses)
- Public tools, no login: get_pricing, list_watch_types, estimate_watch_cost, get_platform_stats, get_ftso_analytics, get_provider_rewards
- Account tools after OAuth sign-in with the user's wallet (scope account:read): get_claimable_rewards, get_credit_balance, list_watches, get_watch, list_alerts
- OAuth discovery: https://ftso.app/.well-known/oauth-protected-resource/api/mcp
- Resources: this file and the OpenAPI description