API Gaps That Block State AI Projects

A state labour-department AI project was 'blocked on NIC' for nine months. The minutes said so. What was actually blocked was a sentence in the RFP: real-time API to the registration database for write-back of AI-verified files. Nobody in labour had offered that interface. NIC had not been asked for a read replica. The model vendor had no standing to demand a write path into a legal register. The GPU arrived on time. It sat in a crate.

This teardown is for SIs and programme managers who keep losing years to imaginary endpoints. It is dated 17 August 2026. It is not a catalogue of live government APIs — that catalogue would be stale before you finish the sentence. It is a method for naming gaps so they can be closed, scoped out, or admitted.

Five gaps that look like one

The first gap is absence. There is no interface. The honest move is retrieval of the PDF or a clerk in the official UI.

The second is permission. There is an interface, but not for you, not for this purpose, not for write. DigiLocker and UIDAI are full of this gap. A letter closes it. A scrape does not.

The third is quality. The interface returns codes that drifted in 2019, or a village list that predates the district split. That is the data-quality teardown, wearing an API badge.

The fourth is ops. The test tenancy is a myth. The only environment is production. The owner will not give you a key because the last guest wrote junk.

The fifth is pride. Someone promised the minister a unified layer. Admitting a PDF circular now feels like career harm. The crate of GPUs is the monument to that pride.

How to write the gap so a secretary can act.

Symptom	Name it	Action
RFP lists an endpoint nobody can URL	Invented API	Corrigendum; scope to PDF or official UI
Vendor has a sandbox key and production hopes	Permission gap	Letter or drop the connector
API works; codes are wrong	Quality gap	Freeze a mapping table; do not let the model 'fix' codes
Owner will not share a test tenancy	Ops gap	Fund a test tenant or do not integrate
Minutes blame NIC	Pride gap	Invite NIC to correct the minute with a dated ask

Write paths are usually the legal act

Many 'API gaps' are the system working. Mutation, FIR, licence, clearance, eligibility decision — the write is the act. Owners refuse write APIs because they have met SIs before. Respect that. Read connectors plus a human write in the system of record is the adult architecture. If you need a write, you need a legal instrument and a competent identity, not a REST fashion.

RPA and stored passwords will appear as a compromise. Budget their fragility. Portal HTML will change. MFA will arrive. The person whose password you stored will be transferred. Call these attended guests in the annex, never APIs, and price the breakages.

Two teardowns of the same stalled file

Objections you will hear — and what to do with them

If we admit the gap we will lose the budget

You will lose the budget later, in public, when the service is not live. Admit the gap while it is still a variation, not a newspaper.

The model can infer the missing fields

That is how you invent a labour registration. Inference is not an API. If the field is missing, the file is incomplete.

NIC is slow on purpose

NIC is often slow because the ask is illegal, vague, or unbounded. Send a one-page ask with a purpose tag and a test-tenancy request. The working-with-NIC guide is the civility manual. Contempt is not a protocol.

We will open-source an API gateway and the departments will join

They will not. Departments join when a G.O. tells them to, or when the gateway saves them work. A gateway in front of nothing is another invented API, with a nicer name.

A four-week teardown playbook

1. Week 1: extract every integration sentence from the RFP, bid and slide. Make a register.
2. Week 2: for each row, demand a URL, a letter, or a working test call. Colour the row.
3. Week 3: take invented rows out of the critical path. Write the variation.
4. Week 4: send dated asks for the permission gaps. If a fortnight passes with no owner, the row dies.

File note you can paste

Subject: Integration gap register for the agentic programme — invented APIs removed from the critical path.

The annex lists every claimed connector. Rows without a URL, letter or test tenancy are marked invented and are not deliverables. Write APIs into legal registers are out of scope unless a competent instrument is attached. Screen-scrapes, if any, will be named as guests and priced as fragile. NIC and department owners will receive dated, single-purpose asks rather than a blame minute.

This note is an internal aid. It is not legal advice.

Prcept AI would rather lose marks on a fantasy marking scheme than staff a scraper farm. If your project is blocked, show us the register. If the register is empty, the blocker is not an API. It is a story.

How to write the dated ask so it can be answered

One page. One endpoint or one letter. One purpose tag. Read or write. Test tenancy. Departmental owner. Date you need a yes, a no, or a request for detail — not a date you need production. Attach the deny-outbound sketch. Send it from the department address. File the sent copy.

If the owner answers 'not for write', celebrate. You have closed a pride gap. Move the critical path to read-plus-human-act. If they answer nothing in a fortnight, escalate once with the same page, not with a new twenty-box slide. A second slide tells them you did not read the silence.

Publish the register monthly to the CIO. Invented rows should shrink. If they grow, someone is still selling architecture. Stop paying for architecture until the register shrinks.

This article is informational field guidance for Indian public institutions, not legal, platform or procurement advice. Confirm against live platform documentation, your contract, DPDP, and counsel before you file it.

How to sequence this in a state, not a slide

“API Gaps That Block State AI Projects” is a department problem. A P4 System Integrator should name the legacy system, the officer who owns the file, and the citizen charter clock before buying “government API integration gaps”.

The model is rarely why a state AI project stalls. The stall is an API that was never published, a password that was called a connector, or a purpose nobody would log. Teardown that gap before you blame NIC. Do not invent league tables of states. Read tenders and policies. Election Model Code of Conduct can freeze a rollout. NIC is a partner, not a villain. SDC readiness is GPU, power, ops and egress — not a logo.

• Audit the legacy store first.
• Keep mutation and money as officer actions.
• Map SLAs to the citizen charter.
• Budget change requests after go-live.

Close this loop before the next CAB

Put “API Gaps That Block State AI Projects” on the next change-advisory or bid-opening agenda as a single line item with an owner. If it cannot earn a line item, it will not earn a control. The owner should be a P4 System Integrator, not “the vendor.”

Revisit the item when the model, the GeM term, the region, or the SI changes. “government API integration gaps” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.

What must be true before you file this

If “API Gaps That Block State AI Projects” is only a heading, it will not survive a file inspection. A P4 System Integrator should be able to attach one artefact that proves “government API integration gaps”: a log export, a clause, a scored row, a dated notice, or a refusal rule.

Write three dated sentences: what was decided, who owns it, and when it will be re-checked. Unsigned sentences are souvenirs. Dated sentences are controls.

• Name the owner of “government API integration gaps” inside the institution.
• Attach one artefact a stranger can open next year.
• Revisit when the model, the notice, or the SI changes.
• Do not treat a vendor slide as evidence.

What the next file must contain

“API Gaps That Block State AI Projects” earns a line in the noting only if a P4 System Integrator can attach proof of “government API integration gaps.” A heading is not proof. A vendor slide is not proof. A workshop photograph is not proof.

Write three dated sentences: what was decided, who owns it after the next posting order, and when it will be re-checked. If you cannot write the three sentences, you are not ready to buy, to sell, or to go live.

Leave unsourced percentages out of the note. DPDP is not a blanket localisation statute. The November 2025 AI governance text is guidance, not an Act. CERT-In’s 28 April 2022 directions still set specified incident and log clocks. A PAC, when lawful, lives in GFR Rule 166.

• Name the designation that owns “government API integration gaps.”
• Attach one artefact a stranger can open next year.
• Record the instrument you are actually using.
• Revisit when the model, the SI, the notice or the posting changes.