Link Preview Cache API

io.github.cmondilloPublished by GitHub account cmondillov1.0.0Updated Nov 1, 2026

Same link preview data as link-preview-api, ~1/3 the price via a shared cache.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingFinance

Overview

AI-generated overview

Remote MCP tool that fetches Open Graph and meta metadata for a public URL, billed per call in USDC on Base through a shared cache.

What you can do
  • Fetch link preview metadata for a public URL: Open Graph tags, title, description and image.
  • Return the same preview data as the pricier link-preview service, served from a shared cache at roughly a third of the price.
  • Handle payment inline: the call returns an HTTP 402 quote, the agent pays a few cents in USDC, and the answer comes back automatically.
When to use it
Useful when an assistant needs quick link previews or page metadata for public URLs and the workflow can pay small per-call fees in USDC without human checkout. A cheaper option than the full-price link preview service when cached results are acceptable.
Requirements
A remote streamable HTTP endpoint; no local install, account, API key or headers are declared. A wallet able to pay USDC on Base mainnet is needed, since each call costs $0.003 USDC via the x402 payment flow. Network access to the endpoint and to the payment network.
Before you install
Every call spends real money: $0.003 USDC on Base mainnet per preview, paid automatically by the agent. Payment requires a funded wallet and signing of x402 payments, so spending limits and wallet keys should be controlled. The URL being previewed is sent to a third-party service, and results come from a shared cache, so they may be stale.

Installation

In SourceWeft

  1. Open Link Preview Cache API in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.cmondillo%2Flink-preview-cache-api/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "link-preview-cache-api": {
      "type": "http",
      "url": "https://link-preview-cache-api.onrender.com/mcp"
    }
  }
}

README

tools

A portfolio of small, single-purpose paid services sold directly to AI agents — no human checkout flow, no dashboard login, no subscription. An agent calls the API, gets an HTTP 402 Payment Required quote, pays a few cents in USDC, and gets its answer. Fully automatic on both sides.

Each service lives in its own self-contained folder under projects/ and follows the same pattern:

  • One narrow problem, solved well. No platforms, no suites — a single job an agent needs done.
  • x402 for payment. HTTP-native, stablecoin micropayments, no merchant account or KYC required on the seller side — just a wallet address. This is the emerging standard for agent-to-API payments (backed by Coinbase, adopted by AWS Bedrock AgentCore, Cloudflare, and others as of 2026).
  • Discoverable by agents, not just humans — each API declares an x402 Bazaar discovery schema so agents can find and call it without a human ever reading the docs.
  • A sample automation client included with every project, showing an agent discovering, paying for, and consuming the service end-to-end.
  • Where it adds real reach, also sold as an MCP tool (api/app/mcp_server.py) — the same product, the same price, a second interface for coding agents that discover tools over MCP rather than raw HTTP.

Projects

ProjectWhat it sellsStatus
link-preview-apiPay-per-call URL metadata (Open Graph/title/description/image) extractionLive on Base mainnet, earning real USDC: https://link-preview-api-z4nf.onrender.com
content-moderation-apiPay-per-call profanity/explicit-content detection with redaction, sold over both HTTP and MCPLive on Base mainnet, earning real USDC: https://content-moderation-api-hhy1.onrender.com
link-preview-cache-apiSame product as link-preview-api, ~⅓ the price — backed by a shared cache. First instance of a general "x402 cache" patternLive on Base mainnet, earning real USDC: https://link-preview-cache-api.onrender.com

Repo conventions

  • Every project is fully self-contained in projects/<project-slug>/: its own code, tests, Dockerfile, deploy config, and README. Nothing product-specific is shared between projects.
  • Every project ships with:
    • api/ — the paid service itself
    • automation-client/ — a sample agent that pays for and consumes it
    • deploy/ — ready-to-use deploy configs (Render/Fly/etc.)
    • README.md — the business case, architecture, and exact steps to take it from "runs on my machine" to "earning money"
    • LISTING.md — the marketplace/directory listing copy, ready to publish
  • New projects get added the same way: a clean new folder, same skeleton, linked in the table above.
  • One deliberate exception to "nothing shared": scripts/ holds portfolio-level publishing tooling — not product code, reused across every project the same way (e.g. submitting a new tool to x402-list.com's API). See PUBLISHING.md for the full playbook: what's genuinely automatic, what's scripted, and what stays a deliberate manual step and why.

Source: README.md at commit 876f8ce

Tools

1

preview_url

Fetch Open Graph / meta metadata for a public URL. Costs $0.003 USDC on Base.

Parametersurlrequired

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.