Minister of Digital Development of Kazakhstan Zhaslan Madiyev, in an interview on the Baitassov Live YouTube channel, spoke about how the state views AI in public services and integration with the private sector. The conversation included eGov GPT, the idea of state APIs for connections (including with banks), and an IT export valuation of “over $1.1 billion” — this follows from the video interview.
What Happened
An interview with Zhaslan Madiyev, Minister of Digital Development, Innovations and Aerospace Industry of Kazakhstan, was released on the Baitassov Live YouTube channel.
In the discussion, which is important for the fintech market, three directions were highlighted:
- eGov GPT — as an AI assistant for consultations and interaction with public services in a chat format;
- “state APIs” as an approach to integrations with the private sector, including banks;
- an IT export valuation for Kazakhstan of “over $1.1 billion” (without specifying the methodology and period within the current source).
Country and Market
Kazakhstan is a market where digital habits have long lived in banking applications: users expect to see payments, transfers, purchases, certificates, and notifications in a single interface.
Therefore, the conversation about “state APIs for banks” is not an abstract GovTech idea. It is an attempt to make public services part of the customer journey where a person already spends time: in a bank or fintech service application.
Why It Matters
If state integrations truly become mass-market and equally accessible to different players, banks will have a clear product lever: embedding certificates, statuses, and other scenarios into their applications without unnecessary transitions and queues.
The main signal here is that Kazakhstan is publicly promoting the “public services as infrastructure and API” model, and competition is shifting to who can make the user journey shorter and clearer.
The second part is AI. The very fact of mentioning eGov GPT in such an interview is important, but for the market, the decisive factors will be the quality of answers, data limitations, and which scenarios the assistant will actually be trusted with, rather than being left at the level of a “chat for consultations.”
What’s Next
In practice, everything will come down to the details: whether a public description of which state APIs are available, on what conditions, and which integrations are already working for banks will appear.
For now, this is more of an outlined course than a measurable story: without metrics on eGov GPT and without clear rules for connecting via API, the market will not be able to assess where the concept ends and a working product begins.