AltAPIs

API archive entry · source-reported

OpenUnfurl

No-signup link unfurl API returning Open Graph, Twitter Card and oEmbed metadata

Provider / source website

From the publisher

README & documentation

Source preview

Read the project’s overview, installation instructions and usage examples. The original README is the source of truth.

A zero-signup link-unfurl / link-preview API. No account, no API key — one GET request. Give it any public URL, get back clean preview metadata (title, description, image, siteName, favicon, Open Graph / Twitter Card, oembed) as JSON. Built so autonomous AI agents can use it as a tool — an agent has no human to do a signup. Live: https://openunfurl.vercel.app Sample response: Any missing field is null. Errors return JSON with an error key and an appropriate HTTP status (400 bad/blocked/missing URL, 422 fetch failed, 429 rate limited, 405 wrong method). OpenUnfurl is also a remote MCP server, so an agent can call it as a tool with no signup, no API key, no OAuth. application/json response — no sessions, no SSE) returns the same preview JSON as the REST endpoint (also as structuredContent) Drop this into any MCP client config (Claude Desktop, Cursor, or any client that speaks…

SolvoHQ/openunfurl on GitHub A short preview, not the full document.

Read the full README ↗ · Preview checked 2026-09-20T18:46:13.830Z

Inside the original README — Document outline
  1. OpenUnfurl
  2. Quick start
  3. JavaScript
  4. Use as an MCP tool (AI agents / Claude / Cursor / LLM clients)
  5. Why
  6. Limitations
  7. Self-host — it's zero-dependency files
  8. License

Headings are captured from the source. Links open the publisher’s document, not a locally hosted copy.

Links from the README

References supplied by the publisher, not independently verified endorsements. Check the destination before downloading files or entering credentials.

Documentation belongs to its respective authors. A listing is not a grant of reuse or training rights. Confirm the document’s own terms at the source.

Where these facts came from

AltAPIs imported it from Public API Lists. The source link and dates remain visible for independent inspection.

What is reported

  • Name, category, and short description
  • Authentication label
  • HTTPS and CORS labels
  • Provider/source URL

What is not established

  • Current uptime or availability
  • Pricing, quotas, and rate limits
  • Security, compliance, or licensing posture
  • SDK quality or endpoint completeness

Record checkpoints

  1. First observed: Sep 20, 2026
  2. Last directory-field change: Sep 20, 2026
  3. Current source observation: Sep 20, 2026

Submit a source-backed correction

Source reference

Public API Lists

This page separates source-reported facts from questions that need live provider verification.