Skip to content
AgentsIndex

NanoParse

Verified owner

Web page to Markdown for AI agents, with rule-based trust signals and per-parse x402 payment in USDC.

NanoParse is a hosted MCP server and REST endpoint that renders a URL in headless Chromium and returns clean Markdown. Each parse also carries Litmus, a set of deterministic checks on authorship, freshness, paywalls and soft 404s, paid per call over x402 without an account.

Best for
Developers building AI agents that need web content converted to Markdown with built-in trust signals, not just raw text.

What we checked

Pages last read
Facts checked
5 facts

From 11 sources

AI answers
Too few read

58 buyer-question answers read, November 2026

At a glance

Tags
No credit card

For developers

Works with
Coinbase, Claude Code, Cursor, Firecrawl, Jina Reader

NanoParse in our research

All research

Study

AI Tool Pricing Index, November 2026

Pricing

Usage-based

43 of the 361 tools we checked bill by usage.

Edition price, checked 14 November 2026.

Pricing pages of the AI tools, November 2026 editionas of n = 361 tools checked

It judges whether a page is citable, not only readable

NanoParse takes one URL, renders it in headless Chromium with JavaScript executed, removes navigation, ads and boilerplate, and returns Markdown with page metadata. Beside the Markdown it returns Litmus, twenty signals in four groups: source (authority, authorship, content type, outbound authority, citations, structured data), trust (structural trust score, hedge language, content density, boilerplate ratio, quote density), validity (freshness, page status, paywall, syndication, archive presence, redirects) and read (TL;DR, key figures, reading time).

The signal set targets specific failures: a soft 404, captcha or login wall that arrives with a 200 status, a syndicated copy taken for the original, and an old explainer cited as current. The Litmus page sorts results into a verdict of drop, review or cite, and states that "a hard failure wins". Every signal is described as "rule-based and extractive" with "no model, no temperature", and the Litmus version is pinned to each response so the same page and version return the same signals. Two signals look outside the page: is_archived queries the Wayback Machine and archive.today, and source.authority "leans on a domain reference list". A signal that cannot be determined comes back as null or "unknown".

One flat charge per successful parse, settled after the render

The terms set the price at "$0.002 per test, paid in USDC on Base over x402, per call", with "No subscription and no minimum. There is no plan to cancel." The same figure is a machine-readable field in the OpenAPI spec, where x-payment-info.price carries mode fixed, currency USD and amount 0.002, and the 402 challenge on the quickstart asks for 2,000 base units of USDC.

Settlement happens only after the page renders. A failed render, a blocked or paywalled target, a timeout and a page yielding under 50 words are not billed, and the facilitator covers network fees. A batch is budgeted as pages times the per-parse rate: the quickstart's worked example puts 150 pages at the flat rate with the free allowance on top and nothing prepaid.

Paying means a wallet. The agent receives an x402 v2 challenge, signs an EIP-712 TransferWithAuthorization for USDC on Base with a 60 second window, and retries. There is no card path; the privacy page says "we never see a card number, because there is no card." For callers without a wallet, the quickstart points to npx @coinbase/payments-mcp, which gives the agent a Coinbase wallet funded through Apple Pay.

The free allowance is described four different ways

The home page and quickstart say "10 free parses a month" with "no account and no key", and the quickstart adds a free claim step: sign a fixed message with any Ethereum wallet (EIP-191) to "claim 10 free parses". After that the pages diverge.

llms.txt says "a signed wallet claims 10 more when the network allowance is spent", which reads as twenty a month. The product catalog inside the same llms.txt says "a signed wallet claims the same 10 from a cloud host", which reads as ten. The OpenAPI description says "Up to 10 parses per network are free", tying the allowance to a network rather than to a month or a wallet. The home page demo box is a separate allowance of "3 free demos / day" in the browser.

The ten a month is the figure every page shares; whether a wallet doubles it is not settled by the vendor's own text.

How long results are kept is not the same on every page

Three retention statements are live at once. The privacy policy says parsed content and results are kept for "a short operational window for debugging and abuse review" and names no duration.

The OpenAPI spec documents a single path, POST /fetch, with the free status poll described only in prose. The vendor's own blog notes that a client generator pointed at the spec "emits one method" while the endpoint "answers five routes". The spec's job status enum now lists completed and failed. Its description also mentions "spam and AI-generation screening", which does not appear among the twenty signals on the Litmus page.

Where it fits, and who should look elsewhere

It fits an agent that reads from a handful to a few hundred pages and needs a logged reason for trusting each one: a research or RAG pipeline, a citation checker, a competitive scan. Connecting is one entry in an MCP client config pointing at https://nanoparse.app/mcp, and hosts such as Claude Code, Cursor, Windsurf, Cline and Zed discover the two tools, nanoparse_fetch and nanoparse_status, on their own.

The vendor's llms.txt lists what it does not do. Firing tens of thousands of concurrent requests "will be rate-limited", though a sequential 1,000 page list is supported. Paywalled and login-gated content stays gated. Renders time out at 15 seconds and queued jobs older than five minutes are dropped.

Two constraints weigh more than the price. Payment requires USDC on Base from a wallet that signs typed data, which rules out a finance team that can only pay by card or invoice. And with no uptime commitment, no audit and no named entity behind the endpoint, a production pipeline should keep a fallback reader behind it.

NanoParse price and terms

Terms

Free plan
YesYes10 free parses a month, no account or API key
Card to start
YesNot required
Sign up without sales
YesYes
The terms in full

on cloud MCP hosts the allowance is claimed by signing an EIP-191 wallet message. The browser demo allows 3 free demos a day.

For AI agents

Where these prices come from

nanoparse.app/legal, checked

What we checked on NanoParse

YesPartlyNo

What it costs to startYes

What the price counts

Priced per use: a flat charge for each successful parse, paid in USDC on Base, with no subscription or minimum and failed parses not billed.

$0.002 per test, paid in USDC on Base over x402, per call. No subscription and no minimum. There is no plan to cancel.

nanoparse.app/legalChecked

What it costs to startYes

Free to use

A standing free allowance of 10 parses a month without an account or key; the MCP server card says cloud hosts must sign a wallet message to claim it.

You get 10 free parses a month with no account and no key.

nanoparse.app/quickstartChecked

How you build with itYes

Public API

A public POST /fetch endpoint is documented in an OpenAPI 3.1 spec with a free unauthenticated status poll, and it needs no key or signup.

POST /fetch with {"url": "https://example.com"} to parse a page.

nanoparse.app/openapi.jsonChecked

How you build with itYes

MCP server

Its MCP server at nanoparse.app answers, 2 tools

nanoparse-mcp

nanoparse.app/mcpChecked by us,

How you build with itYes

Open source

The nanoparse-mcp GitHub repository is MIT licensed, but it holds docs, examples and a retired local client; the hosted parsing service itself is not shown there.

On the page: README, end of Docs section

github.com/nanoparse-dev/nanoparse-mcpChecked

NanoParse alternatives

Questions about NanoParse

How much does NanoParse cost?
NanoParse has a free plan. From nanoparse.app/legal, checked 14 November 2026.
Does NanoParse have an API or an MCP server?
NanoParse has an API. From nanoparse.app/openapi.json, checked 20 October 2026. NanoParse has an MCP server. We checked nanoparse.app/mcp ourselves on 15 November 2026.
Is NanoParse open source, and can you host it yourself?
NanoParse is open source. From github.com/nanoparse-dev/nanoparse-mcp, checked 14 November 2026. You cannot host NanoParse yourself. From github.com/nanoparse-dev/nanoparse-mcp, checked 20 October 2026.
What have we checked on NanoParse?
5 facts, under these headings: What it costs to start, how you build with it.
How do we check NanoParse?
We hold 5 facts on NanoParse, quoted from 11 pages. Facts last checked 15 November 2026. Price last checked 14 November 2026. Last change found 15 November 2026.

How we check every listing

NanoParse price history

We have read the price once so far, on 14 November 2026: a free plan, and paid plans from $0.002 per parse.

PricePlanFirst seenLast seenReadingsSource
$0.002 per parseCheapest paid plan14 November 202614 November 20261Pricing page, read 14 November 2026

From our research on 14 November 2026. A date is when we read the page, not when the price changed.

Similar in Agent tools and integrations

See all in Agent tools and integrations

Claimed by the NanoParse team.

We check its facts against the NanoParse site.Facts checked 15 November 2026

Report an error if a fact is wrong.