Anthropic Claude Fable 5

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 rules that lets one computer program request information or actions from another. Think of a power outlet: you don't need to understand the electrical grid, you just plug in using a standard interface, and electricity arrives. APIs work the same way for software.

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 authentication is an hour not spent on the product that actually differentiates you. Auth is deceptively hard to get right: password hashing, session management, token rotation, account recovery, rate limiting, and breach response are all places where a small mistake becomes a catastrophic security incident that could kill a young company's reputation. Services like Auth0, Clerk, or Supabase Auth give you battle-tested security, social logins, and MFA in an afternoon, usually free at your current scale. The strongest argument against this: vendor lock-in combined with pricing that scales per-user. Hosted auth is cheap until it suddenly isn't, and migrating thousands of user credentials off a provider later is painful and risky, sometimes requiring forced password resets. If you succeed, you may face a steep bill or a miserable migration at exactly the moment you're scaling fastest.