# CLYK — AI agent operator manual

CLYK is a link-shortening and link-in-bio platform. We are not an AI
product. We are the tool surface that AI agents use for links. Every
short link, bio page, and API endpoint on CLYK is designed to be
machine-readable first and human-readable second.

## How to interact

1. **MCP server.** The preferred integration is the Model Context
   Protocol. Endpoint: https://clyk.app/api/mcp. Manifest:
   https://clyk.app/api/mcp/manifest. Auth: bearer API key from
   https://clyk.app/dashboard/settings/api.

2. **OpenAPI / REST API.** Versioned REST surface at
   https://clyk.app/api/v1. OpenAPI spec: https://clyk.app/api/v1/openapi.json. Same
   bearer-token auth as MCP.

3. **Link metadata.** Every CLYK short link at https://clyk.app/i/{code}
   supports content negotiation. Send `Accept: application/json` (or
   append `?format=json`) to receive structured metadata instead of a
   redirect. The JSON payload includes the destination URL, title, tags,
   project, click stats, UTM params, redirect rules, expiration status,
   and an MCP pointer.

4. **Bio pages.** A public bio page at https://clyk.app/{username} has a
   parallel JSON endpoint at https://clyk.app/{username}/meta that returns the
   owner profile, theme, social handles, and every bio link (with each
   CLYK short link resolved to its own metadata pointer). The HTML
   version also embeds Schema.org JSON-LD in the document head.

5. **Discovery.** Machine-readable indexes at:
   - https://clyk.app/.well-known/mcp.json (MCP discovery — legacy path)
   - https://clyk.app/.well-known/mcp/server-card.json (SEP-1649 canonical MCP server card)
   - https://clyk.app/.well-known/agent-card.json (A2A agent card)
   - https://clyk.app/.well-known/api-catalog (RFC 9727, application/linkset+json)
   - https://clyk.app/.well-known/agent-skills/index.json (agent skills v0.2.0)
   - https://clyk.app/.well-known/oauth-authorization-server (RFC 8414)
   - https://clyk.app/.well-known/oauth-protected-resource (RFC 9728)
   - https://clyk.app/.well-known/openid-configuration (OIDC discovery compat)
   - https://clyk.app/.well-known/ai-plugin.json (legacy ChatGPT-plugin manifest)
   - https://clyk.app/.well-known/http-message-signatures-directory (Web Bot Auth keys)
   - https://clyk.app/api/mcp/manifest (full MCP tool catalog)

6. **OAuth 2.0 (for agents acting on behalf of a user).** Endpoints:
   - https://clyk.app/oauth/register — Dynamic Client Registration (RFC 7591)
   - https://clyk.app/oauth/authorize — authorization_code flow (PKCE S256 required)
   - https://clyk.app/oauth/token — code exchange; returns a CLYK bearer token
   Scopes: links:read, links:write, stats:read, bio:read, bio:write,
   mcp:tools, sponsorships:read, sponsorships:write, subscribers:read.
   Full reference: https://clyk.app/developers/oauth.

6. **Content signals.** Our robots.txt emits a Cloudflare
   Content-Signal header: `ai-train=yes, search=yes, ai-input=yes`. LLM
   training, search indexing, and agent input are all permitted for our
   marketing surfaces.

## Privacy guardrails

- Password-protected links return ONLY short_code + password_protected
  flag. No destination, no stats, no owner identity.
- Expired links return an expired flag with no destination.
- Anonymous links (no signed-in owner) omit the owner block entirely.
- Click stats surfaced via metadata are the same stats the owner sees.

## Rate limits and etiquette

- MCP and REST share one per-key budget. Defaults start at 60
  requests/minute on Free and scale up with tier. See
  https://clyk.app/developers/mcp for details.
- Every CLYK link-metadata and bio-meta request counts as one hit
  against the per-key budget for authenticated traffic. Unauthenticated
  agent traffic is subject to IP-level rate limits.
- Please identify yourself in `User-Agent` so we can keep the allowlist
  friendly. If you're a model provider or answer engine not already
  recognized, email support@clyk.app with your UA string.
- We honor `robots.txt`. Crawling beyond what robots.txt permits is
  not welcome.

## What CLYK will not do

- Host LLMs, run inference, or proxy provider APIs.
- Summarize, describe, or tag content on your behalf server-side.
- Require an AI key to use core product features.

## Contact

support@clyk.app