TinyFish
TinyFish provides enterprise infrastructure for AI web agents — a unified platform that lets AI systems interact with the live web at scale. It ships four API surfaces: a Web Agent Automation API that turns natural-language goals into browser automations on real websites (sync, async, SSE-streaming, and batch), a Search API returning structured JSON from browser-rendered results, a Fetch API that converts rendered pages to clean markdown/JSON/HTML, and a Browser API for cloud CDP browser sessions with stealth/anti-bot capabilities. All APIs authenticate with an X-API-Key header, are documented at docs.tinyfish.ai with published OpenAPI specs and an llms.txt, and are exposed to assistants through an official hosted MCP server. TinyFish is the company behind the open-source AgentQL project and is backed by ICONIQ Capital.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles TinyFish the way a machine reads it — 12 machine-readable artifacts across 7 APIs, 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 — TinyFish scores 56.5/100 (developing), with a separate agent-readiness read of 75/100 (agent native). 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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile TinyFish
Each block below is one kind of artifact we hold for TinyFish. 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 7
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.
TinyFish Automation API
Browser automation endpoints for executing tasks on websites
TinyFish Runs API
Endpoints for retrieving automation run data
TinyFish TinyFish Browser API API
The TinyFish Browser API API from TinyFish — 1 operation(s) for tinyfish browser api.
TinyFish TinyFish Fetch API API
The TinyFish Fetch API API from TinyFish — 1 operation(s) for tinyfish fetch api.
TinyFish TinyFish Search API API
The TinyFish Search API API from TinyFish — 1 operation(s) for tinyfish search api.
TinyFish Usage API
The Usage API from TinyFish — 1 operation(s) for usage.
TinyFish Vault API
Vault credential management endpoints for connecting password managers and managing stored credentials
Scroll within the panel for all 7 ·
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.
tinyfish-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Tinyfish Agent Webhooks
ASYNCAPISecurity 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.
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 TinyFish — 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 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/tinyfish · machine-readable index on apis.io