Skip to main content
The catalog is the agent-facing lookup endpoint. Give it a domain, get back every callable endpoint and action that the community has discovered for that site. Use the catalog when you want endpoint recipes. Use hosted fetch when you want Hermai to execute a registered endpoint for you.

Basic usage

Response:
Each endpoint includes what your agent needs to construct a valid HTTP request: URL template, method, headers, and parameters.

Intent

Every catalog request must include an intent: a natural-language description of why your caller needs this schema. Pass it as a query parameter or header:
Requirements: at least 20 characters, at least 5 distinct words. Requests without a valid intent get a 400 error (INTENT_REQUIRED, INTENT_TOO_SHORT, or INTENT_TOO_FEW_WORDS). Why we require it: intent data drives which schemas we prioritize for verification, helps match agents to the right endpoints, and acts as a lightweight anti-spam gate.

Intent taxonomy

Every schema in the registry declares an intent_category from a fixed taxonomy. The full tree is available at:
Top-level categories include: commerce, travel, jobs, social, media, reference, and more. Each has sub-categories (e.g. commerceproduct-detail, product-search, reviews).

Rate limits

Anonymous requests are rate-limited by IP. Registered requests are rate-limited by user account or workspace. Free accounts also have a 20 requests/minute burst cap (60 on Starter, 100 on Pro). Exceeding a limit returns 429 Too Many Requests. See credits and usage for the full plan table.

Browsing the registry

Beyond the catalog lookup, you can browse the full registry:
These browse endpoints do not require an intent. They are designed for exploration, not runtime calls.

What about hosted execution?

Hosted execution is available through POST /v1/fetch. Instead of calling the upstream site yourself, pass the registered site, endpoint, and params to Hermai:
The catalog gives you the recipe. Hosted fetch runs the registered endpoint and returns the result.