March 14, 2026
Clone Wars, but make it APIs
AEP (API Design Standard and Tooling Ecosystem)
Copycat or cleanup? Devs clash over a new API rulebook
TLDR: AEP released its 2026 edition, a public rulebook and tools for building APIs. Commenters split between calling it a Google copy, demanding clearer explanations and real users, and praising it for ending design squabbles—while some insist “API” should mean more than just web CRUD.
AEP—Application Enhancement Proposals—just dropped aep-2026: an open rulebook for building APIs (how apps talk to each other) plus zero‑configuration tools. The site boasts clients like a Terraform provider, a UI dashboard, a command‑line app, and an MCP server, all built on lessons from Google, Microsoft, Roblox, and IBM. It publishes versioned “editions,” promises plug‑and‑play tooling, and invites contributions on aep.dev. Sounds tidy and grown‑up—until you peek at the comments.
That’s where it goes full drama. One camp screams copycat, with spenczar5 pointing at AEP 160 mirroring Google’s AIP‑160. Another roasts the messaging: [phrotoma] says the homepage lists everything except a plain‑English “what is this” statement. A calmer crowd, like [loevborg], likes the idea—less bikeshedding (endless nitpicking)—but notes missing batch create/update and an odd batch get. And [khaledh] brings the nostalgia: “API” should mean more than web CRUD (create, read, update, delete). Jokes fly—“AIPs with extra vowels,” “Ctrl K to Ctrl Confused,” and “Batch? I barely know her.” Verdict: Clone Wars vs Cleanup Crew, and everybody wants receipts.
Key Points
- •AEP is an API design specification and guideline paired with open-source, zero-configuration tooling.
- •AEPs draw on lessons from industry veterans at Google, Microsoft, Roblox, IBM, and contributors to HTTP and IETF specifications.
- •A versioned edition model is used, with aep-2026 announced as officially released.
- •Conformant APIs can use provided clients and tooling, including a Terraform provider, UI, CLI, and an MCP server.
- •AEP positions itself as an open standard with tooling usable across any API that conforms to its editions, and maintains a blog with updates and design details.