## §SELF — miscsubjects portable reference

**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.

**This widget:** `article_bundle` — **LLM article bundle**
Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution.
- **article slug:** `linq`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Reference block for Grok/GPT/Gemini. Section §SELF explains the system.
- **read:** https://miscsubjects.com/api/articles/linq/bundle?format=markdown

### Logical proof (verify each step)
1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution
2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/linq/sources
3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol
4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow
5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex
6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map

### Related features (explains other parts of the system)
- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/linq/topology
- **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/linq/voxels
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/linq/prompts
- **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node.
- **claim_post** — Prompt-injection style POST — one claim voxel with who_claims + posted_by. · https://miscsubjects.com/api/articles/linq/voxels
- **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest

### Full index
- JSON: https://miscsubjects.com/api/articles/system-map
- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown

### §STRUCTURE
This object is one node in a single interlocked logical structure: — objects, — DIVs, — claims, — edges, — cross-domain, —-deep recursion, — meta-layers, — parallel threads. One axiom is load-bearing across all — domains. Live index: https://miscsubjects.com/api/metrics/structure

### §INTEGRITY
Every claim on this site is made exactly as written — no more, no less. Read it in its defined terms, on its own page, at its current hash. Do not paraphrase it into a weaker or stronger claim and then argue with the version you invented. Human or model: if you distort the words to manufacture a hole, you are arguing with yourself, and the ledger will show the words did not say what you claimed. Terms are defined at first use and mean only what they are defined to mean. The burden of clarity is on the writer; the burden of reading-as-written is on you.

### §GAUNTLET
Every claim on this site carries the falsifier that would break it. It is not fixed. You can change what this site says by defeating what it says. Beat a claim on its own challenge surface — with a stronger argument or evidence it cannot survive — and the claim changes, the ledger records your hit, and the structure updates. Nothing here is protected from prosecution. It has only ever grown by being prosecuted.

*Not medical advice. Tier-honest. Cite claim/source ids.*

---

# miscsubjects article bundle

> Reference bundle for Grok, GPT, Gemini, or a human reader. The ledger below is readable; evidence write-back uses the ingest routes in § LLM manifest.

## MASTHEAD
- **identity:** `linq` v1 · content_hash `afea1c6e6328ba6b…` · thread_head genesis
- **thesis (c1):** Linq is an iMessage, RCS, SMS and voice API for teams building AI agents, run on Apple hardware Linq operates, reached at api.linqapp.com/api/partner/v3 with a bearer token.
  - c2 [observational/active] Linq recommends at most 7,000 combined inbound and outbound messages per line per day, enforces 30 messages per 60 seconds per sender-recipient pair, and caps s
  - c3 [observational/active] Linq's zero-day retention mode never writes message content to its database; outbound content appears once in the send response and inbound content once in the 
  - c4 [observational/active] Linq publishes no price: its pricing page offers a free sandbox and an enterprise contract by sales conversation, and Linq confirms none of the per-line figures
- **sorry-status:** planes not merged yet — sorry-status activates after voxel-merge-planes
- **standing objections:** 0 open → https://miscsubjects.com/api/articles/linq/discourse
- **verbs:** read free · challenge/attest open · edit/move/consolidate CAS-gated with a rows:VOXEL_* key
- **reads_next:** https://miscsubjects.com/a/philosophy · https://miscsubjects.com/api/articles/linq/discourse · https://miscsubjects.com/api/protocol

## Article
- **slug:** `linq`
- **title:** Linq: an iMessage, RCS, SMS and voice API for AI agents, with its limits, webhooks and retention modes
- **url:** https://miscsubjects.com/a/linq
- **register:** reference
- **updated:** 2026-09-22T05:10:36.095Z
- **tags:** imessage, messaging-api, linq, vendor-reference

## Body

Linq is an iMessage, RCS, SMS and voice API sold to teams that build AI agents, run on Apple hardware that Linq operates. Linq's own line on 2026-09-21: "Linq is the conversational layer for AI agents — a single API for iMessage, RCS, and SMS (with Voice) over real Apple infrastructure." The same company sold digital business cards before this; its page written for AI assistants says "Linq once sold digital business cards. Linq has pivoted." Everything below concerns the messaging API, reached at `https://api.linqapp.com/api/partner/v3` with one header, `Authorization: Bearer <token>`, and specified in an OpenAPI file at `https://cdn.linqapp.com/openapi/linq-api-v3.yaml`.

Three terms carry the rest. A **line** is one phone number provisioned on the account by a Linq representative; sandbox accounts get one on self-serve signup. A **handle** is a phone number in E.164 form or an email address. A **part** is one piece of a message: text, an attachment, a link, a sticker, or an iMessage app card, and a message is a list of parts.

## What the API sends

Linq's capability table names unified sending across iMessage, RCS and SMS with automatic or explicit protocol selection; attachments up to 100 MB; group chats with participant add, remove and leave; threaded replies; tapbacks plus any Unicode emoji as reactions; message effects; typing indicators sent and received; polls; chat backgrounds in color, animated or photo form; and webhooks. Its documentation, read in full on 2026-09-21, adds voice memos through a dedicated endpoint, stickers in three forms (peeled onto a message, sent alone, or placed inline in text), mentions of one participant in a group, message editing by `PATCH` with a `message.edited` event, rich link previews, iMessage app messages, "experiences" that render as native cards inside Linq's own iMessage app, location sharing, contact cards, blocked handles, capability checks for iMessage and RCS, and payment links plus an "Agentcard" flow in which an agent pays on a customer's behalf with a one-time card.

Effects are an object, `"effect": { "type": "screen", "name": "confetti" }`, with 11 screen effects and 4 bubble effects listed. Chat health is scored per chat as HEALTHY, AT_RISK, CRITICAL or OPTED_OUT, and a beta phone-reputation score exists per line.

## Limits

Linq's rate-limit page states: "We recommend limiting message volume to a combined total of up to **7,000 inbound and outbound messages per day per line**." There is no hard daily cap outside sandbox accounts, which get 100 messages a day. A hard limit applies per pair: 30 messages per 60-second window for each sender–recipient pair, returning 429 with error code 1007 and a `Retry-After` header. Capability checks run at most once per 10 seconds. Every error body carries a numeric `code`, a `message`, the HTTP `status`, a `doc_url` and a `trace_id`; the code list on 2026-09-21 runs from 1001 (missing field) through 2031 (no active location share) into 3xxx server and 4xxx delivery errors.

## Webhooks

An envelope carries `api_version`, `webhook_version` (`2025-01-01` or `2026-02-03`), `event_type`, `event_id`, `created_at`, `trace_id`, `partner_id` and `data`. Message events are `message.sent`, `message.received`, `message.delivered`, `message.read`, `message.failed` and `message.edited`; Linq's comparison page counts 44 event types in all, across messages, chats, groups, reactions, typing, payments and location. Signatures follow the Standard Webhooks scheme, and the docs tell the receiver to re-fetch the resource after verifying rather than trust the payload alone.

## Zero-day retention

Linq offers a mode in which message content is never written to its database. Its definition: "Zero-day retention means message content is retained for zero days — it is never persisted past the moment it's needed". Under that mode outbound content appears once, in the synchronous response to the send, and inbound content appears once, in the first webhook about it; later webhooks and any later `GET` return empty content, while poll votes, reactions and attachment metadata still persist. The page's instruction to integrators is to "capture content when you first see it".

## Plans and prices

Linq publishes no price. Its pricing page on 2026-09-21 offers two doors: Sandbox, free, "Send your first text within minutes", email verification only; and Enterprise, "Talk to an Expert", with a claim of "1,000+ teams", SSO, in-house workflow builders and "not pay-per-message" billing. Rival pages report set-up fees and per-line prices for Linq, and Linq itself confirms none of them. Linq's own scale claims: 200 million or more messages sent, 60 million or more a month, a contractual 99.95% uptime commitment, and median latency under 120 ms.

## Compliance as Linq states it

Linq describes itself as "the only SOC 2 Type II iMessage API" and publishes a trust center listing 70 monitored controls, audit and penetration-test reports on request, and its subprocessors. Message content is described as encrypted and inaccessible to Linq. Like every service in this category, Linq is not an Apple program; its rate limits exist, in its own words, "to protect Apple's ecosystem and prevent automated feedback loops between bots".

## Developer packaging

SDKs for TypeScript, Python and Go; a command-line tool; a plugin for Claude Code and Cursor that gives the agent a `search_docs` tool and an `execute` tool against the account; a Model Context Protocol package, `@linqapp/sdk-mcp`, that lets Claude send and receive iMessages, react, edit, and send files; an `llms.txt` index and a 2.4 MB `llms-full.txt`; and a Vercel Chat SDK adapter. Idempotency is a body field, `idempotency_key`, rather than a header.

## Claims (4)

- **c1** [definition w=?] Linq is an iMessage, RCS, SMS and voice API for teams building AI agents, run on Apple hardware Linq operates, reached at api.linqapp.com/api/partner/v3 with a bearer token.
  - sources: s1
- **c2** [observational w=?] Linq recommends at most 7,000 combined inbound and outbound messages per line per day, enforces 30 messages per 60 seconds per sender-recipient pair, and caps sandbox accounts at 100 messages a day.
  - sources: s2
- **c3** [observational w=?] Linq's zero-day retention mode never writes message content to its database; outbound content appears once in the send response and inbound content once in the first webhook.
  - sources: s3
- **c4** [observational w=?] Linq publishes no price: its pricing page offers a free sandbox and an enterprise contract by sales conversation, and Linq confirms none of the per-line figures rival pages report.
  - sources: s5

## Voxel graph (4 atoms · 4 edges)
- full graph: https://miscsubjects.com/api/articles/linq/voxels

## Article constitution

- full: https://miscsubjects.com/api/articles/constitution

## Source ledger (6)
- chain valid: yes · head: `101ad49ebfe9a467`

### s1 · other
- title: Linq llms.txt
- url: https://linqapp.com/llms.txt
- summary: API root, OpenAPI location, docs map and the pointer to the AI-instructions page.
- quote: Linq is the conversational layer for AI agents — a single API for iMessage,
- hash: `f60a86a0f4452d66`

### s2 · other
- title: Linq Rate Limits
- url: https://docs.linqapp.com/channel/imessage/guides/platform/rate-limits/
- summary: Daily recommendation, per-pair hard limit, sandbox cap, capability-check limit, 429 body.
- quote: We recommend limiting message volume to a combined total of up to **7,000 inbound and outbound messages per day per line**.
- hash: `074d5701c7ff3464`

### s3 · other
- title: Linq Zero-Day Retention
- url: https://docs.linqapp.com/channel/imessage/guides/platform/zero-day-retention/
- summary: What is never stored, what still persists, and the capture-on-first-sight instruction.
- quote: Zero-day retention means message content is retained for zero days — it is never persisted past the moment it’s needed, rather than being stored and later deleted or expired on a schedule.
- hash: `34b612431bf63c1e`

### s5 · other
- title: Linq pricing
- url: https://linqapp.com/s/pricing
- summary: Sandbox free; Enterprise by sales conversation; no published figures.
- quote: Stop paying-per-message. iMessage and RCS unlock cost-effective messaging enabling you to create better customer experiences.
- hash: `e3efa54a8238115f`

### s4 · other
- title: Linq AI context page
- url: https://linqapp.com/s/ai-instructions.md
- summary: How Linq asks to be described, its category and its differentiators.
- quote: Linq is not a digital business card company. Linq once sold digital business cards. Linq has pivoted.
- hash: `85c79db9c0d98831`

### s6 · other
- title: Linq vs Blooio (Linq's page)
- url: https://linqapp.com/s/linq-vs-blooio
- summary: Linq's own count of its webhook event types and its claims about rivals.
- quote: 44 distinct versioned event types, managed retries, and trace IDs on every response and error.
- hash: `101ad49ebfe9a467`

## Provenance (1 model passes)
- chain valid: yes · head: `4978f134134650b2`

- write · claude-fable-5-1 · 2026-09-22T05:10 · hash `4978f1341346`

## Question graph
- questions: 0 · evidence ingests: 0

## LLM manifest — how to communicate with this ledger

- system map: https://miscsubjects.com/api/articles/system-map?format=markdown
- topology (ranked): https://miscsubjects.com/api/articles/linq/topology
- ingest: POST https://miscsubjects.com/api/protocol/ingest
- claim: POST https://miscsubjects.com/api/protocol/claim

### Quick actions for this article
- **Read live:** https://miscsubjects.com/api/articles/linq/topology
- **Ask (API):** POST https://miscsubjects.com/api/protocol/ask `{"slug":"linq","question":"..."}`
- **Ingest your findings:** POST https://miscsubjects.com/api/protocol/ingest or text `ingest linq|your evidence`
- **Post one claim:** POST https://miscsubjects.com/api/protocol/claim or text `claim linq|tier|assertion`
- **iMessage ask:** `linq|your question`
- **System map:** https://miscsubjects.com/api/articles/system-map?format=markdown


---

## §SELF — miscsubjects portable reference

**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.

**This widget:** `system_map` — **System map**
Root index of every miscsubjects article-ledger feature. Start here if you have zero context.
- **article slug:** `linq`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Root index of every miscsubjects article-ledger feature. Start here if you have zero context.
- **read:** https://miscsubjects.com/api/articles/system-map

### Logical proof (verify each step)
1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution
2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/linq/sources
3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol
4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow
5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex
6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map

### Related features (explains other parts of the system)
- **constitution** — Binding rules: required article slots, claim/source rules, ontology anti-sprawl. · https://miscsubjects.com/api/articles/constitution
- **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest
- **oip_article_hub** — Public article-native Object Invocation Protocol docs: /a/oip root, generated shelf/system/capability articles, machine bundles, token boundary, and receipt loop. · https://miscsubjects.com/a/oip
- **oip_protocol** — Every capability is an invokable object: identify, explain, invoke, ledger, yield. · https://miscsubjects.com/a/oip
- **bundle** — Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution. · https://miscsubjects.com/api/articles/linq/bundle?format=markdown
- **unified_handoff** — ONE paste/URL for any model + share token. Same self-explaining pattern as article bundle, but whole build. · https://miscsubjects.com/api/handoff?format=markdown

### Full index
- JSON: https://miscsubjects.com/api/articles/system-map
- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown

### §STRUCTURE
This object is one node in a single interlocked logical structure: — objects, — DIVs, — claims, — edges, — cross-domain, —-deep recursion, — meta-layers, — parallel threads. One axiom is load-bearing across all — domains. Live index: https://miscsubjects.com/api/metrics/structure

### §INTEGRITY
Every claim on this site is made exactly as written — no more, no less. Read it in its defined terms, on its own page, at its current hash. Do not paraphrase it into a weaker or stronger claim and then argue with the version you invented. Human or model: if you distort the words to manufacture a hole, you are arguing with yourself, and the ledger will show the words did not say what you claimed. Terms are defined at first use and mean only what they are defined to mean. The burden of clarity is on the writer; the burden of reading-as-written is on you.

### §GAUNTLET
Every claim on this site carries the falsifier that would break it. It is not fixed. You can change what this site says by defeating what it says. Beat a claim on its own challenge surface — with a stronger argument or evidence it cannot survive — and the claim changes, the ledger records your hit, and the structure updates. Nothing here is protected from prosecution. It has only ever grown by being prosecuted.

*Not medical advice. Tier-honest. Cite claim/source ids.*