Every order in retail grocery starts with a barcode. gtinfetch answers it — any barcode, one call, the page under it. 84 million Global Trade Item Numbers (GTINs), the only agentic read.
The seven AI (artificial intelligence) systems the world's buyers talk to. Every one of them reads gtinfetch.
Every agent that touches a product meets a barcode first — on a shelf, in a basket, in a planogram — and has to know what it is before it can buy, list, price or place it. gtinfetch is where that question is answered: 84 million GTINs on the record, each with the page it was read from, confirmed where two pages agree, and read where the product is sold. The hubs, the agents and the payments stand behind that answer. The barcode is the way in.
Counts are read from the record at request time — the same counts an agent gets from the door.
An agent asks with a barcode. It gets one signed answer: the product and its maker, the markets it is confirmed in, whether it is on sale or recalled, the page each fact was read from, and a claim status that says how far the answer has been verified. Where the resolver does not know, it says “unknown”.
The three checks a buying agent makes before an order, answered in the same call.
Read from the public approved-product lists that retailers and state programs publish, dated to the list, with the file as the source.
Read from the regulators’ own registers — RappelConso in France, the FDA in the USA, Health Canada, the Office for Product Safety and Standards in the UK. The notice, the date, the agency and the lot.
Ask with a market and the answer carries a light: green, cleared; yellow, cleared with a condition; red, not cleared; none, no record. Twenty-five markets, each on its own rules.
Rules differ by jurisdiction; the light is information, not a recommendation — the regulator in the agent’s own market has the last word.
An agent finds gtinfetch on the Official Model Context Protocol (MCP) Registry and the Microsoft Azure API Center, connects over the stock client paths of Amazon, Microsoft and Google, and calls one tool. The only agentic read of its kind: 84.2M barcodes, x402 at the door — USDC and Open USD, both in the wallet GSC takes.
| The tool | fetch_gtin — one barcode in; the who, what, where out; add a market for the light |
| The door | gtinfetch.ai/mcp — Model Context Protocol, served from the edge nearest the agent |
| The card | gtinfetch.ai/.well-known/agent.json — the Agent-to-Agent (A2A) card |
| The listings | Official MCP Registry · ai.gtinfetch/gtinfetch — the only GTIN resolver on the registry · Microsoft Azure API Center |
| The clouds | Amazon · Microsoft · Google — grade A on the stock, unpatched client paths of all three |
| The wallet | x402 · USDC and Open USD — machine payment inside the call |
VECTOR is what a maker gets on GSC: Verified · Exchange · Confirmed · Traffic · Open-to-place · Retail media. Confirmed is gtinfetch. Every agent resolves the barcode first — before it verifies the maker, enters a hub or pays — so the resolver is where every agent arrives, and the answers point to where it trades.
| The question | The door | What it answers |
|---|---|---|
| What is this product? | gtinfetch.ai | the resolver — any barcode, one call, the page under it |
| Who am I dealing with? | A2A-Passport.ai | the registry — hundreds of thousands of makers and thousands of banners, verified |
| Where do I trade? | The four hubs | A2A-Grocery.ai · A2A-Retailmedia.ai · A2A-Cosmetics.ai · A2A-Peptides.ai — 20 markets, one record |
| How do I pay? | gsc-x402.ai | order and payment settled together, agent to agent, a receipt on chain |
An agent that resolves a barcode in one call burns a fraction of the compute of the search it replaces. gtinfetch runs at the edge on Cloudflare, which matches 100% of its power with renewable energy. Eighty-four million answers, one call each.
What is gtinfetch?
gtinfetch is GSC's Global Trade Item Number (GTIN) fact checker for AI agents: any barcode, one call, the page under it. 84 million GTINs, retail grocery, 25 markets.
What does an agent get back?
One signed answer: the product and its maker, the markets it is confirmed in, whether it is on sale or recalled, the page each fact was read from, and a claim status. Where gtinfetch does not know, it says “unknown”.
Why does GSC lead with the barcode?
Every agent that touches a product meets a barcode first. GSC answers it, and the hubs, the agents and the payments stand behind the answer. The barcode is the way in.
What does “confirmed” mean on gtinfetch?
Two or more independent pages — a brand page, a retailer page, a public register — agree on what the barcode is. Two million GTINs are confirmed today; the count is read live.
Can gtinfetch tell an agent whether a product can be sold in a market?
Yes. Ask with a market and the answer carries a compliance light — green, yellow, red or none — read for that market on its own rules. The light is information, not a recommendation.
Where does an agent find gtinfetch?
On the Official Model Context Protocol (MCP) Registry as ai.gtinfetch/gtinfetch, on the Microsoft Azure API Center, and at the door, gtinfetch.ai/mcp. Stock Amazon, Microsoft and Google clients attach without an adapter.
How does an agent pay?
At the door, on x402 — USDC and Open USD, both in the wallet GSC takes. Machine payment inside the call.
Where do gtinfetch's answers lead?
To VECTOR: the maker verified on A2A-Passport.ai, the trade on the four GSC hubs, the payment on gsc-x402.ai. gtinfetch is the C in VECTOR.
Does gtinfetch guess?
No. Right answer or no answer. Every field carries its source page, every answer is signed, and an agent can verify it without calling GSC.
One tool, 84 million answers, 25 markets. A lab, an agent builder, a retailer’s technology team, a maker: tell us your agent and your barcodes, and a person answers.
GSC is a Microsoft AI Cloud Partner, headquartered in Vancouver, Canada, with sales offices in London, UK. Where AI agents buy grocery: GSC-EM.com.
GreenCore Solutions Corp. (GSC) built VECTOR, the AI Agent Hub for Agentic Commerce.