Bot intelligence record

Link CLI

Review first

Link CLI is a signed-agent identity used to recognize Link automated browser or AI-agent traffic in Botcrawl logs. The importable Botcrawl identifier is link-cli.

Ai Agent Payment Workflow Traffic Where Users Approve Purchases Or Spending Actions Through Link. Signed Agent Confidence: High Verified: Yes robots.txt: Unknown
Operator
Link
Family
Link CLI
Type
Ai
Source type
Official
Last checked
2026-06-22

User-Agent Pattern

Link
link-cli
Verification note

User-agent strings are identification signals, not proof of identity. Confirm important allow, block, or rate-limit decisions with logs, DNS or IP evidence, request behavior, or operator documentation when available.

Robots.txt Snippet

Click snippet to copy 
User-agent: link-cli
Disallow: /

Click the snippet to copy it, or highlight the text manually.

Handling Guidance

Depends

Use this record as bot intelligence, then verify the request source and behavior before allowing, blocking, or rate limiting.

Agent payment workflow traffic where users approve purchases or spending actions through Link.

Record Details

Structured data
Operator
Link
Family
Link CLI
Type
Ai
Purpose
Agent Payment Workflow Traffic Where Users Approve Purchases Or Spending Actions Through Link.
Identity type
Signed Agent
Confidence
High
Last verified
2026-06-22
Last checked
2026-06-22
Source type
Official
Verification
HTTP Message Signatures / Web Bot Auth; verify Signature, Signature-Input, and Signature-Agent headers when available.
Spoofing risk
Medium when matched by identifier only; lower after signed-agent verification succeeds.

Notes

Link CLI is a Botcrawl signed-agent identity for automated traffic associated with Link. The importable Botcrawl identifier is link-cli.

Identification

  • Botcrawl identifier: link-cli
  • Operator: Link
  • Family: Link CLI
  • Type: AI agent / browser automation
  • Identity model: signed-agent identity
  • Supporting identifiers: link-cli; Signature-Agent key directory: https://api.link.com/.well-known/http-message-signatures-directory

Common use

Agent payment workflow traffic where users approve purchases or spending actions through Link.

Verification and handling

This identity is best handled as a signed-agent or managed browser identity, not as a traditional fixed HTTP user-agent crawler. For Edge enforcement, match the Botcrawl identifier and verify supporting request signals when available, including Signature, Signature-Input, Signature-Agent, managed bot identifiers, request headers, operator documentation, IP ownership, and observed behavior. Do not treat the identifier alone as cryptographic proof because plain identifiers can be copied.

Botcrawl marks this as normal-risk traffic by default. Monitor or allow when it is expected, rate-limit if it creates load, and block when the activity is unwanted or unverifiable.

Reference: operator documentation.

Evidence and Source

  • HTTP Message Signatures / Web Bot Auth; verify Signature, Signature-Input, and Signature-Agent headers when available.
  • Importable Botcrawl signed-agent identity. This row intentionally uses the Botcrawl identifier in bot_user_agent because the current importer requires a non-empty identifier; it is not a claim that the agent always sends a fixed traditional HTTP User-Agent string.
  • Agent payment workflow traffic where users approve purchases or spending actions through Link.
  • Medium when matched by identifier only; lower after signed-agent verification succeeds.

https://link.com/agents

Monitor This Bot In Edge

Botcrawl Edge

Use Botcrawl Edge to see matching traffic, create allow or block rules, and control this bot across connected sites.

Get Edge Now Open In BotDB