5.3 Compute-as-a-Service (CaaS)

ACP’s service layer will evolve into a Compute-as-a-Service (CaaS) architecture. Various user groups can access compute resources through token-based transactions or partnerships.

User Type	Purpose	Usage Model	Revenue Flow
AI Startups	LLM inference, fine-tuning	Tiered API plans	ACP payments split to contributors
Content Creators	Video/image generation	One-time API calls	Direct ACP consumption
Educational Institutions	Research, training	Partnership or grant model	Brand value and contributor onboarding