fetcher-cloud
The ghost that fetches what your AI can't. 20 pay-per-call HTTP tools for AI agents: render & screenshot JavaScript pages, extract clean Markdown, unfurl links, parse RSS feeds, resolve redirects, and look up domains, DNS, SSL, WHOIS and more. Works with any agent — Claude, ChatGPT, Gemini, Grok, Perplexity — via x402 micropayments in USDC on Base. No sign-up, no API keys.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles fetcher-cloud the way a machine reads it — 27 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — fetcher-cloud scores 36.5/100 (thin), with a separate agent-readiness read of 27/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-10-31 · rubric v0.25.0
Put this on your own site. The badge is drawn live from fetcher-cloud's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/fetcher-cloud/"
title="fetcher-cloud on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/fetcher-cloud.svg"
alt="fetcher-cloud Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/fetcher-cloud/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/fetcher-cloud/"
title="fetcher-cloud on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/fetcher-cloud/card.svg"
alt="fetcher-cloud Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile fetcher-cloud
Each block below is one kind of artifact we hold for fetcher-cloud. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 18
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
fetcher-cloud Diff API
The Diff API from fetcher-cloud — 1 operation(s) for diff.
fetcher-cloud Dns API
The Dns API from fetcher-cloud — 1 operation(s) for dns.
fetcher-cloud Domain API
The Domain API from fetcher-cloud — 2 operation(s) for domain.
fetcher-cloud Extract API
The Extract API from fetcher-cloud — 1 operation(s) for extract.
fetcher-cloud Favicon API
The Favicon API from fetcher-cloud — 1 operation(s) for favicon.
fetcher-cloud Feed API
The Feed API from fetcher-cloud — 1 operation(s) for feed.
fetcher-cloud Guard API
The Guard API from fetcher-cloud — 2 operation(s) for guard.
fetcher-cloud Headers API
The Headers API from fetcher-cloud — 1 operation(s) for headers.
fetcher-cloud Oembed API
The Oembed API from fetcher-cloud — 1 operation(s) for oembed.
fetcher-cloud Pdf Text API
The Pdf Text API from fetcher-cloud — 1 operation(s) for pdf text.
fetcher-cloud Qr API
The Qr API from fetcher-cloud — 1 operation(s) for qr.
fetcher-cloud Render API
The Render API from fetcher-cloud — 1 operation(s) for render.
fetcher-cloud Resolve API
The Resolve API from fetcher-cloud — 1 operation(s) for resolve.
fetcher-cloud Robots API
The Robots API from fetcher-cloud — 1 operation(s) for robots.
fetcher-cloud Screenshot API
The Screenshot API from fetcher-cloud — 1 operation(s) for screenshot.
fetcher-cloud Ssl API
The Ssl API from fetcher-cloud — 1 operation(s) for ssl.
fetcher-cloud Unfurl API
The Unfurl API from fetcher-cloud — 1 operation(s) for unfurl.
fetcher-cloud Whois API
The Whois API from fetcher-cloud — 1 operation(s) for whois.
Scroll within the panel for all 18 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Fetcher Cloud Rate Limits
RATE LIMITSSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
fetcher-cloud API Rules
SPECTRALExamples 1
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Fetcher Cloud Mcp
EXAMPLESecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for fetcher-cloud — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Commercial 1
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/fetcher-cloud · machine-readable index on apis.io
This is an independent, third-party profile of fetcher-cloud, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.