{"id":66771,"date":"2026-06-08T23:54:24","date_gmt":"2026-06-08T23:54:24","guid":{"rendered":"https:\/\/www.europesays.com\/ai\/66771\/"},"modified":"2026-06-08T23:54:24","modified_gmt":"2026-06-08T23:54:24","slug":"from-token-maxxing-to-tokenomics-pega-keeps-ai-real-and-pragmatic","status":"publish","type":"post","link":"https:\/\/www.europesays.com\/ai\/66771\/","title":{"rendered":"From token maxxing to tokenomics: Pega keeps AI real and pragmatic"},"content":{"rendered":"

Pragmatism and agentic AI rarely go hand in hand. We regularly hear stories of organizations seeing costs skyrocket while the profits AI is supposed to deliver fail to materialize. Pegasystems aims to change this for organizations and developers. It does so by firmly taking and maintaining control within its own Infinity platform, taking a pragmatic approach to AI deployment, and by giving greater prominence to Blueprint and its associated AI engine.<\/p>\n

Developments in agentic AI are moving fast. Not so long ago, there was the (in our view, peculiar) trend that developers had to use as many AI tokens as possible. That was a good indicator of how well someone was doing, apparently. However, this so-called token maxxing seems to have had its day already. There seems to be a bit more realism now, and the focus has shifted to what is called tokenomics. In other words, how do you ensure that you actually derive value from the AI tokens you use?<\/p>\n

Essentially, Pega aims to answer the above question this week at PegaWorld in Las Vegas. It\u2019s doing so through a significant number of announcements. We\u2019ve analyzed these announcements to paint a clear picture of what the company aims to achieve and what you can expect. There is certainly some interesting innovation, but pragmatism and predictability take center stage. A good thing in our view, because that\u2019s what organizations can actually use.<\/p>\n

\u201cBiggest update to Infinity in a decade\u201d<\/p>\n

The foundation of Pega was, is, and remains the Infinity platform. Naturally, it\u2019s getting an update. According to Chief Product Officer Kerim Akgonul, this isn\u2019t just any update, but \u201cthe biggest update in a decade.\u201d The main reason for this is that Pega has succeeded in integrating Pega Blueprint AI into Infinity. The result is Infinity Studio. With this, Pega intends, among other things, to bring \u201cclassic\u201d and \u201cmodern\u201d AI together in a single development environment.<\/p>\n

To understand why this integration is important for Pega and for customers, it\u2019s helpful to clarify exactly what Pega Blueprint is. Blueprint is an agentic environment that enables the design of applications. Not building or running them, but designing them. It is, therefore, primarily an ideation environment. You don\u2019t build anything there, but you see what you need to do to build the application you want to create. You can also get a preview of what the app will ultimately look like. Pega Blueprint AI is free to use on the company\u2019s website.<\/p>\n

Faster transition from design to development<\/p>\n

Since its launch over two years<\/a> ago, Pega has significantly enhanced Blueprint and its accompanying AI engine. For instance, Pega has added more granular context regarding how applications fit within a company. Pega is also announcing an integration with AWS Transform this week, which we wrote about<\/a> during the latest edition of AWS re:Invent.<\/p>\n

With Transform, AWS wants to bring mainframes into the modern era. The idea is to convert applications written in COBOL into newer versions. AWS Transform handles the analysis of the COBOL code and generates the necessary documentation. Pega Blueprint AI then designs a modern application based on this documentation, without leaving the AWS Transform environment.<\/p>\n

Within the Pega ecosystem, however, Pega Blueprint AI remained a fairly standalone environment. As Akgonul puts it: \u201cThere was a gap between Blueprint and the development and authoring environment.\u201d That gap no longer exists. With the announcement of Infinity Studio, Blueprint AI has become part of the development platform.<\/p>\n

What does Blueprint add to Infinity Studio?<\/p>\n

In practice, the integration of Blueprint into Infinity Studio means that Pega adds agentic AI to the Infinity platform, where many best practices, business rules, and other deterministic AI features are already present. You could call it a marriage between old and new, or established and emerging. Provided Pega executes this well (the release is in Q3), this will make the Infinity platform as a whole much more modern and powerful.<\/p>\n

The integration of Blueprint into Infinity Studio also adds a sort of \u201ceasy button\u201d to Infinity. That is to say, the designs coming from Blueprint immediately generate an implementation plan in Pega Infinity Studio. This should help developers build applications not only quickly but also efficiently, while paying attention to issues such as security and governance.<\/p>\n

Pega Infinity Studio will (of course) also feature an AI assistant to help developers. Developers don\u2019t have to use Pega\u2019s own AI Assistant. They can also utilize tools like Claude Code, OpenAI Codex, GitHub Copilot, or AWS\u2019s Kiro. Additionally, Pega is making a number of MCP tools and skills available to enable integration with Pega from external agents as well.<\/p>\n

\"Screenshot<\/a>Every application built on Pega is now a Model Context Protocol (MCP) server. This enables Pega workflows to be used in every AI agent.<\/p>\n

Smart use of different types of AI<\/p>\n

By integrating Blueprint AI with Infinity, Pega is taking a step toward building applications more efficiently. However, agentic AI can still be a significant cost factor. Pega, however, only uses the most powerful variant of agentic AI during the design phase. That is, within Blueprint and the new Infinity Studio. At runtime, i.e. once the applications are deployed and running, the applications use a semantic model (rather than Blueprint\u2019s reasoning model).<\/p>\n

The advantage of the semantic model is that it invokes application control agents that are good at handling tasks efficiently and consistently. According to Pega, these agents do not start from scratch every time, which would lead to a lot of extra work and thus additional costs. The agents use a simple AI query to estimate what is expected. Based on that, an agent finds the best workflow and executes it step by step. If it becomes necessary to delve deeper into matters, it can always switch to a more advanced model. <\/p>\n

Several Pega systems and apps come together in what is called the Agentic Process Fabric. That connects all of the processes and applications together and ask it to carry out specific workflows. This isn\u2019t limited to Pega apps, you can also connect external (AI) tools to it.<\/p>\n

Through the above approach, Pega aims to keep costs in check while also maintaining predictable outcomes. The latter is always a challenge with non-deterministic models. By keeping the semantic models strictly in line, and, crucially, not letting them start from scratch every time, Pega maintains a high level of predictability. In principle, the agents follow only pre-approved workflows.<\/p>\n

Billing based on outcome, not tokens <\/p>\n

Saying that costs are going down is one thing; actually being able to demonstrate that this is the case is quite another. With the AI Token Cost Calculator, organizations can gain more insight into this. This seems primarily to be a way to put their own offering in the spotlight. That is to say, it compares the costs of Pega AI with alternatives that bill based on tokens. According to Pega, many customers can achieve savings of up to 20x.<\/p>\n

As already mentioned, in our view, this AI Token Cost Calculator is more of a marketing tool for Pega than anything else. There\u2019s nothing inherently wrong with that, but it\u2019s good to know. What it primarily demonstrates, in our view, is that Pega has a different approach to AI billing. With this company, you don\u2019t pay per token, but per completed case. In other words, organizations pay based on the outcome of the AI deployment. As long as tokens are used but there is no actual result from their deployment, customers pay nothing. <\/p>\n

Pega charges a flat rate per completed case, regardless of how much AI is used behind the scenes. That might sound a bit ill-conceived, because in theory this could end up costing Pega a fortune. According to CTO Don Schuerman, it won\u2019t be that bad. The reason for this confidence lies in how Pega has the workflows executed by AI. It still relies heavily on deterministic, \u201cold-school\u201d AI. Those costs are easy to estimate and predict. It even tries and keep the costs for non-deterministic AI as predictable as possible by having agents use semantic models that don\u2019t have to do a lot of reasoning and don\u2019t have to start from scratch every time.<\/p>\n

For customers, billing per case rather than per token means that metrics like ROI and TCO become much clearer. This allows them to keep agentic AI in check not only technically but also financially. It is important, however, that customers are and remain satisfied with these outcomes, but that goes without saying. <\/p>\n

Pega stays in control<\/p>\n

The way Pega handles agentic AI fits well with how the company has operated for a long time. It strives to make all new technologies part of its own platform. Partly because this allows it to offer a uniform experience for customers, but of course also because it keeps customers within its own platform as much as possible. For example, we recall the time when RPA (Robotic Process Automation) was all the rage. At Pega, it was never a specific goal to enter the market with this, but rather to make the platform as a whole more appealing.<\/p>\n

We\u2019re now seeing something similar happen with agentic AI. Pega recognizes its value but isn\u2019t going all out on it. It integrates it into its own platform but also imposes restrictions where necessary. See the section above on the combination of reasoning AI and semantic AI in Infinity. By having it operate within clear boundaries, it is possible to minimize the non-deterministic aspects of AI agents as much as possible. This makes agentic AI more appealing to highly regulated industries, but also to customers who simply want predictability in costs and performance.<\/p>\n

In other words, Pega delivers a software stack for agentic AI that is, as they say, highly opinionated. It has already made many decisions for customers, for example regarding how a specific agentic workflow performs tasks. This may not result in the the most interesting or dynamic applications of agentic AI. The question is whether this is a problem. We don\u2019t think so. Agentic AI must be kept in check to be useful. That is what Pega is trying to do.<\/p>\n

\"Screenshot<\/a>AI Assistant in Pega Infinity Studio working on a task from an implementation plan to complete the application build process.<\/p>\n","protected":false},"excerpt":{"rendered":"Pragmatism and agentic AI rarely go hand in hand. We regularly hear stories of organizations seeing costs skyrocket…\n","protected":false},"author":2,"featured_media":66772,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[179,7493,37592,37593,37594,37595,37596],"class_list":["post-66771","post","type-post","status-publish","format-standard","has-post-thumbnail","category-agentic-ai","tag-agentic-ai","tag-agentic-artificial-intelligence","tag-aws-transform","tag-infinity-studio","tag-pega-blueprint-ai","tag-pegasystems","tag-tokenomics"],"_links":{"self":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts\/66771","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/comments?post=66771"}],"version-history":[{"count":0,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts\/66771\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/media\/66772"}],"wp:attachment":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/media?parent=66771"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/categories?post=66771"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/tags?post=66771"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}