How are Hydrafetch calls billed?

The spec says calls are billed in credits and charged only on success. A standard scrape is one credit, a site map is one credit, a crawl or batch is one credit per page or URL scraped, and a search is one credit plus one more per result when scrapeResults is true. Richer formats and the extraction tier cost more, and each response reports what it consumed.

What are the rate limits for the Hydrafetch API?

Hydrafetch's spec states that limits are per workspace, not per key, over a 60 second window, with the ceiling set by your plan. Every response carries RateLimit-Policy and RateLimit headers giving the quota, remaining requests, and seconds until reset, and a 429 includes Retry-After in seconds.

Can Hydrafetch crawl a site asynchronously?

Yes. POST /v1/web/crawl discovers and scrapes a whole site as one asynchronous job and returns a crawl id immediately. Poll GET /v1/web/crawl/{id} for progress and per-page results, or register a webhook and check GET /v1/web/crawl/{id}/deliveries to see each callback attempt and its last response.

How do I scrape a page to Markdown with the Hydrafetch API through Jentic?

Search Jentic for 'get a web page as markdown' to get POST /v1/web/markdown, then send the url, optionally with onlyMainContent and blockAds. To run it on your own infrastructure, install Jentic One from its GitHub repo and store your Hydrafetch API key once.

Is there a Hydrafetch MCP server?

You don't need an MCP server to give your agent Hydrafetch. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the operations you allow, discovered when needed instead of preloaded into its context.

Can I limit what my agent is allowed to do with the Hydrafetch API?

Yes. For example, allow only POST /v1/web/markdown and POST /v1/web/search, so the agent can read single pages and search but cannot start crawls or batches that spend credits per page. Your Jentic One instance logs the calls it makes.