link.fish API

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

★ Only Publicly Available OpenAPI DocumentData EnrichmentData Transformationbasic8 EndpointsREST

For Agents

Extract structured data, screenshots, social profiles, and tabular content from any URL via 8 basic-auth endpoints.

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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 main content, title, and metadata from any web URL without writing scrapers

Generate full-page screenshots of a URL using a headless-browser renderer

Pull tabular data from HTML pages and return it as structured rows

GET STARTED

Start building with link.fish API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for link.fish API, keeping it validated and agent-ready. The link.fish API extracts structured data from arbitrary websites by URL — including the page's main content, social-media accounts, geo-coordinates, and tabular data. Eight endpoints cover full-page extraction, browser-rendered extraction, screenshot generation, and lookup helpers for mobile apps, JSON/XML structures, and tabular content. Authentication uses HTTP Basic with a username and password issued by link.fish, and the API is served only over HTTPS.

Use Cases

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

★ Link Preview Generation

Generate rich link previews for chat, email, or CMS clients by extracting title, image, and description plus a full-page screenshot. The /Urls/data and /Urls/browser-screenshot endpoints handle both fast extraction and rendered captures. Replaces hand-maintained Open Graph parsers with one call.

Extract metadata for URL 'https://example.com/article' and generate a 1200x630 screenshot for a chat link preview

Content Ingestion Pipeline

Ingest article content, tabular data, and metadata into a knowledge base from a list of URLs. The /Urls/browser-data endpoint renders JavaScript-driven pages so single-page-app content is captured correctly. Replaces custom Puppeteer pipelines for many simple use cases.

For each URL in a list of 50 industry blogs, run /Urls/browser-data and store the extracted article text

Social-Media Discovery

Find the social-media handles a brand or person publishes on their website without manually crawling each page. The /Urls/social-media endpoint returns Twitter, LinkedIn, Instagram, and other handles surfaced on a URL. Useful for outbound research and lead enrichment.

Run /Urls/social-media against 'https://acme.com' and return all extracted social handles

AI Agent Web Researcher

An AI agent uses Jentic to call link.fish operations when it needs structured page content, social handles, or screenshots from a URL. The agent composes /Urls/data and /Urls/browser-screenshot to surface page summaries with previews. Credentials stay isolated through Jentic.

Search Jentic for 'extract data from a URL', load /Urls/data, and call it with the user's target URL

Key Endpoints

8 endpoints — jentic publishes the only available openapi specification for link.

METHOD

PATH

DESCRIPTION

GET

/Urls/data

Extract structured data from a URL

GET

/Urls/browser-data

Extract data using a headless browser

GET

/Urls/browser-screenshot

Generate a screenshot of a URL

GET

/Urls/social-media

Get social-media accounts referenced on a URL

GET

/Urls/data-tabular

Return tabular data extracted from a URL

GET

/Urls/data

Extract structured data from a URL

GET

/Urls/browser-data

Extract data using a headless browser

GET

/Urls/browser-screenshot

Generate a screenshot of a URL

GET

/Urls/social-media

Get social-media accounts referenced on a URL

GET

/Urls/data-tabular

Return tabular data extracted from a URL

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

link.fish HTTP Basic credentials are stored encrypted in the Jentic MAXsystem vault. Agents call operations through scoped execution credentials so the raw username and password never enter the prompt or logs.

Intent-based discovery

Agents search by intent (e.g., 'extract data from a URL') and Jentic returns the matching link.fish operation across the 8 endpoints with the full query schema.

Time to first call

Direct link.fish integration: half a day for auth and response parsing. Through Jentic: under 20 minutes — search, load, execute.

FAQs

Specific to using link.fish API through Jentic.

Why is there no official OpenAPI spec for link.fish API?

link.fish does not publish a maintained OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the link.fish API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the link.fish API use?

link.fish uses HTTP Basic authentication with a username and password issued by the platform. All requests must use HTTPS. Through Jentic, the credentials are stored encrypted in the MAXsystem vault and injected per request.

Can I extract data from JavaScript-rendered pages with link.fish?

Yes. Use /Urls/browser-data to render the page in a headless browser before extracting. /Urls/data is faster but only sees server-rendered HTML, so prefer /Urls/browser-data for single-page apps.

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

The spec does not document explicit rate limits. Treat browser-rendered endpoints as more expensive than plain extraction; back off on HTTP 429 and prefer /Urls/data over /Urls/browser-data when the target page is not JavaScript-driven.

How do I generate a webpage screenshot through Jentic?

Run pip install jentic, then search Jentic with 'generate a screenshot of a webpage' to retrieve /Urls/browser-screenshot. Execute it with the target URL; Jentic handles HTTP Basic credentials automatically.

Can link.fish extract tabular data from HTML?

Yes. /Urls/data-tabular returns tabular content from a URL as structured rows, suitable for ingesting reference tables and league standings without writing custom HTML parsers.