Basic usage
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: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 anintent_category from a fixed taxonomy. The full tree is available at:
commerce, travel, jobs, social, media, reference, and more. Each has sub-categories (e.g. commerce → product-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:What about hosted execution?
Hosted execution is available throughPOST /v1/fetch. Instead of calling the upstream site yourself, pass the registered site, endpoint, and params to Hermai: