The Ministry of Electronics and Information Technology has narrowed its government-wide agentic artificial intelligence platform to two qualified vendors—CoRover and Kyndryl Solutions—after a National e-Governance Division technical evaluation on 18 September, Moneycontrol reported on 23 September. Cactus Technology Solutions and NEC Corporation India were disqualified in the same notice, while the first production use case stays DigiLocker, treated as a minimum viable product for a reusable “ask, do and escalate” bot framework other ministries could configure later.
What NeGD evaluated
NeGD describes the procurement as a Conversational and Agentic AI Bot Framework—effectively bot-as-a-service for citizen-facing programs. Qualified bidders must show agents that answer queries, execute approved transactions, and escalate when policies require human review. Tender documents on NeGD’s site spell out modular frameworks, secure tool-calling into APIs, audit trails, multilingual support, and human-in-the-loop checkpoints for irreversible actions.
Moneycontrol’s review of the 18 September evaluation notice said CoRover and Kyndryl cleared the technical bar while Cactus and NEC did not. Other entrants including Tata Consultancy Services and Innefy Labs had participated in earlier stages, according to Analytics India Magazine’s recap, but the shortlist for build-out now sits at two.
DigiLocker MVP scope
The agent’s first job is practical: fetch and share documents, manage a user’s document drive, and invoke DigiLocker APIs under Parichay or DigiLocker authentication with consent logging. Citizens should be able to complete routine tasks without navigating multiple menus, while sensitive steps route to human operators when risk thresholds trip.
Implementation timelines in Moneycontrol’s reporting point to four months of development for the DigiLocker agent followed by twelve months of operations and maintenance. Architects are expected to reuse components so additional government bots can onboard through configuration rather than greenfield code—aligning with MeitY’s push to centralise AI capacity instead of letting each department fund duplicate stacks.
Policy context
MeitY has been staffing an internal AI team and publishing framework documents that stress consent, auditability, and deployment flexibility across SaaS APIs or on-premises infrastructure. The DigiLocker pilot sits next to broader digital public infrastructure work, including optional alignment with NPCI’s explorations of AI agent registries for payment-adjacent workflows—though the NeGD tender’s first milestone remains document retrieval, not payments.
Regulators elsewhere in Asia are watching India’s approach because a reusable agent shell could reduce duplicate spend on citizen chatbots that fail audit reviews. MeitY’s disqualification of two bidders shows the bar is technical compliance first—marketing slides about autonomous agents do not substitute for demonstrated tool-calling and escalation paths in evaluation demos.
For Ananya Krishnan’s AI desk, the verifiable facts are the 18 September evaluation outcome, the qualified vendors, the disqualified names, and the MVP timeline—not marketing claims about autonomy levels vendors cannot yet prove in production. The government’s ask-do-escalate model explicitly keeps humans accountable for high-impact actions.
What builders must deliver
Technical evaluators looked for LangGraph-, CrewAI-, or equivalent orchestration layers, discoverable agents third-party apps could embed, and error-handling that fails closed when authentication or consent checks fail. NeGD’s corrigendum-heavy tender also mentions natural-language querying over structured government datasets as a stretch capability after the document agent works.
Disqualified bidders may challenge outcomes through the tender’s remediation process; until commercial bids close, citizens will not see a new bot in DigiLocker apps. CoRover’s prior public-sector chat work and Kyndryl’s systems-integration footprint positioned both as credible integrators, but the evaluation notice is the authoritative cut, not vendor press releases.
What comes next
Financial bids and work orders will determine who ultimately builds the MVP if two vendors remain in play. Other ministries watching the outcome include those running UMANG services and state portals that could consume the same framework once DigiLocker proves audit and consent logs at scale.
On 24 September the story for readers is narrow and sourced: MeitY and NeGD qualified CoRover and Kyndryl, dropped Cactus and NEC, and pointed the agentic stack at DigiLocker first—with four months to build and a year of run support before the framework claims to be reusable across government.