Postlight Mercury Web Parser API

Name: Mercury Web Parser API
Brand: Mercury Web Parser API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentData TransformationapiKey2 EndpointsREST

For Agents

Install Jentic One Beta

Connect the Mercury Web Parser API to your agent

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

Extract article body content from any URL in HTML, Markdown, or plain text format

Identify and return article metadata including author, publication date, and title

Parse pre-fetched HTML content without requiring an additional network request

GET STARTED

Start building with Mercury Web Parser API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Mercury Web Parser API for, with concrete tasks.

★ Content Aggregation Pipeline

Build automated content aggregation feeds by extracting article text and metadata from multiple source URLs. Mercury Parser returns structured data including title, author, publication date, and clean article body, enabling agents to compile curated content digests without manual copy-pasting. Each parsed result includes word count and excerpt for filtering and prioritization.

Parse https://example.com/article-url and return the article title, author, word count, and content in Markdown format

Reader Mode for Applications

Provide a distraction-free reading experience by stripping ads, navigation, and sidebars from web pages. Mercury returns only the core article content in the requested format, along with text direction detection for proper rendering of RTL languages. Integration adds reader-mode functionality to any application in minutes rather than building custom extraction logic.

Extract the article content from a given URL in plain text format and verify the word count exceeds 200 words

Research and Knowledge Base Ingestion

Ingest web articles into knowledge bases or research systems by extracting structured content programmatically. Mercury returns publication dates, authors, and full article text that can be indexed, chunked for embeddings, or stored as reference material. Supports custom headers for accessing authenticated or paywalled content when credentials are available.

Parse a research article URL with custom headers and store the returned title, author, date_published, and content fields in a knowledge base record

AI Agent Web Content Access

Enable AI agents to read and understand web page content through Jentic by searching for the parse operation, loading the schema, and executing against target URLs. Agents discover the parsing capability via intent search and receive structured article data without needing to handle HTML scraping logic directly. Integration through Jentic takes under an hour compared to building custom parsers.

Search Jentic for 'extract article content from URL', load the Mercury Parser schema, and execute a parse request against a target news article URL

Key Endpoints

2 endpoints — jentic publishes the only available openapi specification for mercury web parser api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/parser

Parse a web page by URL and extract content

POST

/parser

Parse pre-fetched HTML content

GET

/parser

Parse a web page by URL and extract content

POST

/parser

Parse pre-fetched HTML content

Why Jentic?

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

Credential isolation

Mercury API keys are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens and never see the raw x-api-key header value directly.

Intent-based discovery

Agents search by intent (e.g., 'extract article content from a URL') and Jentic returns the Mercury Parser operations with their input schemas, so the agent can call the correct endpoint without browsing documentation.

Time to first call

Direct Mercury integration: 1-2 hours for auth setup and response parsing. Through Jentic: under 15 minutes — search, load schema, execute.

FAQs

Specific to using Mercury Web Parser API through Jentic.

Why is there no official OpenAPI spec for Mercury Web Parser API?

Postlight does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Mercury Web Parser 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 Mercury Web Parser API use?

The Mercury Web Parser API uses an API key passed in the x-api-key HTTP header. Through Jentic, this key is stored encrypted in the credential vault and agents receive scoped access without handling raw keys directly.

Can I extract content in Markdown format with the Mercury Web Parser API?

Yes. The parser endpoint accepts a contentType query parameter with values html, markdown, or text. Setting contentType to markdown returns the extracted article body formatted as Markdown, which is useful for knowledge base ingestion and LLM context preparation.

What are the rate limits for the Mercury Web Parser API?

The API returns a 429 status code when rate limits are exceeded. Specific rate limit thresholds depend on your API key tier. Monitor response headers for rate limit state and implement exponential backoff when a 429 response is received.

How do I parse a web page through the Mercury Web Parser API using Jentic?

Install the SDK with pip install jentic, then search for the intent 'extract article content from URL'. Jentic returns the Mercury Parser parseUrl operation with its input schema. Execute with a target URL and optional contentType parameter to receive structured article data including title, author, content, and word_count fields.

Can I parse pre-fetched HTML without making Mercury fetch the URL again?

Yes. The POST /parser endpoint accepts a JSON body with url and html fields. Provide your already-fetched HTML in the html field and the original URL in the url field for link resolution. This avoids duplicate network requests when you have already retrieved the page content.

Postlight Mercury Web Parser API

Connect the Mercury Web Parser API to your agent

Capabilities

Start building with Mercury Web Parser API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs