UCP.NET: Why Fakturus Is Betting on UCP and an AI-Only Future
AI is fundamentally changing the way we find, compare, and consume products and services. Traditional search and “SEO” remain relevant, but AI opens up a rapidly expanding alternative for discovery and interaction.
At Fakturus, we are building micro-SaaS services for end-users and small to medium businesses with an AI-first — and ultimately AI-only — approach.
Examples of such services include:
- File sharing
- Scheduling
- Forms
- Time management
- and many more
Each of these services has a clear focus and is simple in use and functionality. As more specialized services like these emerge, the need for a clear, unified integration layer becomes increasingly important.
Our services are designed not just for classic user interfaces, but primarily for interactions with AI agents and easy discovery by AI systems.
Enter the Universal Commerce Protocol (UCP)
This is exactly where Google’s new Universal Commerce Protocol (UCP) comes into play.
Universal-Commerce-Protocol
UCP is an open standard that enables AI agents to:
- Find and compare products
- Query availability and pricing
- Complete full purchase processes
… all without proprietary, individually developed interfaces for each different agent type.
This new element serves, in our view, as a unified commerce platform (UCP.NET) — a central API layer independent of whether a service runs in the browser or as a native mobile app.
From SEO to AI Discovery
So far, services have mainly been discovered through traditional search engines like Google and then consumed through the interfaces they provide. In that world, services were optimized for SEO — search engine visibility.
However, users are increasingly starting their queries with AI-based systems instead of classic web search. In fact, recent data shows that 37 % of consumers start their search with AI rather than Google Search.
Danny Goodwin
As a result, services and offerings should be optimized not only for SEO but also for AI agents — and this is exactly the opportunity that Google’s UCP aims to address.
AI-First — and Eventually AI-Only
By consistently using AI even in our development process, we were able to build a complete UCP stack in a matter of days, including support for all major transport options.
For us, this isn’t just a technical experiment — it’s a strategic shift toward a future where services are:
- Found by AI agents
- Interacted with by AI agents
- Composable and discoverable outside of traditional UI pathways
We believe this is the direction in which digital services are evolving.
What Is the Current Status?
At the moment, UCP.NET is in internal testing and is targeted for integration across all our services by the end of January.
Although UCP is currently available only in the U.S., support for associated standards such as Model Context Protocol (MCP) already makes it possible to use UCP in environments such as ChatGPT or Claude.
This means that, even today, developers can leverage UCP with existing AI agent platforms — before a wider commercial rollout.
What’s Next?
Depending on interest and relevance, we are considering releasing UCP.NET as open-source.
We welcome feedback and discussion — feel free to reach out to us at info@fakturus.com.
If you haven’t already, you can subscribe to the Fakturus blog to keep up with future updates.