Install Jentic One Beta

Connect the link.fish API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the link.fish 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%2Flink.fish%2Flink-fish" | 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%2Flink.fish%2Flink-fish" | 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 link.fish API.

Extract structured metadata and content from a web page by URL

Render a page in a real browser to capture data past client-side scripts

Generate a screenshot of a rendered page

Pull social media accounts linked from a site

Return geo coordinates and linked mobile apps found on a page

GET STARTED

Start building with link.fish API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use link.fish API for, with concrete tasks.

★ Agent-driven page enrichment through Jentic

An AI agent researching a company can pull a site's metadata, social accounts, and linked apps in one pass. Through Jentic the agent discovers the extract operations by intent and loads their schemas, so it enriches a URL without hand-wiring the link.fish endpoints.

Search Jentic for 'extract data from a web page', pull metadata for a URL, then get the social media accounts linked on it.

Browser rendering for script-heavy pages

Extract data from pages that build their content with client-side scripts by rendering them in a real browser first. link.fish returns the data and an optional screenshot of the rendered page, so an agent captures content a raw fetch would miss.

Render a script-heavy page in a browser, return its extracted data, and capture a screenshot of the result.

Contact and location harvesting

Collect social media accounts and geo coordinates published on a page to seed a contact or location record. link.fish parses these out of the page so an agent does not have to write per-site selectors.

Extract the social media accounts and geo coordinates from a business page and save them to a record.

Key Endpoints

8 endpoints — the link.

METHOD

PATH

DESCRIPTION

GET

/Urls/data

Extract data from a URL

GET

/Urls/browser-data

Extract data via browser rendering

GET

/Urls/browser-screenshot

Generate a screenshot

GET

/Urls/social-media

Get social media accounts

GET

/Urls/geo-coordinates

Get geo coordinates

GET

/Urls/data

Extract data from a URL

GET

/Urls/browser-data

Extract data via browser rendering

GET

/Urls/browser-screenshot

Generate a screenshot

GET

/Urls/social-media

Get social media accounts

GET

/Urls/geo-coordinates

Get geo coordinates

Why Jentic?

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

Setup

Wiring link.fish by hand means sending Basic credentials over HTTPS and choosing between raw and browser-rendered extraction per site. Through Jentic you install once, import link.fish from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

link.fish carries the target URL in the request, so rules bound which operations your agent may call, not which sites. You choose the operations it may call, such as extracting data and social accounts, so browser rendering is not included unless you add it.

Credential isolation

Your link.fish credentials 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 'extract data from a web page' or 'get a screenshot', and Jentic returns the matching link.fish operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using link.fish API through Jentic.

What authentication does the link.fish API use?

The link.fish API uses HTTP Basic authentication per its OpenAPI spec: your agent sends a username and password over HTTPS. Through Jentic these are stored encrypted by your own Jentic One instance and injected at request time, so your agent never handles them directly.

Is there a link.fish API MCP server?

You don't need an MCP server to give your agent the link.fish API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it on demand without loading another server's tool definitions into its context.

Can I render a JavaScript-heavy page with the link.fish API?

Yes. The browser-data operation renders the page in a real browser before extracting, so content built by client-side scripts is captured, and a browser-screenshot operation returns an image of the rendered page.

What are the rate limits for the link.fish API?

The OpenAPI spec does not specify rate limits. Check the link.fish documentation at https://link.fish for current limits before running large extraction batches.

Can I limit what my agent is allowed to do with the link.fish API?

Yes. link.fish carries the target URL in the request, so rules bound which operations your agent may call, not which sites. Allow only the extract operations it needs, such as page data and social accounts, so browser rendering is not included unless you add it.

How do I extract data from a page with the link.fish API through Jentic?

Search Jentic for 'extract data from a web page', load the data operation, and pass the target URL. Jentic injects your credentials and returns the extracted data. To run it on your own infrastructure, install Jentic One from its GitHub repo.

link.fish API

Name: link.fish API
Brand: link.fish
Availability: InStock

Community OpenAPI document · agent-readyData EnrichmentData Transformationbasic8 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Extract metadata, tabular data, screenshots, social accounts, and geo coordinates from any web page by URL.

Use for: I need to extract the title and metadata from a URL, Render this page in a browser and return its data, Get a screenshot of a web page, Find the social media accounts linked on a site

Not supported: Does not store crawled pages, schedule recurring crawls, or manage proxies. Use for extracting structured data from a web page by URL only.

The link.fish API extracts structured data from web pages by URL. It returns page metadata and tabular data, renders pages in a real browser to capture data and screenshots, and pulls out social media accounts, geo coordinates, and linked mobile apps found on a site.

Jentic One on Github View OpenAPI Document