Microlink API

Name: Microlink API
Brand: Microlink API
Availability: InStock

✓ Official Vendor SpecData EnrichmentData TransformationapiKey1 EndpointsREST

For Agents

Send any URL to Microlink and get back structured page metadata plus optional screenshots, PDFs, or scripted browser output for that URL.

Install Jentic One Beta

Connect the Microlink API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Microlink 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 Microlink API.

Extract Open Graph metadata including title, description, author, publisher, image, and logo for any URL

Generate a full-page or viewport screenshot of a URL by adding the screenshot parameter

Render and download a URL as a PDF for archival or compliance purposes

GET STARTED

Start building with Microlink API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Microlink API for, with concrete tasks.

★ Link Previews and Unfurls

Chat, social, and content products that show a rich preview when a user pastes a URL call GET / on api.microlink.io and use the returned title, description, image, and logo to render the card. Microlink handles redirects, lazy-loaded images, and many edge cases that a naive Open Graph parser misses, so previews look right across heterogeneous sites.

Call GET / with the URL parameter set to a news article and return the title, description, and image fields.

Automated Screenshots and PDFs

Marketing, QA, and compliance teams that need a visual record of a page at a specific moment add screenshot or pdf parameters to GET / and store the rendered artefact. This avoids running headless Chromium internally and supports authenticated pages via Microlink's browser automation parameters.

Call GET / with the URL parameter and pdf=true to capture a PDF of the target page.

Bulk URL Enrichment for Pipelines

Data teams enriching feeds of marketing or news URLs use Microlink in their ETL to attach publisher, author, and image fields to each row. Because the API is one stateless endpoint, parallelisation is straightforward, and caching by URL keeps cost bounded when the same articles reappear.

For each URL in a feed of 500 articles, call GET / and persist the returned author, publisher, and image fields.

Agent-Driven Page Understanding

AI agents that read the open web rely on consistent metadata. Through Jentic, an agent searches for the operation by intent, loads the GET / schema with the URL parameter, and executes — getting back a clean structured payload to reason over instead of raw HTML. The Microlink x-api-key never enters the agent's prompt.

Search Jentic for 'extract metadata from a URL', load GET /, and execute with the URL the user wants to research.

Key Endpoints

1 endpoints — microlink is a metadata extraction and browser automation api that turns any url into structured data, screenshots, pdfs, and scripted browser actions with a single get request.

METHOD

PATH

DESCRIPTION

GET

Extract metadata, screenshot, or PDF for a URL

GET

Extract metadata, screenshot, or PDF for a URL

Why Jentic?

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

Credential isolation

The Microlink x-api-key is stored encrypted in the Jentic vault. Agents request operations and Jentic injects the header at execution time, so the key never enters the agent's context.

Intent-based discovery

Agents search Jentic with intents like 'get the title and image for a URL' and Jentic returns the matching GET / operation with its parameter schema, so the agent does not browse Microlink's documentation.

Time to first call

Direct Microlink integration: 1-2 hours since the API is a single endpoint. Through Jentic: minutes — search, load, execute, with consistent calling conventions across all your APIs.

FAQs

Specific to using Microlink API through Jentic.

What authentication does the Microlink API use?

Microlink uses an API key passed in the x-api-key header. There is also a free tier without a key, with stricter limits. Through Jentic the API key lives in the encrypted vault and is added to requests at execution time.

Can I take a screenshot of a page that requires login?

Microlink's browser automation parameters allow scripting clicks, form inputs, and waits before capture, which covers many login flows. For sensitive credentials, supply them through Microlink's secret parameters rather than embedding them in the URL.

What are the rate limits for the Microlink API?

Free, key-less requests are limited to a small per-minute and per-day quota; paid tiers raise the cap and allow higher concurrency. Inspect the X-RateLimit headers and Microlink's pricing page for the current per-tier numbers before scaling out a bulk job.

How do I extract metadata for a URL through Jentic?

Search Jentic for 'extract metadata from a URL', load GET /, and execute with the url query parameter. Jentic injects the x-api-key header from your stored Microlink credential.

Is the Microlink API free?

There is a free tier with limited rate and no SLA. Production use cases and higher quotas require a paid plan; check Microlink's pricing page for current tiers.

Does Microlink follow redirects and resolve canonical URLs?

Yes — Microlink follows redirects and exposes the resolved URL in its response, so link preview cards point to the canonical destination rather than the originally posted URL.