Anthropic Claude Fable 5.2

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 piece of software ask another for information or services. Think of a wall socket: you don't need to understand the power plant, you just plug in. Similarly, a weather app plugs into a weather service's API to fetch forecasts.

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 resets, session handling, multi-factor authentication, and breach response is an hour not spent on the product that makes you different. Authentication is a solved problem where mistakes are catastrophic and success is invisible to customers. A provider gives you tested security, social logins, and compliance paperwork on day one, usually free or cheap at your scale. The strongest argument against this is lock-in at the most sensitive layer of your system. Your users' identities and credentials live in someone else's infrastructure, under their pricing and their roadmap. Costs often climb steeply as you grow, and migrating away is painful, since password hashes may not export cleanly, forcing resets that lose users. If the provider has an outage, raises prices, or shuts down, your entire front door is affected, and you have limited ability to respond.