Knowledge BaseBindings

HTTP Bindings

HTTP binding is the request-driven execution family in MergeSafe. It is the right fit when the browser runtime can call a stable route or endpoint that already represents the real product action.

On this page

What HTTP binding is When HTTP is the right choice What HTTP binding assumes Common caveats

What HTTP binding is

An HTTP binding connects the tool to a browser-side fetch path. MergeSafe treats that binding as an explicit execution strategy rather than a generic integration placeholder.

The runtime performs the request, applies mapping, and validates input and output against the tool schemas during execution.

When HTTP is the right choice

The underlying product action already exists behind a route or API.
The browser runtime can reach that route in a way that fits the product auth and session model.
The tool behavior is naturally request and response oriented.

What HTTP binding assumes

The runtime has the browser context needed to make the request.
The route shape is stable enough that schema and mapping can stay aligned.
Authentication and origin expectations are already understood by the team wiring the tool.

Common caveats

Browser-origin networking constraints can block or reshape requests.
Auth and session assumptions can fail even when the route works elsewhere.
Schema mismatch or response-shape drift can turn a valid route into a failing tool execution.
HTTP should describe a controlled product action, not a loose scrape-or-guess strategy.

Related docs

Creating a Tool

Understand the manual tool authoring flow, schema definition, binding choice, and how to think about drafts before publish.

Hook Bindings

Use Hook bindings when execution should happen through an explicit product-side callable path inside the runtime context.

Latest Pack Fetch and Runtime Delivery

Follow the active-pointer and artifact flow that delivers the live pack into the runtime and selectively exposes tools through WebMCP.

Use the editorial lane when the topic benefits from tradeoffs, framing, or a narrative explanation beyond the reference flow.

HTTP vs Hook Bindings: When to Use Each

A grounded guide to choosing HTTP or Hook bindings based on where the real action lives, what context it needs, and how much of the execution path you already own.

Creating a Tool

Hook Bindings