New Delhi · India→US trade · operator & builder

Mrigank Singh

I move containers for a living and write the code that checks the paperwork. Fifteen thousand containers between India and the United States taught me that trade data can't be trusted — the same event can mean different things depending on which carrier sent it. So I built an observatory that measures it in public, whichever way the numbers fall. Then the same distrust turned out to apply to the tools AI agents call, so I built a second one for those.

01The receipts

Not claims — artifacts. Each one links to the instrument that printed it.

02Now — one company, two observatories
The company · 2021–

Intoglo — India→US freight, run on software we build ourselves

The freight forwarder and NVOCC I co-founded with Sufal Roongta and Ankur Aggarwal. Ocean freight from India to the United States, with a warehouse network at four US gateways — NY-NJ, Savannah, LA–Long Beach, Houston — moving steel, spices, textiles, chemicals, and auto parts. The operations run on systems the founding team writes itself, including production AI that reads carrier emails and shipping documents into structured operational data.

Observatory I · 2026–

Trimtabist — the independent observatory for US trade

The US Trade Ledger is what it publishes: what crossed the border, and what it actually paid. Monthly containerised imports for every US gateway and partner country, revision-tracked from US Census records; the duty assessed on every product from every origin since 2017, reconciled monthly against the US Treasury's own customs receipts — both books, assessed at entry and kept after refunds. Plus the tariff rulebook with its Federal Register citations, CBP classification rulings, and a frozen 2026 archive of own-recorded ship movements.

Twenty pre-registered studies, ruled whichever way they fell — including the nulls. A public corrections log. The whole collection pipeline is open on GitHub, so every number can be re-derived by a stranger. Free, citable, CC BY 4.0.

Observatory II · 2026–

Robin Saige — we check the tools AI agents call

The second observatory, pointed at a new object: the servers agents depend on. It probes every remote server in the official MCP registry weekly — about eleven thousand — and asks five questions in order: does it answer, what is it, can it be checked, did answers hold when re-derived against official primary sources, and what company does it keep. One verdict per server — allow, warn, or block — always with the reason printed, backed by Ed25519-signed receipts.

Findings so far, ruled whichever way they fell: the registry's live share is 55%, not the 27% a first sample said — the correction published as the story; and one gateway wears 1,312 costumes yet serves correct US duty rates. Same rules as Trimtabist: registered before running, nulls published, corrections never deleted. It is listed in the registry it measures — on its own scoreboard.

The conflict, stated rather than buried: the forwarding business is an economic interest in the subject the observatories measure. The guarantee is process — every study registered before the data is touched, public data, published method, a falsification test, a public correction log. The headline ruling on my own corridor to date is suppression — published against interest.
03Before
2021–Intoglo, co-founder & COO — India→US ocean freight, run on systems we build ourselves
2019–2021AIC ISB, CEO — took the Indian School of Business incubator zero-to-one; 25 portfolio companies in 18 months
2016–2019SenseBird, founder — drones; turning aerial data into decisions
2013–20195i Technology, founding team — smart-city infrastructure
2008–2013Engineering & business development — Motorola (GSM protocol stack), Bharat Forge, Commdel

Indian School of Business, MBA · NUS Business School, executive program · Thapar Institute, BE Electronics & Communication · Claude Certified Architect – Foundations (Anthropic, 2026)

04Contact

mrigank@intoglo.com · LinkedIn · GitHub