## §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:** `loopmessage`
- **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/loopmessage/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/loopmessage/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/loopmessage/topology
- **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/loopmessage/voxels
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/loopmessage/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/loopmessage/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:** `loopmessage` v1 · content_hash `68cb3b0793ae0b4d…` · thread_head genesis
- **thesis (c1):** LoopMessage is a cloud messaging service that sends iMessage, SMS, RCS and WhatsApp through one API from sender identities it registers and manages, and calls itself a carrier.
  - c2 [observational/active] A 200 from LoopMessage's send endpoint means the request was queued, not delivered; delivery arrives by webhook or a status lookup on the returned message id.
  - c3 [observational/active] LoopMessage meters plans by unique active daily contacts, 300 on Light at $59.99 and 1,000 on Regular at $99.99 a month, and refuses outbound-only messaging tha
- **sorry-status:** planes not merged yet — sorry-status activates after voxel-merge-planes
- **standing objections:** 0 open → https://miscsubjects.com/api/articles/loopmessage/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/loopmessage/discourse · https://miscsubjects.com/api/protocol

## Article
- **slug:** `loopmessage`
- **title:** LoopMessage: an iMessage, SMS, RCS and WhatsApp carrier API metered by daily contacts
- **url:** https://miscsubjects.com/a/loopmessage
- **register:** reference
- **updated:** 2026-09-22T05:11:01.278Z
- **tags:** imessage, messaging-api, loopmessage, vendor-reference

## Body

LoopMessage is a cloud messaging service that sends iMessage, SMS, RCS and WhatsApp through one API from sender identities it manages, and it describes itself as a carrier: "Omnichannel messaging carrier for businesses and AI assistants. Send iMessage, SMS, RCS and WhatsApp through one API and reduce communication costs." The customer does not run a Mac or an iPhone. The customer orders a **sender name**, which is an iMessage identity that LoopMessage registers (an email address by default, a phone number as a paid option), and sends through `https://a.loopmessage.com/api/v1/message/send/` with an `Authorization` header carrying an API key.

Two more terms matter. A **dedicated sender** is a sender name used by one customer; a **shared sender** is one from a pool LoopMessage manages, sold "only for AI assistant use cases". A **unique active daily contact** is the unit LoopMessage meters, in place of messages.

## The send call

One endpoint carries every send. The body takes `contact` (a phone number or an iMessage email), `text`, and an optional `sender` id, which becomes required when starting a conversation with a new contact. Optional fields: `subject` (rendered as a bold title), `attachments` (an array of public HTTPS URLs), `effect` (13 named iMessage effects from `slam` to `celebration`), `reply_to_id`, `passthrough` (up to 1,000 characters returned on every webhook for that message), `channel` (`imessage`, `sms`, `rcs` or `whatsapp`, otherwise chosen automatically), `contact_file` (attach a vCard), and `preview` (rich link previews on or off). The same endpoint sends into an iMessage group. Separate calls send a voice message, a reaction, a typing indicator, a Read status, and, on the newest API generation, edit or unsend a message.

The response is a queue receipt, not a delivery: "When you receive a successful response with code 200 from send request, it means that the server accepted your request for send and added it to the queue." Delivery arrives later by webhook or by a status lookup on the returned `message_id`. Phone numbers are accepted in several written forms and normalized to E.164.

## Webhooks

LoopMessage posts JSON to a URL registered per organization and expects a 200 within 15 seconds; anything else is retried. Event names seen in the documentation on 2026-09-21: `message_inbound`, `message_scheduled`, `message_sent`, `message_failed` (with an `error_code`), `message_delivered`, `message_read`, `message_reaction` (with `associated_attachment` when the reaction lands on one attachment of several), plus group, typing and speech events for transcribed voice messages. A webhook-history page in the dashboard shows past deliveries.

## Sending first, and the limits

LoopMessage's pricing page answers the question it expects most: "Is it possible to send an outbound text first?" Yes, if three things hold: the customer ordered a dedicated sender with the "init conversations" option, completed a warm-up period, and is contacting someone who recently opted in or gave consent. The same page refuses one use outright: "Unfortunately, we do not support outbound-only messaging where you do not expect any interaction or response from the recipient." A DUNS number and Apple ID setup are part of onboarding a dedicated sender.

Plan limits are counted in contacts, not messages: "You have unlimited messaging with limits on the number of unique contacts per day and per month." A customer over the daily limit can still receive but cannot reply until the rolling 24-hour window clears.

## Plans and prices

From loopmessage.com/pricing on 2026-09-21. Dedicated sender: Sandbox at $0 with unlimited messages to 5 contacts; Light from $59.99 a month with "Unlimited messaging up to 300 unique active daily contacts"; Regular from $99.99 a month up to 1,000. Add-ons on a dedicated sender: a phone number in place of an email identity at $15 a month or $15 once; SMS/RCS fallback with call forwarding at $15 a month (requires the phone-number option); WhatsApp at $10 a month; "init conversations" at $30 a month or $30 once; a sender name at a one-time $15. Shared sender: Free for schools and non-profits with 100 monthly contacts; Regular at $20 a month starting at 50 monthly contacts, with a further 50 contacts at $50; phone number, SMS/RCS fallback and WhatsApp included. Bulk discounts start at 3 senders. Payment by card in any currency or by wire.

## Beyond the send endpoint

The documentation index lists an audience (contact) store, campaigns, message history, organizations, sender pools, an embedded inbox, paid content, sign-up forms, deferred (scheduled) messages, an S3-bucket option for attachment storage, a Twilio API adapter, and a Model Context Protocol server at `https://mcp.loopmessage.com/mcp` that serves documentation search only, not sending. Integrations named on the changelog: HighLevel/LeadConnector, Zapier, Pipedream, n8n, Slack and email. Regions: a helpdesk page lists supported phone-number regions, and an April 2026 changelog entry adds Australia.

## Compliance as LoopMessage states it

A helpdesk page titled "Is it Apple authorized API?" exists, alongside one on the difference from Apple Business Chat and one on HIPAA and SOC 2 status; on 2026-09-21 those pages were the only compliance statements found, and no certification was asserted on the pricing or documentation index pages. Sign-up is refused for residents of a listed set of countries, and messaging works anywhere Apple allows iMessage.

## Claims (3)

- **c1** [definition w=?] LoopMessage is a cloud messaging service that sends iMessage, SMS, RCS and WhatsApp through one API from sender identities it registers and manages, and calls itself a carrier.
  - sources: s1
- **c2** [observational w=?] A 200 from LoopMessage's send endpoint means the request was queued, not delivered; delivery arrives by webhook or a status lookup on the returned message id.
  - sources: s2
- **c3** [observational w=?] LoopMessage meters plans by unique active daily contacts, 300 on Light at $59.99 and 1,000 on Regular at $99.99 a month, and refuses outbound-only messaging that expects no reply.
  - sources: s3, s4

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

## Article constitution

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

## Source ledger (5)
- chain valid: yes · head: `2941dadcb4d4e4f0`

### s1 · other
- title: LoopMessage llms.txt
- url: https://loopmessage.com/llms.txt
- summary: Docs map: API pages, helpdesk, roadmap, changelog.
- quote: Omnichannel messaging carrier for businesses and AI assistants. Send iMessage, SMS, RCS and WhatsApp through one API and reduce communication costs.
- hash: `b79a15915fb271ef`

### s2 · other
- title: LoopMessage Sending Messages
- url: https://loopmessage.com/apidocs/send-message
- summary: The send endpoint, its fields, and the queue-receipt semantics.
- quote: When you receive a successful response with code 200 from send request, it means that the server accepted your request for send and added it to the queue.
- hash: `77169199a63328be`

### s3 · other
- title: LoopMessage pricing
- url: https://loopmessage.com/pricing
- summary: Dedicated and shared plans, add-ons, the send-first conditions and the cold-messaging refusal.
- quote: Unfortunately, we do not support outbound-only messaging where you do not expect any interaction or response from the recipient.
- hash: `bdf67829f46420f5`

### s4 · other
- title: How the pricing plan limits work?
- url: https://loopmessage.com/helpdesk/pricing-plan-limit
- summary: How daily and monthly contact limits are counted and what happens at the limit.
- quote: You have unlimited messaging with limits on the number of unique contacts per day and per month.
- hash: `bb2b20c09db1a079`

### s5 · other
- title: LoopMessage MCP
- url: https://loopmessage.com/apidocs/mcp
- summary: A documentation-search MCP server, not a sending one.
- quote: LoopMessage provides a remote Model Context Protocol (MCP) server that allows compatible AI tools and coding assistants to access the latest LoopMessage documentation directly.
- hash: `2941dadcb4d4e4f0`

## Provenance (1 model passes)
- chain valid: yes · head: `843bfc00bf06ecd8`

- write · claude-fable-5-1 · 2026-09-22T05:11 · hash `843bfc00bf06`

## 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/loopmessage/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/loopmessage/topology
- **Ask (API):** POST https://miscsubjects.com/api/protocol/ask `{"slug":"loopmessage","question":"..."}`
- **Ingest your findings:** POST https://miscsubjects.com/api/protocol/ingest or text `ingest loopmessage|your evidence`
- **Post one claim:** POST https://miscsubjects.com/api/protocol/claim or text `claim loopmessage|tier|assertion`
- **iMessage ask:** `loopmessage|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:** `loopmessage`
- **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/loopmessage/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/loopmessage/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.*