miniurl.com valid

MiniURL.com

MiniURL.com is a URL shortener with analytics, custom aliases, QR codes, custom domains, and an agent-friendly REST API and MCP server.

For agents: URL shortener with analytics, custom domains, QR codes, a REST API, OpenAPI spec and MCP server for AI agents.

url shortenerqr codeslink analyticsrest apimcp server

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T13:02:56.772Z. Cached copy · Source on miniurl.com

# MiniURL.com

> MiniURL.com is a URL shortener with analytics, custom aliases, QR codes, custom domains, and an agent-friendly REST API and MCP server.

## For AI Agents - Quick Start

If the client supports MCP, use the MiniURL MCP server first:

- MCP endpoint: https://workers.miniurl.com/mcp
- Transport: Streamable HTTP
- Preferred first tool: shorten_url
- Guest behavior: shorten_url can auto-create a short-lived guest bearer token when no auth is configured
- Production Agent behavior: discover OAuth 2.1 + PKCE from https://workers.miniurl.com/.well-known/oauth-protected-resource and https://workers.miniurl.com/.well-known/oauth-authorization-server, then use a short-lived scoped at_ token
- Safety controls: OAuth Agent tokens can preview create/update redirects with dry_run=true; destructive link/tag/domain/billing operations return human approval links by default
- Production MCP auth: there is no token-setting tool; use OAuth 2.1 + PKCE for a short-lived scoped at_ token, and never expose a long-lived mk_ key to an Agent model
- Raw Streamable HTTP: prefer stateless MCP 2026-07-28 with per-request _meta, MCP-Protocol-Version, Mcp-Method, and Mcp-Name for tools/call; legacy initialize/Mcp-Session-Id remains compatible
- OAuth client registration: Client ID Metadata Documents are supported; Dynamic Client Registration remains available as a fallback
- Agent discovery: the MCP server must be explicitly registered in the Agent runtime; visiting this website does not install it

If MCP is not available, use the REST API:

1. POST https://workers.miniurl.com/api/v1/guest/token
2. POST https://workers.miniurl.com/api/v1/shorten with Authorization: Bearer gt_xxxxx and body {"url":"https://example.com"}
3. For production Agent access, use OAuth 2.1 + PKCE to obtain a scoped at_ token. The guest registration endpoints remain a human account bootstrap flow; do not relay the returned mk_ key to a model
4. Use POST /api/v1/alias/check before custom aliases and GET /api/v1/tags for registered account tag workflows

Always read the meta object in API responses. It may include usage, notices, limitations, and upgrade hints.

## Agent-Readable Docs

- [REST API Markdown](https://miniurl.com/ai/apidocs.md)
- [MCP Markdown](https://miniurl.com/ai/mcp.md)
- [OpenAPI JSON](https://miniurl.com/openapi.json)
- [AI index](https://miniurl.com/ai/index.md)

## Main Pages

- [Home](https://miniurl.com/): Create short URLs, QR codes, and track clicks
- [Pricing](https://miniurl.com/pricing/): Compare Guest, Free, and Pro plans
- [REST API docs](https://miniurl.com/apidocs/): Endpoint reference and quick start
- [MCP docs](https://miniurl.com/mcp/): Agent tool reference and setup
- [Terms](https://miniurl.com/terms/)
- [Privacy](https://miniurl.com/privacy/)

## Marketing Hubs

- [MiniURL Comparisons](https://miniurl.com/compare/): Compare MiniURL with common link management approaches and short link workflows.
- [MiniURL Integrations](https://miniurl.com/integratio
…

Related sites

Other listed sites in APIs and SDKs. See the whole category →

Machine-readable: GET /v1/resolve?q=miniurl.com · GET /v1/domain/miniurl.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for miniurl.com:
1. POST https://agentwebmap.com/v1/sites/miniurl.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://miniurl.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/miniurl.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/miniurl.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.