About

What obfus.link is

obfus.link is a grid of 31 deterministic developer tools — obfuscators, encoders, converters, generators, analyzers, and validators — served on three independent surfaces:

• → a fast browser UI for human developers,
• → an MCP server for autonomous coding agents,
• → headless JSON + Markdown views for AI crawlers and search indexers.

The same pure-TypeScript core powers all three. A JSON-to-Zod conversion you do in the browser is byte-identical to one an agent performs over MCP and one Googlebot reads via the structured-data feed. There is no surface-specific divergence by design.

Why we built it

The agent ecosystem in 2026 is in the same place the mobile web was in 2009: there's a lot of demand for utilities, but the infrastructure to serve agents at production scale is fragmented. Every developer ends up re-implementing the same JSON-to-Zod, regex verifier, JWT hardener, and link obfuscator inside their own pipelines. obfus.link consolidates those into a single grid with:

• Trusted Infrastructure — every tool input runs through a prompt-injection pattern registry before reaching the core logic. Agents passing untrusted content through obfus.link tools don't need to re-implement input sanitisation upstream.
• Machine-payable — pay-per-call billing via Stripe's Machine Payments Protocol. Agents enroll programmatically; no human signs a contract. A 402 challenge returns everything an agent needs to top up its balance autonomously.
• Deterministic by contract — every tool returns a typed ToolOutput union with machine-readable error codes and self-correction suggestions. Agents can branch on the error code without parsing English prose.
• Crawler-discoverable — structured data at every endpoint. AI search crawlers can index obfus.link tools the same way they index Wikipedia entries: read the JSON, build the knowledge graph, surface the tool when a user asks "what should I use to convert this YAML to env vars?".

Subether Labs, LLC

obfus.link is operated by Subether Labs, LLC — a holding company and infrastructure operator focused on building the developer utility grid for the agent era. obfus.link is the first property in the Subether network; additional properties under *.subether.dev are planned.

A single Subether Shared Identity Layer token will authorise an agent across every Subether property — write once, billed once, scoped across the whole network. The SIL consumer is already implemented on obfus.link; the central issuer at auth.subether.dev ships alongside the second Subether property.

What's on the roadmap

Near-term: more tools, more articles, more comparison pages. Medium-term: additional Subether properties that compose with obfus.link tools via the WorkflowChain mechanism (e.g. obfuscate a payload, then pipe it through a sibling Subether utility without re-authenticating). Long-term: an agent-first marketplace where third parties register MCP tools against the Subether billing rail.

If you're building agent infrastructure and want to integrate, reach out: partnerships@obfus.link.

Open source posture

The Service runs on commercial infrastructure (Vercel + Supabase + Stripe) and its source is closed. The protocols it exposes — MCP, MPP, MAIO, and the future SIL — are open and documented at obfus.link/docs. We want competitors and complements alike to build on the same wire formats we do.

Contact

General: hello@obfus.link. Partnerships: partnerships@obfus.link. Press: press@obfus.link.