Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.
All 92 tools →
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/hydrafetch-com:hydrafetch-com-feedback-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: Hydrafetch Feedback API
description: 'Hydrafetch is a web data API for developers and agents. Send a URL and get back clean Markdown, the page''s own structured data, schema-shaped JSON, links, or a summary, with the navigation, banners and boilerplate stripped out. Scrape one page, crawl a whole site, run a search, or extract to a schema, all through one API with one response shape. Every call costs one credit a page whatever it took to fetch, and failures are never billed.
Point us at a whole site and get every page. Ask a question and get answers with per-field
confidence and the passage each value came from. You describe the outcome you want — the
pipeline decides how to get it.
## Authentication
Every request is authenticated with your API key in the `X-API-Key` header. Keys are scoped to a
workspace and carry its credit balance.
## Credits
Calls are billed in credits and charged only on success. A standard scrape is one credit; richer
formats and the extraction tier cost more. Each response reports what it consumed.
## Conventions
All timestamps are UTC ISO 8601. Long-running jobs (crawl, batch) return a job id you poll, or a
webhook you register.
## Errors
Every failure returns the same shape, whatever the status:
```json
{ "success": false, "error": { "code": "INSUFFICIENT_CREDITS", "message": "Insufficient credits" },
"meta": { "requestId": "019e8a3c-9f0b-7c12-88ab-1d2e3f4a5b6c" } }
```
Branch on `error.code`, which is stable. `error.message` is written for a person and may be
reworded without notice. Validation failures add `error.details`. Quote `meta.requestId` when
asking us about a specific failure. Every operation documents the codes it can return.
## Rate limits
Limits are per workspace, not per key, over a 60 second window, and the ceiling comes from your
plan. Every response carries the IETF RateLimit header fields so you can self-throttle rather
than discovering the limit by hitting it:
```http
RateLimit-Policy: "workspace";q=600;w=60
RateLimit: "workspace";r=599;t=42
```
`q` is the quota, `w` the window in seconds, `r` the requests remaining and `t` the seconds until
the window resets. A 429 also carries `Retry-After` in seconds; wait that long rather than
retrying immediately. The older `X-RateLimit-Limit`, `X-RateLimit-Remaining` and
`X-RateLimit-Reset` headers are still sent and mean the same thing.
## Versioning and deprecation
The version is in the path: every endpoint on this API lives under `/v1/`. Within a version we
only make additive changes — new endpoints, new optional parameters, new fields in a response.
Adding a field to a response is not a breaking change, so parse defensively and ignore what you
do not recognise.
Anything that would break an existing integration ships under a new version path instead. When an
endpoint or a version is retired, the responses say so before it stops working:
```http
Deprecation: @1780272000
Sunset: Sat, 01 May 2027 00:00:00 GMT
Link: ; rel="deprecation"
```
`Deprecation` (RFC 9745) marks when the endpoint became deprecated, `Sunset` (RFC 8594) when it
stops responding, and the `deprecation` link relation points at what to move to. Nothing on this
API is deprecated today, so you will not see these headers yet. Watch for them rather than for an
announcement: the headers are the notice, and the linked changelog carries what to move to.'
version: '1.0'
contact:
name: Hydrafetch
url: https://hydrafetch.com
email: support@hydrafetch.com
servers:
- url: https://api.hydrafetch.com
description: Production
security:
- apiKey: []
tags:
- name: Feedback
paths:
/v1/web/feedback:
post:
description: Tell us whether a result was accurate. Rate a request by its id (the X-Request-Id header) or by the URL it read. Rating the same request again replaces the earlier rating. Free.
operationId: rateResult
parameters: []
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/ResultFeedbackDto'
responses:
'200':
description: ''
content:
application/json:
schema:
$ref: '#/components/schemas/ResultFeedbackResponseDto'
'400':
description: The request body or query failed validation.
content:
application/json:
schema:
$ref: '#/components/schemas/WebError'
example:
success: false
error:
code: VALIDATION_ERROR
message: url must be a valid URL
meta:
requestId: 019e8a3c-9f0b-7c12-88ab-1d2e3f4a5b6c
'401':
description: The X-API-Key header is missing, malformed, or names a key that no longer exists.
content:
application/json:
schema:
$ref: '#/components/schemas/WebError'
example:
success: false
error:
code: UNAUTHORIZED
message: 'Missing X-API-Key header. Agents: https://hydrafetch.com/auth.md'
meta:
requestId: 019e8a3c-9f0b-7c12-88ab-1d2e3f4a5b6c
'402':
description: The workspace has no credits left for this request. Nothing was charged and nothing was fetched.
content:
application/json:
schema:
$ref: '#/components/schemas/WebError'
example:
success: false
error:
code: INSUFFICIENT_CREDITS
message: Insufficient credits
meta:
requestId: 019e8a3c-9f0b-7c12-88ab-1d2e3f4a5b6c
'403':
description: The key is valid but the workspace may not make this request.
content:
application/json:
schema:
$ref: '#/components/schemas/WebError'
example:
success: false
error:
code: WORKSPACE_BANNED
message: This workspace has been suspended and cannot make API requests.
meta:
requestId: 019e8a3c-9f0b-7c12-88ab-1d2e3f4a5b6c
'404':
description: No such job, or the id belongs to another workspace.
content:
application/json:
schema:
$ref: '#/components/schemas/WebError'
example:
success: false
error:
code: NOT_FOUND
message: Job not found
meta:
requestId: 019e8a3c-9f0b-7c12-88ab-1d2e3f4a5b6c
'422':
description: The target site did not respond, or we could not read that page. This is a fact about that URL rather than a fault on our side, and retrying it will not change the answer. When details.retryAfterSeconds is present, asking again before then returns this same answer. Nothing was charged.
content:
application/json:
schema:
$ref: '#/components/schemas/WebError'
example:
success: false
error:
code: UPSTREAM_UNREACHABLE
message: The origin did not respond to any attempt we made.
meta:
requestId: 019e8a3c-9f0b-7c12-88ab-1d2e3f4a5b6c
'429':
description: The workspace exceeded its per-minute request limit. Read the RateLimit headers, or Retry-After on this response, and retry after the window resets.
headers:
Retry-After:
description: Seconds to wait before retrying. Prefer this over a fixed backoff.
schema:
type: integer
example: 17
RateLimit:
description: Requests remaining (r) and seconds until the window resets (t).
schema:
type: string
example: '"workspace";r=0;t=17'
RateLimit-Policy:
description: The quota (q) for your plan and the window it applies over (w), in seconds.
schema:
type: string
example: '"workspace";q=600;w=60'
content:
application/json:
schema:
$ref: '#/components/schemas/WebError'
example:
success: false
error:
code: TOO_MANY_REQUESTS
message: Rate limit exceeded for this workspace and plan.
meta:
requestId: 019e8a3c-9f0b-7c12-88ab-1d2e3f4a5b6c
'500':
description: Unexpected server error. Nothing was charged.
content:
application/json:
schema:
$ref: '#/components/schemas/WebError'
example:
success: false
error:
code: INTERNAL_SERVER_ERROR
message: Internal server error
meta:
requestId: 019e8a3c-9f0b-7c12-88ab-1d2e3f4a5b6c
'503':
description: A dependency needed for the requested formats is unavailable. Safe to retry.
content:
application/json:
schema:
$ref: '#/components/schemas/WebError'
example:
success: false
error:
code: SERVICE_UNAVAILABLE
message: The summary and json formats are not available.
meta:
requestId: 019e8a3c-9f0b-7c12-88ab-1d2e3f4a5b6c
summary: Rate a result
tags:
- Feedback
components:
schemas:
ResultFeedbackDto:
type: object
properties:
requestId:
type: string
description: 'The request being rated: the X-Request-Id response header, or usage.requestId from an MCP tool. Give this or url.'
format: uuid
url:
type: string
description: The URL that was read, when the request id is not to hand. Rates the latest request for it in the last 24 hours.
rating:
type: string
enum:
- good
- bad
description: Whether the result was accurate.
reasons:
type: array
description: What was wrong, for a bad rating.
items:
type: string
enum:
- missing_content
- wrong_content
- blocked
- slow
- formatting
- other
note:
type: string
description: More detail, in your own words.
maxLength: 500
required:
- rating
WebErrorBody:
type: object
required:
- code
- message
properties:
code:
type: string
enum:
- VALIDATION_ERROR
- INVALID_INPUT
- UNAUTHORIZED
- INSUFFICIENT_CREDITS
- FORBIDDEN
- WORKSPACE_BANNED
- NOT_FOUND
- TOO_MANY_REQUESTS
- UPSTREAM_UNREACHABLE
- SERVICE_UNAVAILABLE
- INTERNAL_SERVER_ERROR
description: Stable, machine-readable reason. Branch on this rather than on the message, which may be reworded.
example: INSUFFICIENT_CREDITS
message:
type: string
description: Human-readable explanation. Safe to show a user, not to parse.
example: Insufficient credits
details:
type: object
additionalProperties: true
description: Optional machine-readable context, present on validation failures.
ResultFeedbackResponseDto:
type: object
properties:
data:
$ref: '#/components/schemas/ResultFeedbackDataDto'
required:
- data
ResultFeedbackDataDto:
type: object
properties:
id:
type: string
format: uuid
requestId:
type: string
format: uuid
rating:
type: string
enum:
- good
- bad
required:
- id
- requestId
- rating
WebErrorMeta:
type: object
properties:
requestId:
type: string
description: Quote this when contacting support about a specific failure.
example: 019e8a3c-9f0b-7c12-88ab-1d2e3f4a5b6c
WebError:
type: object
required:
- success
- error
- meta
description: Every failure on this API returns this shape, whatever the status. Successful responses never carry it.
properties:
success:
type: boolean
enum:
- false
example: false
error:
$ref: '#/components/schemas/WebErrorBody'
meta:
$ref: '#/components/schemas/WebErrorMeta'
securitySchemes:
apiKey:
type: apiKey
in: header
name: X-API-Key