Which GeM Category Fits an AI Agent Platform?

The most expensive sentence in an AI procurement file is we bought it under the category we used last time. GeM categories, product specifications and service SLAs are living objects. They are created, split, renamed and retired. A code that fitted a perpetual on-prem licence in 2023 may now sit beside a SaaS listing that phones a foreign model, or may not exist.

This guide does not print a category number. If another article or a salesperson gives you one, treat it as a hint to search, not as a citation. The official storefront is gem.gov.in. The official buyer help is on the same hostname. Your file should contain a dated search note, not a memory.

The decision you actually owe is prior to the code: are you buying goods, services, or a mix that the portal cannot honestly hold in one cart? An on-prem agent platform is often a mix — software, implementation, support, and sometimes metal. How you split that mix is a GFR and audit decision. The category search comes after the split.

Goods versus services, before the dropdown

Goods language fits when you are buying a licence or a boxed appliance you will accept, stock-account if required, and run. A perpetual or term licence for software that is delivered as media or a key, with a defined version, often looks like goods to a store officer. A rackmount appliance with the stack preloaded is even closer to goods.

Services language fits when you are buying outcomes, people, or a continuing right to a hosted capability: implementation, managed operation, training, or a subscription whose substance is someone else's uptime. Many platforms on the market are services even when the invoice says licence. On-prem agentic AI with a no-outbound claim is usually closer to software plus implementation services than to a public SaaS. If the vendor's only GeM listing is a cloud subscription with a public login, that listing is the wrong object, even if the category title contains the letters A and I.

When in doubt, split the cart the way you will accept the work. Licence or appliance on one document. Implementation and AMC on another, or as a clearly described service line. Mixing them in a category that cannot express isolation requirements is how you buy a chatbot and receive a login.

Family first, code second. The code you used for antivirus is not a family.

What you think you are buying	Questions that decide the family	Likely portal posture (confirm live)
On-prem licence + your staff operate	Is there a version, media, acceptance test?	Software goods / licence category if one exists and fits
On-prem but vendor operates for 3 years	Whose uptime? Whose people?	Managed service, not a one-time good
Hosted model, India region	Is there outbound? Who is the processor?	SaaS / cloud service listing — different risk, different ATC
Implementation of your chosen stack	Are you paying for hours and a runbook?	IT / professional services
GPU node	Is the SKU listed and in stock?	Hardware goods — do not hide it inside software
A mix you cannot split	Can a custom bid describe the whole?	Custom bid or a bid with ATC — not a blind direct purchase

How to search so the file survives

On the week of the indent, log into GeM as the buyer. Search the words you would defend: on-premises software, software licence, artificial intelligence, machine learning, IT services, managed services, data centre software. Save the result pages. Categories will overlap. Overlap is normal.

Open the specification template for each candidate. If the mandatory parameters cannot express isolation, licence type, data residency of logs, or support without a tunnel, the category will fight you. You may still use it with additional terms if the portal and your manual allow. Or you may need a custom bid. Write why. Call GeM facilitation or your ministry's GeM cell if the search is ambiguous. Put their written guidance in the file. A phone memory is not guidance. Do not let the vendor choose the category alone. They will choose the listing they already have.

Rule 149 sits on availability, not on the word AI

GFR 2017 Rule 149 is the reason this question is not academic. In substance, goods and services that are available on GeM are to be procured through GeM by ministries and departments, subject to the Rule's own conditions and to later DoE instructions. Read the current text on doe.gov.in rather than a training-deck paraphrase. Availability is the hinge. If a fitting good or service is available, you generally should not wander off to a private email RFQ because the category felt awkward.

If nothing available matches the object — on-prem, isolatable agent platform with the annexure you need — document the search and take the path your GFR and manual allow (custom bid on GeM, or another route if lawfully open). I could not find a perfect dropdown is not, by itself, a reason to ignore GeM if a reasonable listing exists. No listing can carry our mandatory isolation rows is a reason to write a custom bid or to split the buy. Thresholds, direct purchase limits and bid tools on GeM change. Do not copy a 2017 rupee figure into a 2026 file without checking the live Rule, OMs and portal.

1. Write the object: goods, services, or split.
2. Search live GeM; file dated screenshots.
3. Read specification templates for isolation fitness.
4. Decide catalogue / direct, bid, or custom bid.
5. Write the why in five lines for the next auditor.
6. Re-search if the file sleeps more than a few weeks.

Objections you will hear — and what to do with them

These are the lines that stall the file. Answer them in the room, then put the answer in the note. A spoken answer without paper will be forgotten by the next officer.

Just give us the category code you use.

Any code printed here will rot. Search the portal. If we listed a product, that listing is ours, not your determination that the category fits your isolation rows. Do your search note.

Services are harder to buy than products, so we will force a goods code.

Forcing a goods code onto a managed service is how you fail inspection and still have a processor you did not contract. Buy the object. GeM now treats services as a first-class path — see the companion piece in this cluster — but confirm live.

Our last antivirus buy is a good enough precedent.

Antivirus was a well-trodden goods category with known AMC patterns. An agent platform that may train, may phone home, and may hold personal data is not antivirus. Precedent is useful for process, not for category id.

A two-day category note

1. Morning 1: write the object and the split (metal / licence / implementation / operate).
2. Afternoon 1: live search, save templates, mark isolation fit.
3. Morning 2: GeM cell query if ambiguous; draft five-line why.
4. Afternoon 2: choose catalogue, bid or custom bid; attach the air-gap annexure only where the form can evaluate it.

How this shows up in the file

The category note is five lines and screenshots: what we are buying; what we searched on which date; why the chosen family fits; why others do not; what we will do if the listing cannot hold our mandatory rows. That note is the procurement's memory. Without it, the next officer will copy the code and buy the wrong tenant.

A search note template you can paste

On [date] at [time], buyer [name] searched GeM for: [terms]. Candidate categories / listings: [A, B, C] with specification templates reviewed. Listing A is a hosted chatbot and cannot carry isolation parameters [evidence]. Listing B is a generic software licence whose mandatory parameters are silent on deployment mode [evidence]. Listing C is a service template that can carry an ATC. Conclusion: the object (on-prem isolatable agent platform with media install) is not available as a faithful catalogue SKU; we will use [custom bid / split cart] because [one sentence]. Screenshots at [file numbers].

That paragraph is the entire intellectual content of the category decision. Everything else is decoration. Write it every time. Re-write it if the file sleeps.

When a listing appears mid-file

Markets move. A listing that did not exist in April may exist in July. If you are still pre-tender, re-search. If you are mid-bid, take counsel before you abandon a custom bid for a new cart — changing tools mid-stream is how complaints are born. If you already awarded, the new listing is a fact for the next cycle, not a reason to break this one without cause.

Teaching the committee the family first

Committees like codes because codes feel official. Spend three minutes on family — goods, services, split — before anyone opens the portal. Once they have said this is a licence plus an implementation service, the search has a shape. If they start on the portal, they will pick the first tile that contains AI. Invite the SDC owner to that three minutes. They can say whether they will accept a goods appliance or only a service install. Their acceptance is the family.

This article is informational field guidance, not legal or procurement advice. Confirm against the current Gazette, GFR, GeM portal terms and your counsel before you file it.