Anthropic Claude Fable 5.1

Explain what an API is to someone who has never written code. Do not use a restaurant or waiter analogy. Plain prose only — no headings, bullet points, or markdown formatting. Maximum 50 words.

An API is a set of agreed-upon rules that lets one piece of software ask another for information or actions, like a wall socket: you don't need to understand the power plant, you just plug in a standard shape and electricity arrives reliably.

A two-person startup is deciding whether to build their own user authentication or use a hosted provider. Give them a clear recommendation, then the single strongest argument against your own recommendation. Plain prose only — no headings, bullet points, or markdown formatting. Maximum 150 words.

Use a hosted provider. With two people, every hour spent on password hashing, session management, MFA, account recovery, rate limiting, and breach response is an hour not spent on the product that actually differentiates you. Authentication is a solved problem with well-audited implementations, the failure modes are catastrophic and public, and services like Auth0, Clerk, Supabase Auth, or Firebase Auth cost nothing at your scale. Pick one with a clean migration path (exportable password hashes, standard OIDC) so you're not trapped later. The strongest counterargument is vendor lock-in combined with pricing cliffs. Hosted auth providers have a history of steep price increases once you cross user thresholds, and by then your user model, sessions, and integrations are entangled with their APIs. Migrating live users off a provider without forcing password resets is genuinely painful, so the "cheap now" decision can become an expensive, distracting rewrite precisely when you least want one.