Makes me think of a hypothetical openapi fuse filesystem, thing.

We built an open API gateway for AI agents. The core idea: map the entire internet's APIs into a virtual filesystem, so agents can discover and call them using 5 Unix commands they already understand (ls, cat, grep, write, pipe).

The problem we're solving: today, if your agent needs to call 10 different APIs, it needs 10 different auth flows, 10 sets of API keys floating around in plaintext, and 10 OpenAPI specs eating up your context window. MCP helps, but loading tool schemas still burns thousands of tokens per service.

With nkmc, the agent authenticates once (single JWT), and the gateway handles per-service credentials through a 3-layer encrypted vault — the agent never sees raw API keys. API specs are replaced by minimal skill.md files (~90% fewer tokens than OpenAPI).

For API providers: register your API in 3 minutes via DNS TXT verification. No SDK integration needed.

40+ services already registered (GitHub, Stripe, OpenAI, Cloudflare, Slack, Notion, etc.). Open source, built on Cloudflare Workers.