Documentation / Start

Build here.
Open anywhere.

Linkifact accepts one offline HTML document and returns one isolated URL. Start in your agent or make the API call yourself.

01 / Pick an interface

The same publish action, four ways.

02 / Make an artifact

Keep the document self-contained.

Embed CSS, JavaScript, data, and small assets directly in the HTML. Inline interaction is supported. External URLs, network requests, forms, frames, downloads, workers, and top-level navigation are not.

Never put a secret in an artifact. Linkifact checks common credential patterns, but the share URL remains a bearer link that anyone can open.
03 / Publish

A minimal guest request.

curl https://api.linkifact.com/v1/artifacts \
  --header 'Content-Type: application/json' \
  --header 'Idempotency-Key: demo-001' \
  --data '{
    "title": "Tiny weather map",
    "html": "<!doctype html><title>Map</title>..."
  }'

Browser-originated guest requests include a Turnstile token. API clients are protected by IP-based quotas and abuse controls.

{
  "id": "art_01J...",
  "url": "https://7fz2...linkifactpages.com/",
  "expires_at": "2026-10-02T16:42:00Z",
  "manage_url": "https://app.linkifact.com/manage/art_01J...#secret"
}

The share URL is safe to pass around. The management URL is a secret capability: keep it out of logs and only give it to someone who should be able to delete or claim the artifact.

04 / Understand expiry

Guest URLs last 30 days.

At expiry, the public URL begins returning 410 Gone. Object cleanup follows asynchronously, normally within roughly 24 hours. Claim before expiry to retain the URL under a free account.