Launching today
AICP (AI Consumption Protocol)

AICP (AI Consumption Protocol)

The standard for monetizing AI access to Open Source

5 followers

Open Source is in crisis. AI agents consume maintainers' work at scale, but give zero return. Some projects are now closing docs (e.g. Tailwind), hurting the community. AICP solves this with Freshness Gating: Stable N-1 (Previous): Always FREE. Ideal for students & startups. Stable N (Latest): Gated. AI agents need a Sponsor Token to unlock it. Enterprises pay for the "Fast Lane". The community stays free. Use aicp.json to align incentives.
AICP (AI Consumption Protocol) gallery image
AICP (AI Consumption Protocol) gallery image
AICP (AI Consumption Protocol) gallery image
AICP (AI Consumption Protocol) gallery image
Free
Launch Team
Intercom
Intercom
Startups get 90% off Intercom + 1 year of Fin AI Agent free
Promoted

What do you think? …

Maciej Gren
Maker
📌
Hey Hunters! 👋 I built AICP because I saw the Tailwind CSS maintainer close a PR for llms.txt saying he couldn't afford to make it easier for AI to consume his docs because it hurt his business. That hit me hard. We are optimizing our repos for AI, effectively training our replacements, for free. But blocking AI isn't the answer. The answer is value alignment. Professional tools (IDEs, Agents) need the latest version. Hobbyists just need a working version. AICP standardizes this "Freshness Gate". It lets AI agents know: "You can use v1.8 for free, but if your user is a Sponsor, here is the link to v1.9 docs. Ask the user to buy the token or let him now when the v.1.9 will be released." Let's save OSS sustainability together. Check it out on GitHub: https://github.com/SHGrowth/AICP
Wojciech Kargul

I would like to see this become a standard that is adopted quickly and globally across OSS libraries. That may sound like a dream, because in practice it would mainly be adopted by projects that are already affected by economic pressure. Enthusiasts who maintain libraries without any monetization strategy would likely not care at all. For them, more code reads mean more satisfaction and energy to keep going. To be honest, there is still a large number of such projects on the market, and only some OSS initiatives actually make money not all maintainers benefit financially from open source.

OSS companies that try to monetize have adopted the enterprise model for open source some time ago. Kestra is a good example: it’s a great orchestration tool and while the free OSS version is already very strong, they still offer additional features in the enterprise edition. My agentic IDE might not state this directly (and this is where the AICP standard could help), but it’s not really hard to discover.

Phuc Doan

Congratulations on the AiCP launch. The idea of enabling secure, scalable sharing of AI assets with a protocol feels very forward-thinking and practical. This could open up exciting new ways for builders to collaborate. Wishing the team a successful launch day.