Install Jentic One Beta

Connect the TinyFish Web Agent Automation API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the TinyFish Web Agent Automation API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmino.ai%2Fmino" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmino.ai%2Fmino" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with TinyFish Web Agent Automation API.

Run a browser automation against a URL with a natural language goal, in lite or stealth browser_profile mode

Start batches of asynchronous automation runs and cancel them by run id

Fetch up to 10 URLs in parallel and extract their content as markdown, HTML, or JSON

Search the web, news, or research papers with domain, language, and date filters

GET STARTED

Start building with TinyFish Web Agent Automation API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use TinyFish Web Agent Automation API for, with concrete tasks.

★ Agent Web Tasks Through Jentic

An AI agent that needs data from a website with no API hands TinyFish a target URL and a goal such as 'find the cheapest monthly plan', and TinyFish drives a hosted browser to complete it. Through Jentic the agent finds the run operation by intent, sends the url and goal fields with a stored API key, and gets the run result back without managing a browser fleet.

Run a synchronous automation with url 'https://example.com/pricing' and goal 'Return the name and monthly price of every plan as JSON', using the lite browser_profile

Bulk Page Extraction for LLM Pipelines

Retrieval and summarisation pipelines send up to 10 URLs per fetch request and receive each page as markdown, cleaned HTML, or JSON, with optional outbound links, image links, and page metadata. CSS include_selectors and exclude_selectors trim navigation and footers before extraction, and a per-URL timeout keeps one slow page from blocking the rest.

Fetch three documentation URLs in markdown format with exclude_selectors set to 'nav' and 'footer', and return each page's text

Streamed Research Reports

Analysts submit a research question and choose a depth from instant to max, optionally restricting sources to news or research papers and to a date range. The report streams as it is written, and a follow-up run can be seeded with prior_run_id so the next question builds on the earlier evidence.

Start an asynchronous research run with query 'State of WebGPU browser support', mode 'standard', and domain_type 'news', then poll it by research_run_id until it completes

Run Auditing and Debugging

Teams reviewing an automation list runs filtered by status such as FAILED and by created_after timestamp, open a run with screenshots and HTML included, and pull the screenshot or HTML snapshot for an individual step to see where the browser agent went wrong.

List runs with status FAILED created after 2026-11-01T00:00:00Z, then fetch the step screenshot for the first step of the most recent one

Key Endpoints

41 endpoints — the tinyfish web agent automation api runs ai-driven browser automations on any website from a target url and a natural language goal, returning results synchronously, as a server-sent event stream, or as an asynchronous run you poll later.

METHOD

PATH

DESCRIPTION

POST

/v1/automation/run

Run a browser automation synchronously

POST

/v1/automation/run-async

Start an automation asynchronously

GET

/v1/runs/{id}

Get a run by id

GET

/v1/runs

List and search runs

POST

/fetch

Fetch and extract content from URLs

GET

/search

Search the web

POST

/v1/automation/run-research

Run research with SSE streaming

POST

/browser

Create a remote browser session

POST

/v1/automation/run

Run a browser automation synchronously

POST

/v1/automation/run-async

Start an automation asynchronously

GET

/v1/runs/{id}

Get a run by id

GET

/v1/runs

List and search runs

POST

/fetch

Fetch and extract content from URLs

GET

/search

Search the web

POST

/v1/automation/run-research

Run research with SSE streaming

POST

/browser

Create a remote browser session

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring TinyFish by hand means setting the X-API-Key header, choosing between synchronous, SSE, and async run modes, and writing the polling loop for long runs. Through Jentic you install once, import TinyFish from the API Directory, store the key once, and your agent calls it.

Permission scoping

TinyFish targets most work through the request body (the url and goal travel in the payload), so rules bound which operations your agent may call, not which websites it visits. You choose the operations it may call, so sensitive ones like connecting a vault, deleting a profile, or topping up the wallet are not included unless you add them.

Credential isolation

Your TinyFish API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'automate a task on a website' or 'fetch a page as markdown', and Jentic returns the matching TinyFish operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using TinyFish Web Agent Automation API through Jentic.

What authentication does the TinyFish Web Agent Automation API use?

The TinyFish Web Agent Automation API authenticates with an API key sent in the `X-API-Key` header per its OpenAPI spec, and every operation in the spec declares it. Through Jentic the key is stored once, encrypted, by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs.

Can I get structured JSON back from a TinyFish automation run?

Yes. The run operations accept an optional output_schema field that describes the structured result you want, alongside the required url and goal fields. Runs can also post lifecycle events to an HTTPS webhook_url, and the batch operation starts several runs in one request.

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

Yes. For example, write a rule that allows only the fetch, search, and run-by-id read operations, so the agent can pull page content, search the web, and check results while vault connections, profile deletion, and wallet top-ups stay out of reach, and every call it makes is logged.

What are the rate limits for the TinyFish Web Agent Automation API?

The OpenAPI spec does not specify rate limits. Check the TinyFish documentation at https://docs.tinyfish.ai for current limits, and use the fetch, search, and browser usage endpoints to track how much your agent has consumed.

How do I run a TinyFish browser automation through Jentic?

Search Jentic for the intent 'automate a task on a website', which returns the TinyFish run operation and its input schema; the agent posts the url and goal to /v1/automation/run, or to /v1/automation/run-async and polls /v1/runs/{id} for longer jobs. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a TinyFish MCP server?

You don't need an MCP server to give your agent the TinyFish API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the automation, fetch, search, and research operations. Operations are discovered on demand, so no extra tool definitions are loaded into the agent's context.

Mino TinyFish Web Agent Automation API

AI ReadinessAI-Aware (A-)70/100

See full scorecard

Official vendor OpenAPI document · agent-readyCloud InfrastructureComputeapiKey41 EndpointsREST

For Agents

Run natural-language browser automations on any website, fetch and extract page content, search the web, and run streamed research jobs with TinyFish. Authenticated with an X-API-Key header.

Use for: I need to extract pricing from a website by describing the goal in plain language, Start a batch of browser automations and check their status later, Fetch these product pages as markdown for my summariser, Search recent news about a company from the last 60 minutes

Not supported: Does not handle test-suite management, site monitoring schedules, or hosting of scraped datasets. Use for running goal-driven browser automations, page fetching, web search, and research reports only.

The TinyFish Web Agent Automation API runs AI-driven browser automations on any website from a target URL and a natural language goal, returning results synchronously, as a server-sent event stream, or as an asynchronous run you poll later. It also fetches and extracts up to 10 URLs per request as markdown, HTML, or JSON, searches the web, news, or research papers, and runs multi-step research jobs that stream a written report. Supporting resources cover remote browser sessions, Browser Context Profiles that keep signed-in state, 1Password and Bitwarden vault connections for site credentials, and per-step screenshots and HTML snapshots for every run.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

95%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

60%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4

42%

Example Density

How richly the API is illustrated with examples.

98%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: CSignals: 4

70%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

95%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

55%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

77%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the TinyFish Web Agent Automation API to your agent

Capabilities

Start building with TinyFish Web Agent Automation API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Mino TinyFish Web Agent Automation API

Jentic AI Readiness Score

TinyFish Web Agent Automation API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness