The second batch of submitted APIs has been profiled, enriched and published — eight providers, 349 new artifacts. The first batch went live last week; submissions have been arriving at better than two a day since late July.
What landed
| Provider | What it does | Notable surface |
|---|---|---|
| Neutrino API | General-purpose API collection — data validation, telephony, geolocation, security | One of the longest-running multi-tool API products still shipping |
| WhoisFreaks | Domain and IP intelligence | Live, historical, bulk and reverse WHOIS, plus IP and ASN |
| APIFreaks | First-party API hub from JFreaks Software Solutions, Lahore | 100+ production endpoints behind one key — the deepest set in this batch |
| MirrorFly | Self-hosted CPaaS from CONTUS TECH, Chennai | Chat, messaging, HD voice, video and live streaming |
| Lacuna | AI music creation from lyrics or a plain-text style description | Operated by JOYLINK LTD |
| Spocket | Agent-native deployment and hosting | An AI coding agent ships a folder over MCP; it runs 24/7 with HTTPS and custom domains |
| Automation Preflight API | Inspects a public URL and returns bounded integration-readiness evidence | Deterministic JSON, by TinyOps Studio LLC |
| AppsMax | Russian-language SaaS for small business — requests, booking, orders | A reminder the API economy is not Anglophone |
Two API hubs from the same city, and what that means
APIFreaks and WhoisFreaks are both from Lahore, and between them they cover WHOIS, IP intelligence, and a hundred-plus general-purpose endpoints. Neutrino API does much the same job from a different continent. Three of eight providers in this batch sell the same product shape — a bundle of small, unglamorous utilities behind one key.
That shape does not get written about, but it keeps reappearing, because the demand is real and permanent. Somebody always needs to validate a phone number, resolve an IP, or check a domain’s registration, and almost nobody wants to build or maintain those three things.
The other pattern worth naming is agent-native infrastructure showing up again — Spocket exists so an AI coding agent can ship a folder over MCP and have it running with a real URL. That is the second batch in a row where the newest providers are built for an agent rather than a human reading docs.
On who wrote what
As with the first batch, every artifact carries provenance in its frontmatter: searched when we found it published by the provider, probed when we confirmed it against a live endpoint, generated or derived when we authored it from what the provider does publish. In this batch that came out to 85 searched, 23 probed, 44 generated and 33 derived.
Every provider owns their record and can correct it — write to us and we will.
More are in the queue. If yours is one of them, it is coming. If it is not, add it.