Most websites weren’t made for AI agents. Aperture opens a doorway, so they can use those sites without starting from scratch every time.
Already using an agent?
The web wasn’t built for agents. Millions of applications still depend on forms, buttons, and interfaces designed for people. Agents can navigate them, but every action takes time, and it’s often hard to tell whether something actually worked. Aperture gives agents a better way in.
01
An agent opens a website and learns how it works. No API or custom integration required for supported interfaces.
02
Aperture turns discovered actions into reusable, structured tools that agents can call directly.
03
Agents run those tools within their permissions, without repeating the entire exploration.
04
Aperture checks the result, records what changed, and helps agents recover when something goes wrong.
Fresh agent sessions on the same job, each graded from the system’s own records.
2.3×
faster
Remove two residents and their devices from a gate-access admin app. Aperture: median 70 s, 18 tool calls, $0.23. A browser agent: 158 s, 33 calls, $0.46. Both 5 of 5 correct.
Claude Code
Playwright MCP8/10
chose it
Ten fresh sessions had a browser and Aperture connected, and the prompt never named either. 8 used only Aperture, 2 used both, none used only the browser. All 10 correct; none pressed Send without being asked.
Claude CodePlaywright MCP20/20
on WordPress
Browser only against Aperture only, on Sonnet and Haiku. Every run correct on both sides. Deleting a user: 38 s against 47 s, 8 calls against 14, about 60% cheaper. Trashing two posts: even (45 s against 42 s).
WordPress
Sonnet · HaikuPlaywright MCPOur own test setup, small samples, every run reported, including the ones where it didn’t win.
No need to rebuild the applications you already use.
Discover a workflow once. Run it again without starting from scratch.
Agents act within delegated permissions and escalate when necessary.
Every consequential action gets a result you can inspect, including failures and incomplete recovery.
Aperture connects through MCP. No new agent or workspace required.
and any other MCP client.
Connect to the Aperture MCP server and run a safe first check. 1. Add it as an MCP server named "aperture" at https://calm-steel-d31rh.run.mcp-use.com/mcp. Use your client's own MCP setup. In Claude Code: claude mcp add --transport http "aperture" 'https://calm-steel-d31rh.run.mcp-use.com/mcp' 2. If it asks you to sign in, use the sign-in flow it provides. Never ask me to paste a password or key into this chat. 3. List the tools it exposes. For each one, tell me what it does and whether it only reads or can change data. 4. Make one read-only call and show me the result. Change nothing. Stop and ask me before anything that writes, deletes, or sends.
Aperture turns websites into reusable tools that AI agents can discover and execute through MCP.
Anyone building AI agents that need to work with websites, especially legacy systems without usable APIs.
No. Aperture explores the interface and learns how to interact with it through a browser.
Instead of reasoning through the same clicks every time, Aperture compiles workflows into reusable tools, with execution checks and recovery where supported.
Aperture is designed to support a wide range of interfaces. Compatibility depends on the site’s structure, permissions, and available functionality.
Aperture can detect when a compiled workflow no longer matches the interface. Its self-healing engine is being developed to repair and revalidate those workflows.
That’s the goal. Agents operate within delegated permissions, escalating only when necessary.
When the underlying application supports a recovery path. Aperture distinguishes recoverable changes from irreversible ones.
Any compatible MCP client, including Claude, Codex, and Cursor.
Not every application has an API. Not every business will build an MCP server.
Aperture bridges that gap.