A screenshot of the aep.dev site that shows rule 300, which establishes the rules for edition-based versioning.
The aep-2026 edition has shipped! 🚀
This release establishes long-term stability as a critical foundation. The new versioning mechanism and release cycle supports our tooling ecosystem, which now includes a Terraform Provider, CLI, MCP Server, and more.
Read more: aep.dev/blog/aep-202...
For those who prefer video, @rambleraptor.bsky.social has added a walkthrough showing how the Terraform provider works: www.youtube.com/watch?v=dL3E...
The AEP project (especially this Terraform provider) feels like a culmination of a large portion of my career. As an industry, we spend so much effort trying to manually translate our APIs to the tools that users use. AEPs are proving that better-designed APIs lead to stronger tooling faster.
Announcing a Terraform provider for the AEP project! 🚀
Most companies staff engineers just to maintain their Terraform provider. However, just by making AEP-compliant APIs you get providers for minimal effort beyond writing the API.
Read @rambleraptor.bsky.social's post: aep.dev/blog/terrafo...
Look who's here! 👋
Happy (A)PI Day, 3.14!
May you always receive the response codes you were expecting.
What to know what's cooking with for the AEP project in 2025? Learn about our plans and roadmap, including:
- The path to a major release
- The tooling to accompany it
- Upcoming community events
- Our longer term goals
- … and how to get involved!
aep.dev/blog/2025-ro...
To learn more about the history of the AEPs project, the philosophies that guide it, and how to benefit from the tooling that supports an AEP-compliant approach, read the full article: aep.dev/blog/history...
They build upon Google's AIPs with a stronger formalization of the API design guidance itself, to:
- Act as a reference point for organization-agnostic best practices.
- Enable an official ecosystem of tooling to make best-practice APIs easier to build and consume.
3. AEPs provide an ecosystem of server-side and client-side tooling to produce and consume AEP-compliant APIs.
2. AEPs include design patterns for common use cases such as long-running operations, resource revisions, filtering, with best practices aggregated from API design experts with experience at Google, Microsoft, Meta, Roblox, and DataBricks.
1. AEPs are a API design specification for gRPC and REST APIs, with a heavy focus on resource-oriented design and standard methods that operate on them.
API Enhancement Proposals (AEPs) are a specification and tooling for building best-in-class resource oriented APIs.
Where did the AEPs come from? What are the underlying motivation and philosophies of the project? In our latest post, @y.tsutsumi.io explains that and more! aep.dev/blog/history...