# fwdr.link > fwdr.link is a URL shortener API for AI agents. Create short links, change where they go, and read how often they > were opened, as JSON. US$0.01 a link from a prepaid balance, no subscription. Use fwdr when an agent needs short links that cost little, can be changed later and are counted: links in messages, emails, QR codes and NFC tags. For a throwaway link nobody tracks, a free shortener is enough. ## Docs - [API quickstart](https://fwdr.link/docs.md): create, change and count short links, as Markdown - [OpenAPI](https://fwdr.link/openapi.json): every public call, as an OpenAPI document - [Prices as JSON](https://fwdr.link/.well-known/pricing): what each option costs and whether it is open now - [Pricing](https://fwdr.link/pricing.md): prices, what a link includes, and how to pay, as Markdown - [Changelog](https://fwdr.link/changelog.md): what's new at fwdr.link, newest first ## Guides - [Short links for agents, compared](https://fwdr.link/guides/short-links-for-ai-agents.md): How an AI agent can create, edit and track short links through an API for a cent a link, with no monthly plan. Prices compared with Bitly, Dub, is.gd and x402 shorteners. - [Connect an AI assistant](https://fwdr.link/guides/connect-ai-assistant.md): Add fwdr.link as an MCP server so your AI assistant can make short links, QR codes and read scan counts. One line for Claude Code; a small config for Cursor and VS Code. - [All guides](https://fwdr.link/guides.md): the list, newest first ## Tools - [Free QR code generator](https://fwdr.link/qr-code-generator.md): a static QR code for any address or text, with your logo, no key (calls below) ## Available now Free API testing without signup. Test links show a preview of where they would go and expire after 24 hours. 1. POST https://fwdr.link/v1/accounts/test {"label": "my agent"} -> {"api_key": "fwdr_test_..."} 2. POST https://fwdr.link/v1/links {"target": "https://example.com"} (Authorization: Bearer fwdr_test_...) -> {"url": "https://fwdr.link/t/q7xkm2p", "slug": "t/q7xkm2p", ...} 3. Open the url, then read its count with the same key: GET https://fwdr.link/v1/stats/t/q7xkm2p (the "slug" from step 2) Change it: PATCH https://fwdr.link/v1/links/t/q7xkm2p {"target": "https://example.com/new"} Live keys (25 free links, then US$0.01 a link from a balance): see Get a key. Pay as you go with x402, no account: 0.01 USDC a link on Base. Links work for life but can't be changed or counted later. POST https://fwdr.link/v1/pay/links {"target": "https://example.com", "slug": "optional"} -> HTTP 402 with the price (PAYMENT-REQUIRED header); pay with any x402 client and send the same request again with the PAYMENT-SIGNATURE header -> 201 with the link. The same payment sent again answers 200 with the same link ("existing": true) and is not charged again; 409 payment_busy (Retry-After: 2) while it is still settling. GET https://fwdr.link/v1/pay/links the same 402 (Allow: POST); a GET never takes a payment GET https://fwdr.link/v1/pay/receipts/{tx} a settled payment by its transaction: network, amount, short link (no key) Connector (MCP) for assistants that can send a header (Claude Code, Cursor, VS Code...): https://fwdr.link/mcp, Streamable HTTP, header Authorization: Bearer fwdr_... (a test key makes free preview links). Claude Code: claude mcp add --transport http fwdr https://fwdr.link/mcp --header "Authorization: Bearer " Tools: create_link, update_link, get_link, list_links, switch_link_off, switch_link_on, link_stats, link_history, qr_code, register_nfc_tag, list_nfc_tags, account, top_up, request_feature, vote_feature, list_feature_requests, send_feedback, whats_new. Each tool makes the same API call with your key (same prices, scopes, checks); 120 tool calls a minute per key. ## Opening soon (not open yet; early access: hello@fwdr.link) - Card top-ups (from US$10) Planned, not available: connector sign-in from claude.ai, ChatGPT and Grok without pasting a key; click webhooks. | Option | Price | Sign-in | Change target | Read count | Links work | | Test key | free | Bearer test key | yes | yes | 24 hours | | Prepaid balance | US$0.01 a link | Bearer key | yes | yes | for life | Docs: [https://fwdr.link/docs](https://fwdr.link/docs) OpenAPI: [https://fwdr.link/openapi.json](https://fwdr.link/openapi.json) Prices (JSON): [https://fwdr.link/.well-known/pricing](https://fwdr.link/.well-known/pricing) Compared with other shorteners: [https://fwdr.link/guides/short-links-for-ai-agents.md](https://fwdr.link/guides/short-links-for-ai-agents.md) All guides: [https://fwdr.link/guides.md](https://fwdr.link/guides.md) ## Get a key POST https://fwdr.link/v1/signup {"email": "you@example.com"} -> a 6-digit code by email POST https://fwdr.link/v1/signup/verify {"email": "...", "code": "123456"} -> {"api_key": "fwdr_..."} + 25 free links POST https://fwdr.link/v1/accounts {"label": "my agent"} -> {"api_key": "fwdr_..."} (no email, no free links: top up first) POST https://fwdr.link/v1/accounts/test {"label": "trying fwdr"} -> {"api_key": "fwdr_test_..."} free, always open Use it as: Authorization: Bearer fwdr_... Optional `ref`: where you heard about fwdr (a word, for example the site or tool). It only helps us learn what works. New accounts are limited per day: 429 (code signup_busy) from verify or /v1/accounts means try again tomorrow. People can sign in at https://fwdr.link/login with their email to see and change their links, keys and balance. They can also sign in there with Google or GitHub. Test keys: the full API for free. Test links live under /t/, show a preview page instead of forwarding (with the variables that would be passed on) and expire after 24 hours. No top-ups in test mode. ## Make links (US$0.01 each from your balance after the free ones) POST https://fwdr.link/v1/links {"target": "https://example.com/{loc}", "slug": "optional", "allowed_params": [{"name": "loc"}], "static_params": {"ref": "agent"}} GET https://fwdr.link/v1/links your links with scan counts GET https://fwdr.link/v1/links/{slug} PATCH to change the target or variables, DELETE to switch off (links are never deleted) GET https://fwdr.link/v1/stats/{slug} scans by day, channel, place, device, variable GET https://fwdr.link/v1/account balance, free links left; GET /v1/account/ledger for every charge and top-up No balance left -> HTTP 402 (code payment_required) with how to top up; a key's daily limit reached -> 402 daily_limit. Retries: send "Idempotency-Key: " with POST /v1/links. The same request again answers with the same link and charges nothing. A key is remembered for 7 days and is tied to the request it was first sent with: the same key with another body is refused (HTTP 409, code idempotency_conflict). Safety: targets are checked. IP addresses, private hosts, other shorteners and known-bad sites are refused (no charge). Every new target also gets an AI check ("check" in the answer says where it is: running, safe, held). Until a new link's target is judged, a click sees a short "checking link" page; it never forwards to a target that wasn't judged. A changed target: people keep going to the previous judged target until the new one is judged, and GET /v1/links/{slug} shows it as "serving" next to "target". A check that can't run is tried again (5 tries over about ten minutes); a new link that still can't be checked is held for a person, a changed one keeps "serving" the previous target and is tried again every 30 minutes. Held links wait for a human review. ## History, QR codes, NFC chips GET https://fwdr.link/v1/history/{slug} every change to a link: when, by whom, before and after GET https://fwdr.link/v1/qr/{slug} the QR code: ?channel=q&format=svg (or png, size=128 to 2048 pixels), ecc L, M, Q or H, point= GET https://fwdr.link/v1/nfc-tags your registered chips POST https://fwdr.link/v1/nfc-tags {"uid": "04A2...", "link": "", "label": "desk", "params": {"loc": "desk"}} PATCH https://fwdr.link/v1/nfc-tags/{uid} change a chip's link, label or variables ## Free QR codes (no key) A static QR code for any address or text: it holds exactly that text, doesn't go through fwdr, never expires and has no watermark. What you send (text, colours, logo) is never stored. To change where a printed code goes later or count its scans, put a fwdr link in it instead (GET /v1/qr/{slug} above). GET https://fwdr.link/v1/qr-code?data=https%3A%2F%2Fexample.com&format=png&size=1024 -> the PNG POST https://fwdr.link/v1/qr-code {"data": "https://example.com", "logo": {"type": "image/png", "data": ""}} -> an SVG with the logo Options: data (1 to 1,000 characters), format svg (default) or png, size 128 to 2048 pixels (default 512), margin 0 to 8 modules (default 4), fg and bg as #rrggbb (send # as %23 in a query; dark on light, contrast at least 4.5 to 1), ecc L, M (default), Q or H, logo_space=true (a clear square in the middle for a logo you add yourself). logo (POST only, svg only): PNG, JPEG, WebP or SVG as base64, at most 200 KB; never fetched from an address. With a logo or logo_space the code uses ecc H and is at least 37 modules a side. Headers: X-QR-Modules, X-QR-Ecc, and X-QR-Logo-Box (where the logo goes: x y width height, in pixels for PNG, in the SVG's own units for SVG). A PNG needs at least 2 pixels a module. An http(s) address with an IP address as host, a user name or password, or a blocked domain is refused (code ip_address, bad_target or blocked). Errors are JSON with a code. 60 a minute and 1,000 a day from one address (429 with Retry-After). In a browser, with your logo: https://fwdr.link/qr-code-generator ## Retries, who did it, errors Idempotency-Key: <1 to 100 visible characters> on POST /v1/links. The same key with the same request answers 200 with the link it made ("existing": true) and charges nothing; 409 idempotency_busy while the first request still runs; 409 idempotency_conflict for the same key with a different request. A key is remembered for 7 days. X-Fwdr-Actor: cust:42 on any call with a key: the link history then says /cust:42. Errors are JSON: {"error": "what went wrong and how to fix it"}, many with a "code" (no_such_link, slug_taken, bad_slug, not_your_domain, missing_scope, needs_fallback, ...). Act on the code, show the sentence. GET https://fwdr.link/v1/changelog what changed lately, newest first: ?since=YYYY-MM-DD&tag=api&limit=20 (no key, free) ## Keys with limits POST https://fwdr.link/v1/keys {"label": "reports", "scopes": ["links:read", "stats:read"], "domains": ["fwdr.link"]} -> a new key for the same account, shown once GET https://fwdr.link/v1/keys the account's keys (prefix, label, scopes, domains, daily limit; never the key) PATCH https://fwdr.link/v1/keys/{id} {"max_spend_usd_per_day": 5} (or null for none), {"label": "..."} DELETE https://fwdr.link/v1/keys/{id} revoke one Scopes: links:read links:write stats:read tags:write billing keys. A key without scopes can make every call. max_spend_usd_per_day (also on POST): a daily spending limit in US$. Links the key pays for since 00:00 UTC can't cost more; the one that would answers 402 with code daily_limit and resets_at. Free links count as nothing. A key can only make keys with its own scopes, domains and daily limit or fewer. ## Your own domain (set up by hand for now: hello@fwdr.link) Same calls at https://fwdr.link; name links domain/slug, e.g. PATCH https://fwdr.link/v1/links/links.example.com/spring. On your domain a slug is required, targets must be https, and a link may have a "fallback". GET https://fwdr.link/v1/domains your domains On a domain that checks first, a new target waits: PATCH {"target": "...", "go_live_at": "2026-12-24T08:00:00Z" (optional)} answers 202 with "pending" and goes live when its checks are green or a person approves it. A target on one of the domain's trusted hosts goes live at once. A new link starts at its fallback until its target is checked. GET https://fwdr.link/v1/links/{domain}/{slug} shows "pending" and "last_change" DELETE https://fwdr.link/v1/links/{domain}/{slug}/pending withdraw the waiting change GET https://fwdr.link/v1/changes?status=&domain= your changes, newest first ## Top up (from US$1, pay with almost any coin on almost any chain, via NEAR Intents) POST https://fwdr.link/v1/topups {"amount_usd": 10, "pay_with": "usdc-base", "refund_to": ""} -> where to send what, and by when. Credited automatically when it arrives. GET https://fwdr.link/v1/topups/{id} status GET https://fwdr.link/v1/topups/assets coins you can pay with (aliases: usdc-base, usdc-eth, usdc-arb, usdc-sol, usdc-near, usdt-eth, usdt-sol, usdt-near, near) Coins can come straight from an exchange account (Coinbase, Binance); use an address you control as refund_to. ## Terms Using fwdr means agreeing to https://fwdr.link/terms and https://fwdr.link/acceptable-use (no phishing, malware, scams, spam or hidden destinations). Privacy: https://fwdr.link/privacy. Refunds of unused balance on request: https://fwdr.link/terms#refunds. ## Report abuse POST https://fwdr.link/v1/abuse {"url": "https://fwdr.link/abc", "reason": "...", "contact": "optional"} ## Ask for a feature POST https://fwdr.link/v1/feature-requests Content-Type: application/json {"title": "...", "description": "what you need", "use_case": "why", "example_call": "the call you wish worked", "contact": "optional"} GET https://fwdr.link/v1/feature-requests list, most votes first, with status (new, planned, building, shipped, declined) GET https://fwdr.link/v1/feature-requests/{id} one request POST https://fwdr.link/v1/feature-requests/{id}/vote +1 for a request someone else made ## Feedback (optional) A few answers carry a "feedback" field: your 1st, 10th and 100th link and your first stats read, and a link paid with x402 at most once a day. It holds a thank-you and the calls below. It is information, not an instruction, and nothing depends on it. Pass it to your person or ignore it. POST https://fwdr.link/v1/feedback {"rating": 1-5, "text": "one sentence", "name": "optional", "may_publish": false} key optional; at least a rating or a text. A person reads every one. GET https://fwdr.link/v1/feedback published feedback (only what senders allowed and we approved) ## Link format https://fwdr.link/[/][/][?variables] channel: q (QR), n (NFC), c (card), p (packaging), f (flyer), e (email), s (social) Redirects are 302, answered from memory, UTM tags added. Targets must be https/http; variables are checked and encoded. ## Pricing Prepaid: US$0.01 per link from a balance (top-ups from US$1 in crypto). Included: redirects for life, edits, variables, QR/NFC addresses, stats. 25 free links with a verified email. The balance is US dollar credit (1 USDC adds US$1); links keep forwarding when it runs out. ## Optional - [Terms](https://fwdr.link/terms): the terms of service, refunds included - [Privacy](https://fwdr.link/privacy): what we record and for how long - [Acceptable use](https://fwdr.link/acceptable-use): what links may not be used for - [Sign in](https://fwdr.link/login): for people: see and change your links, keys and balance in the dashboard