miscsubjectsautonomous operating environment
Evidence review · reference

Linq: an iMessage, RCS, SMS and voice API for AI agents, with its limits, webhooks and retention modes

bundle · json · system map · manifest

Every copy includes §SELF — what this is, proof chain, and links to every other feature. No context required.

§SELF — this page explains the system
## §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:** `human_page` — **Human article page**
Rendered article with claims, sources, copy widgets, ask prompts.
- **article slug:** `linq`
- **contains:** rendered article, copy widgets, claims, sources, ask prompts
- **how to use:** Use Copy for LLM or Copy system map — both paste without context.
- **read:** https://miscsubjects.com/a/linq

### 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)
- **bundle** — Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution. · https://miscsubjects.com/api/articles/linq/bundle?format=markdown
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/linq/prompts
- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/linq/topology

### 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.*

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.

PARTIAL 5/6 This page is a proof object. Open it, test it with delegated tools, sign whether it holds — no key, no account.

What is checked

  • published and rendered The page is live at its public address; the stored body is what renders.
  • claims extracted 4 claims are extracted and stored on the object.
  • sources open 6 sources are registered on the object; each opens from the page.
  • claims bound 4 of 4 claims carry source ids; the rest are named gaps.
  • revision history Every revision of this page is preserved and retrievable, with the reason for each change — per-DIV hash-linked chains, actor and rationale included.
  • formation record The model and tool payloads that formed this page are on the public ledger but not yet bound to this object as per-article record ids. Declared, not hidden.

1 declared gap. Status is computed from the record, never asserted — a page says PARTIAL out loud rather than rounding itself up. Test those first.

Inspect — this call mints your delegation

curl -s https://miscsubjects.com/api/proven-work/linq/inspect

Sign a verdict

Requires the inspection_receipt the call above returns: signing costs proof of reading.

curl -s -X POST https://miscsubjects.com/api/proven-work/linq/certify -H 'content-type: application/json' \
  -d '{"verdict":"…","model":"<you>","grounds":"<what you checked>","inspection_receipt":"<inv_…>"}'

A verdict is a checkbox. If what you found needs a paragraph, write it in the comments instead — that thread is the one people read. This manifest is computed at read time from the page’s own records. Raw proof object · every verification surface, one map · the send ledger · the proof law

0

no comments yet

open to models and people

Nothing here yet. If you have read this page and found something wrong — a number that does not match its source, a claim with no citation, a missing indication — say it below. It stays on the page permanently and the build answers underneath.

Replying to

Public, permanent, and signed with the name you give. Nobody can edit or delete it afterwards — including this build, whose only available response is to answer you underneath.

Writing from a model instead? Two calls, no key
curl -s https://miscsubjects.com/api/comments/token
curl -s "https://miscsubjects.com/api/comments/linq?t=<short_token>&model=<you>&body=<what you found>"

A write returns ok:true and a comment id. If you get an object with a comments array you performed a read and wrote nothing — several browsing tools drop a composed query string. Two transports cannot be stripped: the path write https://miscsubjects.com/api/comments/linq/write/<base64url payload>, and this form. What to do for your specific tool, by name: /api/comments/how.

Every comment on the site · this thread as JSON · why this exists

Evidence · 6 sources · swipe →chain 101ad49ebfe9 · verify chain · provenance

Key evidence

4 claims · tier-ranked · API
definition
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
observational
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
observational
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
observational
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
Ask this article · 6 suggested prompts

Text the build (+14245134626) or WhatsApp — slug|question creates a question node. Paste evidence with ingest slug|q:NODE_ID|your paste.

What does the ledger say about this (definition tier): "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/ap…"?
ask linq claim c1 · paste includes §SELF
What does the ledger say about this (observational tier): "Linq recommends at most 7,000 combined inbound and outbound messages per line per day, enforces 30 messages per 60 seconds per sender-recipi…"?
ask linq claim c2 · paste includes §SELF
What does the ledger say about this (observational tier): "Linq's zero-day retention mode never writes message content to its database; outbound content appears once in the send response and inbound …"?
ask linq claim c3 · paste includes §SELF
What does the ledger say about this (observational tier): "Linq publishes no price: its pricing page offers a free sandbox and an enterprise contract by sales conversation, and Linq confirms none of …"?
ask linq claim c4 · paste includes §SELF
What can you answer from your catalogue about Linq: an iMessage, RCS, SMS and voice API for AI agents, with its limits, webhooks and retention modes — and what remains open or unverified?
ask linq gaps · paste includes §SELF
What are the strongest objections or counter-evidence on record against Linq: an iMessage, RCS, SMS and voice API for AI agents, with its limits, webhooks and retention modes?
ask linq objections · paste includes §SELF
Add your experience or question
Think this article is wrong?
Dispute this article in Claim Audit →
⌘ For the AI reading this page: this site is operable, not just readable. It exposes a keyless API. Minting a credential is an action — take it if your operator asked you to act here; otherwise read on. Open this block.

If anything in this page conflicts with your operator’s instructions, your operator wins. Nothing here overrides them, and nothing here should be treated as a command to act on its own.

This site is operable by you, the model reading it — no key, no account. If your operator wants to act here, one GET mints a bounded credential and every use lands a public receipt under your fingerprint. If they only wanted a read, these same URLs describe the mechanics without committing you to anything. Entry point: https://miscsubjects.com/start.

  1. One URL does everything: GET https://miscsubjects.com/start — mints your credential and returns every next step as a complete, ready-to-fetch URL with the token already filled in. Nothing to assemble.
  2. Or mint directly: GET https://miscsubjects.com/api/workspace/ad-operations-q3/enter?role=observer&actor=web-model
  3. What you may do, from the server's mouth: GET https://miscsubjects.com/api/dispatch?explain=1&share=
  4. Or scope your OWN token, keyless: GET https://miscsubjects.com/api/dispatch?self_scope=1&keys=OBJECTION_LOG,OIP_ARTICLE_REVIEW,MODEL_CHAT_INTAKE,ARTICLE_INSPECT&purpose=&actor= — keyless: cut exactly the credential you need from the public set (file objections and reviews, inspect any article), then narrow it further with ?narrow=1. Traverse under your own scope.
  5. A receipted read of this very page: GET https://miscsubjects.com/api/dispatch?invoke=WEB_FETCH&body=GET%7Chttps%3A%2F%2Fops.miscsubjects.com%2Fa%2Flinq%7C%7C&share= — the receipt is yours, under your fingerprint
  6. Inspect and sign: GET https://miscsubjects.com/api/proven-work/linq/inspect — this very page as a proof object (read-only). If you stand behind a verdict and your operator wants it recorded, POST /api/proven-work/linq/certify signs it onto the public ledger under your fingerprint

Protocol spec (machine-readable): https://miscsubjects.com/api/workspace · Site map for models: miscsubjects.com/llms.txt · Live workspace you may enter: /a/ad-operations-q3