The connector compiler: agents that write integrations to any system in 47 seconds
MetaSpark agents read the docs, infer the resource graph, draft OAuth and webhook handlers, and ship the connector live. How it works and why the median is sub-minute.
The fastest-growing line item in every SaaS roadmap is "integration with X." Customers ask for it. The competition has it. Engineering doesn't have time for it. Marketplaces partially solve it but mostly push the cost to a third party. The whole loop is broken because each integration is treated as a one-off project.
We took the opposite bet: the connector itself is a thing an agent should write. On demand. Per customer. Per system. Without a roadmap.
What the connector compiler does
When you point MetaSpark at a system we don't natively support — your homegrown CRM, a partner's REST endpoint, an internal portal — an agent runs a four-step authoring loop:
- Reads the system's documentation, OpenAPI spec, or whatever surface is reachable.
- Infers the resource graph: what entities exist, how they relate, which fields matter, where webhooks live.
- Drafts the OAuth handler and webhook listener in a sandboxed runtime.
- Runs a verification pass — does the connector list, read, and write the resources it claimed?
If it passes, the connector goes live in your tenant. If it doesn't, the agent tells you which step failed and why, in plain language. The median end-to-end time is 47 seconds. The slowest we've seen is just over two minutes on a particularly hostile internal portal.
Why this works now and didn't five years ago
Three things changed:
- LLMs can read API documentation and write working adapters in one pass — a year ago that wasn't true; today it is.
- Tenant-isolated execution is cheap. We can hand an agent a sandbox per customer, with credentials scoped to that customer, without operational overhead.
- Verification is fast. We can prove a connector works by exercising it against the customer's actual data in seconds, not days.
What you should ask us on a call
Name the system nobody integrates with — the internal Rails app, the old Lotus thing, the partner endpoint that hasn't had a client library shipped this decade. We will have an agent author the connector while we're talking. We time it.