Skip to main content
An action is a single thing your agent can do on a website: read a product catalog, add an item to a cart, search for listings, submit a form. Schemas describe actions alongside endpoints, giving your agent a menu of capabilities for each site.

Action types

Reading actions from the catalog

When you call GET /v1/catalog/{domain}, the response includes both read endpoints and write actions in the same list:
Your agent reads the method, url, headers, and params fields and constructs the HTTP request. For registered endpoints that support hosted execution, you can also call POST /v1/fetch with the endpoint name and params.

Parameters

Each action lists its parameters with: For body parameters, your agent builds a JSON object. For query parameters, it appends to the URL. For path parameters, it fills in {placeholder} segments in the URL template.

Executing actions

You can execute a schema in two ways. For self execution, your agent calls the upstream site directly:
For hosted execution, call Hermai with the registered site, endpoint, and params:
The catalog gives you the recipe. Hosted fetch runs registered endpoints through Hermai.

Actions in contributed schemas

When you contribute a schema, you can include actions alongside endpoints. Write actions (add-to-cart, submit form, login) are easiest to capture with hermai intercept, which launches a browser, lets you perform the action in the UI, and records the underlying XHR request for replay.