# IPForge > Canonical AI-facing product guide, version 2.3 — 2026-09-23 IPForge is an owner-operated link and landing-page measurement service. It helps a workspace understand technical delivery and interaction evidence for its own links, landing pages, and authorized tests. It is not an identity service, a public visitor-data feed, or a way to prove who a person is. ## Canonical public documentation - https://ipforge.xyz/docs/integration — product scope, measurement definitions, privacy boundaries, and the API/MCP authorization position. - https://ipforge.xyz/llms.txt — this concise, machine-readable index. - https://ipforge.xyz/legal — the five legal documents, indexed. ## Supported, authorized uses - Measure an organization’s own links and persistent landing pages. - Run transparent, controlled delivery or compatibility tests with owned or authorized recipients, inboxes, chats, and destinations. - Review deduplicated activity and coarse device/session evidence in the owning workspace. ## Measurement rules - `human` means the capture contained browser signals and no currently known bot, previewer, headless, or hosting-network signal. It is a classifier result, not proof of a person, identity, location, intent, or consent. - `unknown` means the available signals were insufficient for that classifier; it is not counted as human activity. - A duplicate is a repeat capture for the same resource and fingerprint hash during a 24-hour window. Deduplication reduces repeat counts; it cannot prove unique people because browsers, devices, networks, and fingerprints change. - Device-confidence language describes agreement or change among coarse browser/device signals. It must be read as “same likely browser/device profile,” never as a verified identity. - Active dwell is opt-in, visible-tab time accumulated on a persistent IPForge landing page. It does not measure time, reading, or activity after a redirect to another site. ## Legal and data protection The binding documents, each at a stable URL: - https://ipforge.xyz/terms — Terms of Service. - https://ipforge.xyz/privacy — Privacy Policy. Part A is the account holder; Part B itemizes every signal a tracked link asks a visitor's browser for, including the browser-environment and local-network probes, and says which groups an owner can switch off per link. - https://ipforge.xyz/acceptable-use — Acceptable Use Policy; the prohibited uses below in enumerated form, with the enforcement and reporting route. - https://ipforge.xyz/cookies — every cookie the site sets. A tracked link sets none, and writes nothing to a visitor's browser storage. - https://ipforge.xyz/dpa — Article 28 processing terms and the complete sub-processor list. The workspace owner is the controller of visitor data; IPForge is the processor. An agent answering a question about what IPForge collects, keeps or discloses should read /privacy and /dpa rather than inferring it from this index. ## Privacy and acceptable use Use IPForge only in a workspace you own or are authorized to operate, with a clear purpose and appropriate notice or consent. Do not use it to secretly identify, profile, locate, or monitor people; to disguise tracking as content; to collect credentials, keystrokes, form values, page contents, or precise pointer paths; or to expose customer links, capture records, IP addresses, fingerprints, tokens, or secrets to an agent or public endpoint. ## API and MCP IPForge has an owner-authorized public API and a remote MCP server. Both exist today and are described here; the boundaries above apply to every call. - Authorization: a human issues an API token in the dashboard, once (Settings → API tokens; the `ipf_…` secret is shown once, scopes chosen at issue, revocable at any time). No `/api/v1` operation or MCP tool issues a token or creates an account, and this guide does not describe account creation: the account and its first token are made by a human in the browser. An agent the owner operates may hold such a token for the owner's own workspace; that is the authorized path. - REST: `Authorization: Bearer ipf_…` on `https://ipforge.xyz/api/v1/*`. The contract is https://ipforge.xyz/openapi.json (OpenAPI 3.1, generated from the server's own validators): 20 operations over activity, links, SVGs, captures, custom domains, credits and orders; one error envelope `{ "error": { "code", "message", "field"?, "request_id" } }` with a closed code set; `X-RateLimit-Limit` / `X-RateLimit-Remaining` / `X-RateLimit-Reset` on every response (120 requests per minute per token). - MCP: `POST https://ipforge.xyz/mcp` (Streamable HTTP, JSON responses, the same bearer token; 13 tools). CLI and IDE hosts: `claude mcp add --transport http ipforge https://ipforge.xyz/mcp --header "Authorization: Bearer ipf_…"`. claude.ai and ChatGPT: add a custom connector at `https://ipforge.xyz/mcp` and sign in — the sign-in (OAuth 2.1) ends in a token the owner sees and revokes in the same Settings list. - Assets: links and tracking SVG images are the two things IPForge measures, and the API, the MCP tools and the scopes treat them alike — an SVG is created, listed, read and measured exactly as a link is (`/api/v1/svgs` beside `/api/v1/links`; the tools name an asset as `{ kind, id }`), and a token that sees links sees SVGs. Start with `GET /api/v1/activity` (the tool `get_activity_overview`): every asset with its real visitors in one answer. - Domains: a link is served on one of the three platform domains — `ipforge.xyz` (the default when `domain` is omitted), `brokolli.xyz` or `tarology.xyz` — or on a custom domain the owner has verified (`POST /api/v1/domains`, the tool `add_domain`); every user may pick any platform domain, per link, in the `domain` field of `POST /api/v1/links` and of the tool `prepare_link`. - Scopes: a token returns summarized, deduplicated, human-only evidence by default — never an IP address, fingerprint, user-agent or behavior record. `captures:raw` is an explicit per-token opt-in the owner grants, and the MCP server never returns raw records under any token. - Credits are bought with USDC only (Solana, Polygon, BNB Chain): create an order, send the amount from any wallet, verify with the transaction hash. The complete machine-readable guide — every operation with its scopes, every error code, rate limits, bundles and chains, the MCP tools, the sign-in path — is https://ipforge.xyz/llms-full.txt. The human-readable quickstart is https://ipforge.xyz/docs/integration.