LADLE vs 'just use the Anthropic API directly.'

The most technically-honest question anyone asks about LADLE: "Why pay $20/mo when I could just call the Anthropic API directly for way less?" Let's do the math.

**The API cost side.** Claude Sonnet on Anthropic's API is $3/MTok input, $15/MTok output (verified 2026-08-09). A typical chat turn — 500 input tokens + 200 output tokens — costs roughly $0.0015 + $0.003 = $0.0045. At 300 turns/month (heavy daily use), you'd spend $1.35 raw. Adding prompt caching brings it down further.

**The API friction side.** You'd need: an Anthropic account with billing, API credentials in your environment, a client library, a way to persist chats (SQLite? Postgres?), a UI (build your own? Cursor? Claude Desktop?), memory/instructions handling, projects, artifact storage, and a way to attach files. All buildable; all real work.

**The gap between "API access" and "finished product."** The API gives you the raw model. Everything else — the UI, the storage, the file handling, the design canvas, the kitchen panel, the shared surfaces, the mobile experience, the auth, the payment infra — you build yourself or forgo.

**When the API path is right.** - You're a developer with time to build (or an existing chat product to plug Claude into). - Your usage is very low (a handful of turns per week) — a $20/mo subscription is overkill. - You need programmatic access from your own scripts/tools (LADLE is a chat product, not an API). - You want to build something specifically not-available in any consumer product.

**When LADLE (or Claude Pro, or ChatGPT) is right.** - Your time is worth more than the $18-19/mo delta above raw API costs. - You value a finished product over building it. - You use AI conversationally more than programmatically. - You want features that require infrastructure (Projects, Memory, chat history, mobile).

**The LADLE-specific answer.** If you're going to buy a finished chat product anyway, LADLE's $20 sends $8 to WFP with a monthly receipt. If you're not going to buy a finished chat product — you're going the API route — LADLE isn't the right recommendation and I'd rather you use the API and donate to WFP directly than pay us reluctantly for infra you don't need.

**Honest self-assessment.** If reading this list makes you realize "I could probably build my own chat interface in a weekend," you probably should. LADLE isn't the right product for you. Come back when the build/maintain math flips.