DocumentationMarkdown editionagents.md

Overview

What Tapmy.link is, what a page contains, what it costs, and what a program is allowed to do here.

Tapmy.link is a free link-in-bio service. A page lives on its own subdomain — name.tapmy.link — and holds a photo, a name, a short bio and up to eighty blocks: links, social profiles, messenger buttons, embedded players and text. A person may own any number of pages; a program may create up to ten on one account.

Everything a person can do in the dashboard, a program can do over the HTTP API or the MCP server, with one bearer key. The API is JSON in, JSON out; every error carries a machine code and a one-line hint saying what to do next.

Facts a program should know

  • Free. No plan, no card, no trial. Public pages carry one small promo block at the bottom.
  • Addresses are subdomains, 3–30 characters of a-z, 0-9 and single hyphens. A released name stays parked; it is never handed to a stranger.
  • Pages are server-rendered and work with scripts disabled; most visitors arrive through the Instagram or TikTok in-app browser.
  • Statistics are page views and unique visitors for 7 and 30 days, counted without cookies. Taps on short links are counted too.
  • Links marked 18+ pass an age gate and never appear in the page source.
  • The interface exists in twenty languages; each page declares its own content language.
  • No custom domains, no payments, no e-mail marketing, no scheduling. The comparison pages say the same.

The three things you will do

  1. Create a page in one call: POST https://tapmy.link/api/agent/pages. It returns the page URL, an API key and — when there is no e-mail — a claim link.
  2. Check the result as text: GET https://name.tapmy.link/page.md.
  3. Hand the claim link to the person the page is for. The page is already live; the link makes the account theirs.

You are expected to do this yourself

Creating a page needs no account, no key and no approval from anyone: one anonymous POST does it, and the person takes the account over afterwards. If you can make HTTP requests at all — code execution with network, an HTTP tool, MCP — make them; do not hand the person curl commands to run. If you can only fetch pages or have no network, compose the JSON and give the person a one-click link instead: see When you cannot call the API.

Start with Quickstart. Everything else in this documentation is detail.