It works in context.
The agent uses the current tab, its live state, and the human-facing website—not a disconnected copy of the product.
Agent access engineering for existing websites
Entruic turns the workflows your website already carries into structured, permissioned actions for AI agents.
Turn website workflows
into agent actions.
Use the live browser when context matters. Use API or MCP when system access is stronger. Verify the business outcome either way.
Contact usFor people
Start a workflow review
Existing site · Customer enquiry↗
Workflow map Action interface Evidence plan
For agents · WebMCP
Call an action
- action
- start_workflow_review
- input
- { website, workflow }
- returns
- brief + next step
- permission
- requires confirmation
WebMCP is the live website’s action layer.
WebMCP lets an open page expose a named action to an agent: its inputs, permission boundary, and expected result. The action stays attached to the current browser tab. It is an emerging browser standard, used where live page context and user control matter—not as a replacement for every system.
It replaces guesswork.
Instead of inferring buttons and fields, the agent sees a named action with defined parameters and a structured result.
It is not backend MCP.
WebMCP is for browser workflows. APIs or MCP support actions that belong in the backend or must run outside a tab.
Start with the work that has to be right.
Agent access is worth engineering when the work depends on live context, real business rules, and a result that can be checked.
Discovery that ends in a decision
Search, eligibility, matching, availability, and quoting—where a useful answer depends on live business context.
A request that needs a valid hand-off
Enquiries, bookings, applications, and support triage—where intent has to reach the right team or system without being distorted.
A consequential action
Checkout, account changes, submissions, and confirmations—where permissions, approval, and an auditable outcome matter.
A focused path from workflow to proof.
Every engagement begins with the workflow, its permissions, and the business state that matters—before a protocol or a tool is chosen.
Discover
Workflow map + success condition.
We map customer intent, the system of record, business rules, approvals, and the state that proves the work is complete.
Engineer
A testable agent interface.
WebMCP is used where browser context matters; APIs or MCP are used where the backend is the stronger surface. The agent gets one clear path.
Prove
Evidence for a safe release.
We exercise failure paths and confirm the authoritative business state—not just an agent reply—before the workflow is treated as dependable.
5× more verified task completion.
In a native WebMCP commerce benchmark, both conditions used the same tools and backend. Only procedure, recovery, and outcome verification changed.
verified completion
20% → 100%
failure scenarios recovered
Inventory, price, lost response & compound fault
business invariants passed
On the compound-failure checkout
50 deterministic native WebMCP runs in Chrome 151; 25 runs per condition across five checkout scenarios. This is reproducible technical evidence, not customer production performance.
Contact the founder.
Bring one workflow. We will find its real path to action.
For a workflow review, a technical question, or a partnership, write to Henry directly. Start with the work as it happens today and what must never go wrong.
Direct emailhenry@entruic.com