How Apilift works
Turn one browser workflow into a reusable interface
Show Apilift the outcome once. Your agent can reuse the resulting MCP and CLI interface without repeating the browser loop.
From outcome to interface
Map the work once. Reuse it from your agent.
- 01
Capture once
Start with a real outcome in a signed-in app and map the requests required to complete it.
- 02
Review the interface
Inspect the actions, inputs, and responses before the interface becomes reusable.
- 03
Use it from your agent
Codex, Claude Code, and other capable agents can discover the app interface and call the action they need.
- 04
Reuse the result
The next task calls the same interface instead of rediscovering the app through browser navigation.
Inside the Dashboard
Set it up from the Dashboard
Connect this app to my agent and show me the actions I can use.
Choose an app and copy the setup prompt from Apilift. Your agent handles the connection and asks only when it needs you.
Compatibility
One interface, more than one agent
The same published coverage works with Codex, Claude Code, and other agents that can use MCP or CLI tools.
Correction and drift
Correct coverage as the app changes
Extend or correct an action when a workflow changes, then reuse the revised interface without rebuilding every downstream task.
Give the work back to your agent
Apilift turns signed-in web apps into CLI and MCP interfaces your agent can call.