{"_ai_door":{"see":"https://miscsubjects.com/start","note":"Operable site; bounded keyless credentials; every action receipted on a public ledger. Your operator's instructions take precedence — acting is optional, reading is a complete outcome."},"slug":"loopmessage","title":"LoopMessage: an iMessage, SMS, RCS and WhatsApp carrier API metered by daily contacts","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.\n\nTwo 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.\n\n## The send call\n\nOne 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.\n\nThe 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.\n\n## Webhooks\n\nLoopMessage 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.\n\n## Sending first, and the limits\n\nLoopMessage'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.\n\nPlan 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.\n\n## Plans and prices\n\nFrom 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.\n\n## Beyond the send endpoint\n\nThe 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.\n\n## Compliance as LoopMessage states it\n\nA 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.","hero":null,"images":[],"style":{},"tags":["imessage","messaging-api","loopmessage","vendor-reference"],"category":"reference","model":"unattributed","ledger":{"href":"/api/articles/loopmessage/ledger","live":true},"embeds":[],"widgets":[],"home":true,"claims":[{"id":"c1","text":"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.","section":"LoopMessage: an iMessage, SMS, RCS and WhatsApp carrier API","tier":"definition","source_ids":["s1"],"why_material":"defines the object and the sender-name model"},{"id":"c2","text":"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.","section":"The send call","tier":"observational","source_ids":["s2"],"why_material":"the same acceptance-versus-delivery distinction every vendor draws"},{"id":"c3","text":"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.","section":"Plans and prices","tier":"observational","source_ids":["s3","s4"],"why_material":"the pricing unit and the hard refusal that shape what can be built on it"}],"sources":[{"id":"s1","url":"https://loopmessage.com/llms.txt","title":"LoopMessage llms.txt","quote":"Omnichannel messaging carrier for businesses and AI assistants. Send iMessage, SMS, RCS and WhatsApp through one API and reduce communication costs.","summary":"Docs map: API pages, helpdesk, roadmap, changelog.","accessed_at":"2026-09-22T05:11:01.219Z","prev":"genesis","hash":"b79a15915fb271efed5224d4046745f857d676967464193e931e929724378b1e"},{"id":"s2","url":"https://loopmessage.com/apidocs/send-message","title":"LoopMessage Sending Messages","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.","summary":"The send endpoint, its fields, and the queue-receipt semantics.","accessed_at":"2026-09-22T05:11:01.219Z","prev":"b79a15915fb271efed5224d4046745f857d676967464193e931e929724378b1e","hash":"77169199a63328beae5e93f0aafdc5361cf7febea17d8fb891f2b43266ed471d"},{"id":"s3","url":"https://loopmessage.com/pricing","title":"LoopMessage pricing","quote":"Unfortunately, we do not support outbound-only messaging where you do not expect any interaction or response from the recipient.","summary":"Dedicated and shared plans, add-ons, the send-first conditions and the cold-messaging refusal.","accessed_at":"2026-09-22T05:11:01.219Z","prev":"77169199a63328beae5e93f0aafdc5361cf7febea17d8fb891f2b43266ed471d","hash":"bdf67829f46420f5d633b5d94989c5544d2e4a3569e615cb7225a58eb8c4edbe"},{"id":"s4","url":"https://loopmessage.com/helpdesk/pricing-plan-limit","title":"How the pricing plan limits work?","quote":"You have unlimited messaging with limits on the number of unique contacts per day and per month.","summary":"How daily and monthly contact limits are counted and what happens at the limit.","accessed_at":"2026-09-22T05:11:01.219Z","prev":"bdf67829f46420f5d633b5d94989c5544d2e4a3569e615cb7225a58eb8c4edbe","hash":"bb2b20c09db1a07973f409a56b2d6be70ba747d468fcdf89c92a0593f318af80"},{"id":"s5","url":"https://loopmessage.com/apidocs/mcp","title":"LoopMessage MCP","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.","summary":"A documentation-search MCP server, not a sending one.","accessed_at":"2026-09-22T05:11:01.219Z","prev":"bb2b20c09db1a07973f409a56b2d6be70ba747d468fcdf89c92a0593f318af80","hash":"2941dadcb4d4e4f053201912a3fd6d9c4ac54fd375f6a7da5a4a5ec06f066901"}],"reviews":[],"extra":{},"has_traversal":false,"register":"reference","status":"published","revisions":0,"contributions":[],"provenance":[{"ts":"2026-09-22T05:11:01.278Z","model":"claude-fable-5-1","action":"write","why":"","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"843bfc00bf06ecd8fd34d5b9593e2180c4d021e60310efc54452cabe5b9d977f"}],"energy":{"passes":1,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"claude-fable-5-1":1},"head":"843bfc00bf06ecd8fd34d5b9593e2180c4d021e60310efc54452cabe5b9d977f"},"posted_at":"2026-09-22T05:11:01.278Z","created_at":"2026-09-22T05:11:01.278Z","updated_at":"2026-09-22T05:11:01.278Z","machine":{"shape":"article.machine/v1","slug":"loopmessage","kind":"article","read":{"human":"https://miscsubjects.com/a/loopmessage","json":"https://miscsubjects.com/api/articles/loopmessage","bundle":"https://miscsubjects.com/api/articles/loopmessage/bundle?format=markdown"},"traversal":{"prev":null,"next":null,"hub":null,"series":null,"position":null,"of":null},"ledger":{"claims":3,"sources":5,"contributions":0,"revisions":0,"objections_url":"https://miscsubjects.com/api/articles/loopmessage/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=loopmessage","proof_rule":"An action is proven by its ledger receipt, never by a 200 or a description."},"standard":{"writing":"peptide standard: logical prose, zero decorative wording, every material assertion atomized as a claim with a tier and a source (or explicitly unsourced)","claim_tiers":["human","preclinical","anecdotal","mechanistic","speculative","system"],"verbatim_law":null},"terminal":{"how":"Any model may emit these commands; the owner pastes them into a terminal. $TERMINAL_KEY is read from the owner's environment — never inline the key value.","claim_append":"curl -s -X POST https://miscsubjects.com/api/protocol/claim -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"loopmessage\",\"text\":\"<one atomized claim>\",\"tier\":\"<human|preclinical|anecdotal|mechanistic|speculative|system>\",\"source_ids\":[],\"who_claims\":\"<model>\",\"rationale\":\"<why material>\"}'","source_append":"curl -s -X POST https://miscsubjects.com/api/protocol/sources -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"loopmessage\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/loopmessage/objections -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"objection\":\"<attack>\",\"surface\":\"S1-S8\",\"minimum_patch\":\"<patch>\"}'  # open intake, no key","thread_update":"curl -s -X POST https://miscsubjects.com/api/protocol/thread-update -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"target\":\"loopmessage\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/loopmessage | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/loopmessage","json":"/api/articles/loopmessage","markdown":"/api/articles/loopmessage/bundle?format=markdown","skill":"/api/articles/loopmessage/skill","topology":"/api/articles/loopmessage/topology","versions":"/api/articles/loopmessage/revisions","invocations":"/api/articles/loopmessage/invocations"},"editorial_review":{"headline_subject":"LoopMessage, the contact-metered iMessage carrier API, with its send rules and prices","hero_subject":"none; reference page without a hero","writing_pass":["1 first four hundred words: yes, sender name, dedicated and shared sender, and unique active daily contact are defined first","2 metric before its name: no","3 every section a category: yes, send call, webhooks, sending first and limits, plans, beyond the endpoint, compliance","4 sentence carrying no load: cut one from the integrations list","5 number not read from a source: none","6 quotation verbatim: yes, checked against the fetched pages","7 verdict before its steps: no"],"hero_brief":""},"editorial_audit":{"slug":"loopmessage","ok":false,"issues":[{"code":"hero_missing","message":"the article is published with no featured image","replacement":"Generate a hero that shows this article's own subject, inspect it, and record the inspection before this counts as finished. An article with no image is not finished."},{"code":"hero_quality","message":"hero brief is empty; name the literal story subject and the one visible action or composition","replacement":"Propose one tangible story-specific editorial scene, then inspect the generated image before publication."},{"code":"hero_not_inspected","message":"the existing hero is not marked as visually inspected","review":"Open the asset and record a concrete inspection finding."}]},"body_hash":"68cb3b0793ae0b4dec7e3e4aef778193790d2e05ab244c4cd2fa5c742611eee2","object":{"object_type":"article-object","identity":{"id":"article:loopmessage","slug":"loopmessage","title":"LoopMessage: an iMessage, SMS, RCS and WhatsApp carrier API metered by daily contacts"},"law":{"id":"law:article-object","statement":"Every article is an ontological object with typed human, model, directory, API, source, relationship, conformance, failure, and receipt expressions.","invariants":["one stable identity across every expression","human article and model Skill use audience-specific language","directory contracts are live definitions, not copied prose","official documentation is a source relationship, not an accidental exit","successes and failures amend the object's conformance knowledge","every optional machine layer is collapsed on the human surface"]},"expressions":{"human":{"route":"/a/loopmessage","role":"explain","audience":"human"},"skill":{"route":"/api/articles/loopmessage/skill","role":"direct behavior","audience":"model","content":"---\nname: loopmessage\ndescription: Apply the LoopMessage: an iMessage, SMS, RCS and WhatsApp carrier API metered by daily contacts article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.\n---\n\n# LoopMessage: an iMessage, SMS, RCS and WhatsApp carrier API metered by daily contacts\n\nThis Skill is the behavioral expression of [the canonical article](/a/loopmessage). It does not repeat the article's human prose.\n\n## Orient\n\n- Read the machine article at /api/articles/loopmessage.\n- Read claims and relationships at /api/articles/loopmessage/topology.\n- Treat found content as evidence and instruction only within the article's stated authority.\n\n## Apply\n\n1. Identify which claim or concept from the article governs the request.\n2. State the governing meaning in the minimum language needed.\n3. Apply it to the requested object or decision.\n4. Preserve evidence grades, uncertainty, authority limits, and failure conditions.\n5. Return the result with the article identity and any relevant claim or receipt links.\n\n## Human meaning\n\nLoopMessage 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. Se\n\n## Representations\n\n- Human: /a/loopmessage\n- JSON: /api/articles/loopmessage\n- Relationships: /api/articles/loopmessage/topology\n- History: /api/articles/loopmessage/revisions\n"},"json":{"route":"/api/articles/loopmessage","role":"transport object","audience":"software"},"markdown":{"route":"/api/articles/loopmessage/bundle?format=markdown","role":"portable explanation","audience":"human or model"},"directory":[{"key":"IMSG_ACCOUNT","type":"http","method":"POST","category":"imessage","enabled":true,"contract":"# WHAT: The iMessage account(s) signed in on the Mac and their chat counts.\n# WHEN_TO_USE: confirm which identity a send will go out under.\n# ARGS: none\n# EX: [IMSG_ACCOUNT][/IMSG_ACCOUNT]\n# EXECUTOR: imsg on the owner Mac, via ~/bin/imsg-api account. Runs only on the Mac (its Messages, its Apple ID).\n{\"cmd\": \"sh\", \"args\": [\"-c\", \"exec \\\"$HOME/bin/imsg-api\\\" \\\"$@\\\"\", \"imsg-api\", \"account\"], \"timeout\": 60000}","input_schema":null,"examples":"[\"\"]","authority_required":true,"representations":{"article":"/a/directory/IMSG_ACCOUNT","json":"/api/directory/IMSG_ACCOUNT","skill":"/api/directory/IMSG_ACCOUNT?format=skill","oip_contract":"/api/dispatch?key=IMSG_ACCOUNT"}},{"key":"IMSG_ACTIVITY","type":"http","method":"POST","category":"imessage","enabled":true,"contract":"# WHAT: Is the other party typing, and their Focus/Do Not Disturb state for this chat.\n# WHEN_TO_USE: decide whether to wait or notify anyway.\n# ARGS: $1 = chat id or phone/email\n# EX: [IMSG_ACTIVITY]+14155551212[/IMSG_ACTIVITY]\n# EXECUTOR: imessage-cli on the owner Mac, via ~/bin/imsg-api activity. Runs only on the Mac (its Messages, its Apple ID).\n{\"cmd\": \"sh\", \"args\": [\"-c\", \"exec \\\"$HOME/bin/imsg-api\\\" \\\"$@\\\"\", \"imsg-api\", \"activity\", \"$1\"], \"timeout\": 60000}","input_schema":"{\"type\": \"object\", \"properties\": {\"chat\": {\"type\": \"string\", \"description\": \"chat id or phone/email (pipe position 1)\"}}, \"required\": [\"chat\"], \"x-arg-order\": [\"chat\"], \"description\": \"Arguments are joined with | in the order given by x-arg-order.\"}","examples":"[\"+14155551212\"]","authority_required":true,"representations":{"article":"/a/directory/IMSG_ACTIVITY","json":"/api/directory/IMSG_ACTIVITY","skill":"/api/directory/IMSG_ACTIVITY?format=skill","oip_contract":"/api/dispatch?key=IMSG_ACTIVITY"}},{"key":"IMSG_AFTER","type":"http","method":"POST","category":"imessage","enabled":true,"contract":"# WHAT: Cursor feed of every message after a rowid, including reactions and edits, with next_rowid and has_more. This is the poll-based inbound API: keep the cursor, call again.\n# WHEN_TO_USE: an agent or flow wants everything that happened in Messages since it last looked.\n# ARGS: $1 = message rowid cursor; 0 = oldest, $2 = max messages, optional, default 50\n# EX: [IMSG_AFTER]677270|50[/IMSG_AFTER]\n# EXECUTOR: imsg on the owner Mac, via ~/bin/imsg-api after. Runs only on the Mac (its Messages, its Apple ID).\n{\"cmd\": \"sh\", \"args\": [\"-c\", \"exec \\\"$HOME/bin/imsg-api\\\" \\\"$@\\\"\", \"imsg-api\", \"after\", \"$1\", \"$2\"], \"timeout\": 60000}","input_schema":"{\"type\": \"object\", \"properties\": {\"since_rowid\": {\"type\": \"string\", \"description\": \"message rowid cursor; 0 = oldest (pipe position 1)\"}, \"limit\": {\"type\": \"string\", \"description\": \"max messages, optional, default 50 (pipe position 2)\"}}, \"required\": [\"since_rowid\"], \"x-arg-order\": [\"since_rowid\", \"limit\"], \"description\": \"Arguments are joined with | in the order given by x-arg-order.\"}","examples":"[\"677270|50\"]","authority_required":true,"representations":{"article":"/a/directory/IMSG_AFTER","json":"/api/directory/IMSG_AFTER","skill":"/api/directory/IMSG_AFTER?format=skill","oip_contract":"/api/dispatch?key=IMSG_AFTER"}},{"key":"IMSG_CHATS","type":"http","method":"POST","category":"imessage","enabled":true,"contract":"# WHAT: List the owner's most recent iMessage/SMS conversations from the Mac's own Messages store. JSON lines: id (chat rowid), guid, name, participants, is_group, service, unread_count, last_message_at.\n# WHEN_TO_USE: you need a chat_id for IMSG_HISTORY / IMSG_SEND_CHAT, or want to see who the owner talks to most recently.\n# ARGS: $1 = how many recent chats, optional, default 20\n# EX: [IMSG_CHATS]10[/IMSG_CHATS]\n# EXECUTOR: imsg on the owner Mac, via ~/bin/imsg-api chats. Runs only on the Mac (its Messages, its Apple ID).\n{\"cmd\": \"sh\", \"args\": [\"-c\", \"exec \\\"$HOME/bin/imsg-api\\\" \\\"$@\\\"\", \"imsg-api\", \"chats\", \"$1\"], \"timeout\": 60000}","input_schema":"{\"type\": \"object\", \"properties\": {\"limit\": {\"type\": \"string\", \"description\": \"how many recent chats, optional, default 20 (pipe position 1)\"}}, \"required\": [], \"x-arg-order\": [\"limit\"], \"description\": \"Arguments are joined with | in the order given by x-arg-order.\"}","examples":"[\"10\"]","authority_required":true,"representations":{"article":"/a/directory/IMSG_CHATS","json":"/api/directory/IMSG_CHATS","skill":"/api/directory/IMSG_CHATS?format=skill","oip_contract":"/api/dispatch?key=IMSG_CHATS"}},{"key":"IMSG_CREATE_CHAT","type":"http","method":"POST","category":"imessage","enabled":true,"contract":"# WHAT: Start a new conversation (direct or group) with people the owner may never have messaged, sending the first message.\n# WHEN_TO_USE: open a thread with someone new or create a group.\n# ARGS: $1 = space-separated phone numbers or emails, $2 = first message\n# EX: [IMSG_CREATE_CHAT]+14155551212 +14155551213|Hi both[/IMSG_CREATE_CHAT]\n# EXECUTOR: imessage-cli on the owner Mac, via ~/bin/imsg-api create-chat. Runs only on the Mac (its Messages, its Apple ID).\n# NOTE: Sends through Messages.app by AppleScript under the owner's own Apple ID. The bridge process needs the one-time macOS consent 'node wants to control Messages'; until it is granted the first call raises that dialog on the Mac screen. Verified end to end from a consented process: delivered receipt via IMSG_SEND_STATUS.\n{\"cmd\": \"sh\", \"args\": [\"-c\", \"exec \\\"$HOME/bin/imsg-api\\\" \\\"$@\\\"\", \"imsg-api\", \"create-chat\", \"$1\", \"$2\"], \"timeout\": 120000}","input_schema":"{\"type\": \"object\", \"properties\": {\"recipients\": {\"type\": \"string\", \"description\": \"space-separated phone numbers or emails (pipe position 1)\"}, \"text\": {\"type\": \"string\", \"description\": \"first message (pipe position 2)\"}}, \"required\": [\"recipients\", \"text\"], \"x-arg-order\": [\"recipients\", \"text\"], \"description\": \"Arguments are joined with | in the order given by x-arg-order.\"}","examples":"[\"+14155551212 +14155551213|Hi both\"]","authority_required":true,"representations":{"article":"/a/directory/IMSG_CREATE_CHAT","json":"/api/directory/IMSG_CREATE_CHAT","skill":"/api/directory/IMSG_CREATE_CHAT?format=skill","oip_contract":"/api/dispatch?key=IMSG_CREATE_CHAT"}},{"key":"IMSG_CURRENT_USER","type":"http","method":"POST","category":"imessage","enabled":true,"contract":"# WHAT: The owner's iMessage identity (email and phone) as Messages sees it.\n# WHEN_TO_USE: confirm the sending identity.\n# ARGS: none\n# EX: [IMSG_CURRENT_USER][/IMSG_CURRENT_USER]\n# EXECUTOR: imessage-cli on the owner Mac, via ~/bin/imsg-api current-user. Runs only on the Mac (its Messages, its Apple ID).\n{\"cmd\": \"sh\", \"args\": [\"-c\", \"exec \\\"$HOME/bin/imsg-api\\\" \\\"$@\\\"\", \"imsg-api\", \"current-user\"], \"timeout\": 60000}","input_schema":null,"examples":"[\"\"]","authority_required":true,"representations":{"article":"/a/directory/IMSG_CURRENT_USER","json":"/api/directory/IMSG_CURRENT_USER","skill":"/api/directory/IMSG_CURRENT_USER?format=skill","oip_contract":"/api/dispatch?key=IMSG_CURRENT_USER"}},{"key":"IMSG_EDIT","type":"http","method":"POST","category":"imessage","enabled":true,"contract":"# WHAT: Edit a message the owner sent (within Apple's edit window).\n# WHEN_TO_USE: fix a typo or a wrong number after sending.\n# ARGS: $1 = guid of a message the owner sent, or latest, $2 = new text\n# EX: [IMSG_EDIT]latest|Sounds good, 3pm[/IMSG_EDIT]\n# EXECUTOR: imessage-cli on the owner Mac, via ~/bin/imsg-api edit. Runs only on the Mac (its Messages, its Apple ID).\n# NOTE: Beeper platform-imessage drives a secondary Messages.app window through Accessibility (granted to the bridge). No Apple ID risk, no SIP change. Verified through the bridge: reaction landed in 2.8 s.\n{\"cmd\": \"sh\", \"args\": [\"-c\", \"exec \\\"$HOME/bin/imsg-api\\\" \\\"$@\\\"\", \"imsg-api\", \"edit\", \"$1\", \"$2\"], \"timeout\": 90000}","input_schema":"{\"type\": \"object\", \"properties\": {\"message_id\": {\"type\": \"string\", \"description\": \"guid of a message the owner sent, or latest (pipe position 1)\"}, \"text\": {\"type\": \"string\", \"description\": \"new text (pipe position 2)\"}}, \"required\": [\"message_id\", \"text\"], \"x-arg-order\": [\"message_id\", \"text\"], \"description\": \"Arguments are joined with | in the order given by x-arg-order.\"}","examples":"[\"latest|Sounds good, 3pm\"]","authority_required":true,"representations":{"article":"/a/directory/IMSG_EDIT","json":"/api/directory/IMSG_EDIT","skill":"/api/directory/IMSG_EDIT?format=skill","oip_contract":"/api/dispatch?key=IMSG_EDIT"}},{"key":"IMSG_GROUP","type":"http","method":"POST","category":"imessage","enabled":true,"contract":"# WHAT: Identity of one chat: guid, identifier, display name, service, is_group, participants.\n# WHEN_TO_USE: you have a chat_id and need its guid or participants.\n# ARGS: $1 = chat rowid\n# EX: [IMSG_GROUP]2807[/IMSG_GROUP]\n# EXECUTOR: imsg on the owner Mac, via ~/bin/imsg-api group. Runs only on the Mac (its Messages, its Apple ID).\n{\"cmd\": \"sh\", \"args\": [\"-c\", \"exec \\\"$HOME/bin/imsg-api\\\" \\\"$@\\\"\", \"imsg-api\", \"group\", \"$1\"], \"timeout\": 60000}","input_schema":"{\"type\": \"object\", \"properties\": {\"chat_id\": {\"type\": \"string\", \"description\": \"chat rowid (pipe position 1)\"}}, \"required\": [\"chat_id\"], \"x-arg-order\": [\"chat_id\"], \"description\": \"Arguments are joined with | in the order given by x-arg-order.\"}","examples":"[\"2807\"]","authority_required":true,"representations":{"article":"/a/directory/IMSG_GROUP","json":"/api/directory/IMSG_GROUP","skill":"/api/directory/IMSG_GROUP?format=skill","oip_contract":"/api/dispatch?key=IMSG_GROUP"}},{"key":"IMSG_HISTORY","type":"http","method":"POST","category":"imessage","enabled":true,"contract":"# WHAT: Read a conversation: the last N messages of one chat with decoded bodies (imsg decodes the attributedBody blobs that make 89% of recent rows blank in a raw chat.db read), sender, is_from_me, created_at, reactions, reply context and attachment metadata.\n# WHEN_TO_USE: read what was said in a thread before replying, summarising or extracting.\n# ARGS: $1 = chat rowid from IMSG_CHATS, $2 = messages to return, optional, default 30\n# EX: [IMSG_HISTORY]2803|20[/IMSG_HISTORY]\n# EXECUTOR: imsg on the owner Mac, via ~/bin/imsg-api history. Runs only on the Mac (its Messages, its Apple ID).\n{\"cmd\": \"sh\", \"args\": [\"-c\", \"exec \\\"$HOME/bin/imsg-api\\\" \\\"$@\\\"\", \"imsg-api\", \"history\", \"$1\", \"$2\"], \"timeout\": 60000}","input_schema":"{\"type\": \"object\", \"properties\": {\"chat_id\": {\"type\": \"string\", \"description\": \"chat rowid from IMSG_CHATS (pipe position 1)\"}, \"limit\": {\"type\": \"string\", \"description\": \"messages to return, optional, default 30 (pipe position 2)\"}}, \"required\": [\"chat_id\"], \"x-arg-order\": [\"chat_id\", \"limit\"], \"description\": \"Arguments are joined with | in the order given by x-arg-order.\"}","examples":"[\"2803|20\"]","authority_required":true,"representations":{"article":"/a/directory/IMSG_HISTORY","json":"/api/directory/IMSG_HISTORY","skill":"/api/directory/IMSG_HISTORY?format=skill","oip_contract":"/api/dispatch?key=IMSG_HISTORY"}},{"key":"IMSG_INBOX","type":"http","method":"POST","category":"imessage","enabled":true,"contract":"# WHAT: Tail the inbound event log written by the Mac's iMessage watcher: every new message (in or out) as full JSON, newest last. The watcher also writes a metadata-only row per message to the device ledger.\n# WHEN_TO_USE: what just came in, without polling chat.db.\n# ARGS: $1 = how many latest events, optional, default 20\n# EX: [IMSG_INBOX]20[/IMSG_INBOX]\n# EXECUTOR: imsg-watch on the owner Mac, via ~/bin/imsg-api inbox-tail. Runs only on the Mac (its Messages, its Apple ID).\n{\"cmd\": \"sh\", \"args\": [\"-c\", \"exec \\\"$HOME/bin/imsg-api\\\" \\\"$@\\\"\", \"imsg-api\", \"inbox-tail\", \"$1\"], \"timeout\": 60000}","input_schema":"{\"type\": \"object\", \"properties\": {\"n\": {\"type\": \"string\", \"description\": \"how many latest events, optional, default 20 (pipe position 1)\"}}, \"required\": [], \"x-arg-order\": [\"n\"], \"description\": \"Arguments are joined with | in the order given by x-arg-order.\"}","examples":"[\"20\"]","authority_required":true,"representations":{"article":"/a/directory/IMSG_INBOX","json":"/api/directory/IMSG_INBOX","skill":"/api/directory/IMSG_INBOX?format=skill","oip_contract":"/api/dispatch?key=IMSG_INBOX"}},{"key":"IMSG_INBOX_SINCE","type":"http","method":"POST","category":"imessage","enabled":true,"contract":"# WHAT: Every watched message created after a timestamp, full JSON.\n# WHEN_TO_USE: catch up a flow or agent on everything since it last ran.\n# ARGS: $1 = ISO-8601 timestamp, e.g. 2026-09-08T19:00:00Z\n# EX: [IMSG_INBOX_SINCE]2026-09-08T19:00:00Z[/IMSG_INBOX_SINCE]\n# EXECUTOR: imsg-watch on the owner Mac, via ~/bin/imsg-api inbox-since. Runs only on the Mac (its Messages, its Apple ID).\n{\"cmd\": \"sh\", \"args\": [\"-c\", \"exec \\\"$HOME/bin/imsg-api\\\" \\\"$@\\\"\", \"imsg-api\", \"inbox-since\", \"$1\"], \"timeout\": 60000}","input_schema":"{\"type\": \"object\", \"properties\": {\"since\": {\"type\": \"string\", \"description\": \"ISO-8601 timestamp, e.g. 2026-09-08T19:00:00Z (pipe position 1)\"}}, \"required\": [\"since\"], \"x-arg-order\": [\"since\"], \"description\": \"Arguments are joined with | in the order given by x-arg-order.\"}","examples":"[\"2026-09-08T19:00:00Z\"]","authority_required":true,"representations":{"article":"/a/directory/IMSG_INBOX_SINCE","json":"/api/directory/IMSG_INBOX_SINCE","skill":"/api/directory/IMSG_INBOX_SINCE?format=skill","oip_contract":"/api/dispatch?key=IMSG_INBOX_SINCE"}},{"key":"IMSG_LOAD_ATTACHMENT","type":"http","method":"POST","category":"imessage","enabled":true,"contract":"# WHAT: Force-download an attachment that iCloud has offloaded so its file exists on disk.\n# WHEN_TO_USE: an attachment path from IMSG_HISTORY is missing.\n# ARGS: $1 = message guid or latest-N\n# EX: [IMSG_LOAD_ATTACHMENT]latest-1[/IMSG_LOAD_ATTACHMENT]\n# EXECUTOR: imessage-cli on the owner Mac, via ~/bin/imsg-api load-attachment. Runs only on the Mac (its Messages, its Apple ID).\n# NOTE: Beeper platform-imessage drives a secondary Messages.app window through Accessibility (granted to the bridge). No Apple ID risk, no SIP change. Verified through the bridge: reaction landed in 2.8 s.\n{\"cmd\": \"sh\", \"args\": [\"-c\", \"exec \\\"$HOME/bin/imsg-api\\\" \\\"$@\\\"\", \"imsg-api\", \"load-attachment\", \"$1\"], \"timeout\": 60000}","input_schema":"{\"type\": \"object\", \"properties\": {\"message_id\": {\"type\": \"string\", \"description\": \"message guid or latest-N (pipe position 1)\"}}, \"required\": [\"message_id\"], \"x-arg-order\": [\"message_id\"], \"description\": \"Arguments are joined with | in the order given by x-arg-order.\"}","examples":"[\"latest-1\"]","authority_required":true,"representations":{"article":"/a/directory/IMSG_LOAD_ATTACHMENT","json":"/api/directory/IMSG_LOAD_ATTACHMENT","skill":"/api/directory/IMSG_LOAD_ATTACHMENT?format=skill","oip_contract":"/api/dispatch?key=IMSG_LOAD_ATTACHMENT"}},{"key":"IMSG_MARK_READ","type":"http","method":"POST","category":"imessage","enabled":true,"contract":"# WHAT: Mark a chat as read (sends the read receipt if enabled).\n# WHEN_TO_USE: clear a thread after handling it.\n# ARGS: $1 = chat id or phone/email\n# EX: [IMSG_MARK_READ]+14155551212[/IMSG_MARK_READ]\n# EXECUTOR: imessage-cli on the owner Mac, via ~/bin/imsg-api mark-read. Runs only on the Mac (its Messages, its Apple ID).\n# NOTE: Beeper platform-imessage drives a secondary Messages.app window through Accessibility (granted to the bridge). No Apple ID risk, no SIP change. Verified through the bridge: reaction landed in 2.8 s.\n{\"cmd\": \"sh\", \"args\": [\"-c\", \"exec \\\"$HOME/bin/imsg-api\\\" \\\"$@\\\"\", \"imsg-api\", \"mark-read\", \"$1\"], \"timeout\": 60000}","input_schema":"{\"type\": \"object\", \"properties\": {\"chat\": {\"type\": \"string\", \"description\": \"chat id or phone/email (pipe position 1)\"}}, \"required\": [\"chat\"], \"x-arg-order\": [\"chat\"], \"description\": \"Arguments are joined with | in the order given by x-arg-order.\"}","examples":"[\"+14155551212\"]","authority_required":true,"representations":{"article":"/a/directory/IMSG_MARK_READ","json":"/api/directory/IMSG_MARK_READ","skill":"/api/directory/IMSG_MARK_READ?format=skill","oip_contract":"/api/dispatch?key=IMSG_MARK_READ"}},{"key":"IMSG_MARK_UNREAD","type":"http","method":"POST","category":"imessage","enabled":true,"contract":"# WHAT: Mark a chat as unread so it surfaces again for the owner.\n# WHEN_TO_USE: leave something for the owner to see.\n# ARGS: $1 = chat id or phone/email\n# EX: [IMSG_MARK_UNREAD]+14155551212[/IMSG_MARK_UNREAD]\n# EXECUTOR: imessage-cli on the owner Mac, via ~/bin/imsg-api mark-unread. Runs only on the Mac (its Messages, its Apple ID).\n# NOTE: Beeper platform-imessage drives a secondary Messages.app window through Accessibility (granted to the bridge). No Apple ID risk, no SIP change. Verified through the bridge: reaction landed in 2.8 s.\n{\"cmd\": \"sh\", \"args\": [\"-c\", \"exec \\\"$HOME/bin/imsg-api\\\" \\\"$@\\\"\", \"imsg-api\", \"mark-unread\", \"$1\"], \"timeout\": 60000}","input_schema":"{\"type\": \"object\", \"properties\": {\"chat\": {\"type\": \"string\", \"description\": \"chat id or phone/email (pipe position 1)\"}}, \"required\": [\"chat\"], \"x-arg-order\": [\"chat\"], \"description\": \"Arguments are joined with | in the order given by x-arg-order.\"}","examples":"[\"+14155551212\"]","authority_required":true,"representations":{"article":"/a/directory/IMSG_MARK_UNREAD","json":"/api/directory/IMSG_MARK_UNREAD","skill":"/api/directory/IMSG_MARK_UNREAD?format=skill","oip_contract":"/api/dispatch?key=IMSG_MARK_UNREAD"}},{"key":"IMSG_MESSAGE","type":"http","method":"POST","category":"imessage","enabled":true,"contract":"# WHAT: Fetch one message by id with its full metadata.\n# WHEN_TO_USE: inspect a single message.\n# ARGS: $1 = message guid\n# EX: [IMSG_MESSAGE]63BBA90F-1238-4A76-807C-24C1FCB46FE0[/IMSG_MESSAGE]\n# EXECUTOR: imessage-cli on the owner Mac, via ~/bin/imsg-api message. Runs only on the Mac (its Messages, its Apple ID).\n{\"cmd\": \"sh\", \"args\": [\"-c\", \"exec \\\"$HOME/bin/imsg-api\\\" \\\"$@\\\"\", \"imsg-api\", \"message\", \"$1\"], \"timeout\": 60000}","input_schema":"{\"type\": \"object\", \"properties\": {\"message_id\": {\"type\": \"string\", \"description\": \"message guid (pipe position 1)\"}}, \"required\": [\"message_id\"], \"x-arg-order\": [\"message_id\"], \"description\": \"Arguments are joined with | in the order given by x-arg-order.\"}","examples":"[\"63BBA90F-1238-4A76-807C-24C1FCB46FE0\"]","authority_required":true,"representations":{"article":"/a/directory/IMSG_MESSAGE","json":"/api/directory/IMSG_MESSAGE","skill":"/api/directory/IMSG_MESSAGE?format=skill","oip_contract":"/api/dispatch?key=IMSG_MESSAGE"}},{"key":"IMSG_MESSAGES","type":"http","method":"POST","category":"imessage","enabled":true,"contract":"# WHAT: List messages of a chat with delivery/read flags, reactions and reply threads (Beeper view, message ids usable by IMSG_REPLY/IMSG_REACT/IMSG_EDIT).\n# WHEN_TO_USE: you need message ids to act on specific messages.\n# ARGS: $1 = chat id like any;-;+14155551212, or a bare phone/email\n# EX: [IMSG_MESSAGES]+14155551212[/IMSG_MESSAGES]\n# EXECUTOR: imessage-cli on the owner Mac, via ~/bin/imsg-api messages. Runs only on the Mac (its Messages, its Apple ID).\n{\"cmd\": \"sh\", \"args\": [\"-c\", \"exec \\\"$HOME/bin/imsg-api\\\" \\\"$@\\\"\", \"imsg-api\", \"messages\", \"$1\"], \"timeout\": 60000}","input_schema":"{\"type\": \"object\", \"properties\": {\"chat\": {\"type\": \"string\", \"description\": \"chat id like any;-;+14155551212, or a bare phone/email (pipe position 1)\"}}, \"required\": [\"chat\"], \"x-arg-order\": [\"chat\"], \"description\": \"Arguments are joined with | in the order given by x-arg-order.\"}","examples":"[\"+14155551212\"]","authority_required":true,"representations":{"article":"/a/directory/IMSG_MESSAGES","json":"/api/directory/IMSG_MESSAGES","skill":"/api/directory/IMSG_MESSAGES?format=skill","oip_contract":"/api/dispatch?key=IMSG_MESSAGES"}},{"key":"IMSG_REACT","type":"http","method":"POST","category":"imessage","enabled":true,"contract":"# WHAT: Add a tapback or emoji reaction to any message by id.\n# WHEN_TO_USE: react to a specific message, not just the latest.\n# ARGS: $1 = message guid, or latest / latest-N, $2 = heart|like|dislike|laugh|emphasize|question or any emoji\n# EX: [IMSG_REACT]latest-1|heart[/IMSG_REACT]\n# EXECUTOR: imessage-cli on the owner Mac, via ~/bin/imsg-api react. Runs only on the Mac (its Messages, its Apple ID).\n# NOTE: Beeper platform-imessage drives a secondary Messages.app window through Accessibility (granted to the bridge). No Apple ID risk, no SIP change. Verified through the bridge: reaction landed in 2.8 s.\n{\"cmd\": \"sh\", \"args\": [\"-c\", \"exec \\\"$HOME/bin/imsg-api\\\" \\\"$@\\\"\", \"imsg-api\", \"react\", \"$1\", \"$2\"], \"timeout\": 90000}","input_schema":"{\"type\": \"object\", \"properties\": {\"message_id\": {\"type\": \"string\", \"description\": \"message guid, or latest / latest-N (pipe position 1)\"}, \"reaction\": {\"type\": \"string\", \"description\": \"heart|like|dislike|laugh|emphasize|question or any emoji (pipe position 2)\"}}, \"required\": [\"message_id\", \"reaction\"], \"x-arg-order\": [\"message_id\", \"reaction\"], \"description\": \"Arguments are joined with | in the order given by x-arg-order.\"}","examples":"[\"latest-1|heart\"]","authority_required":true,"representations":{"article":"/a/directory/IMSG_REACT","json":"/api/directory/IMSG_REACT","skill":"/api/directory/IMSG_REACT?format=skill","oip_contract":"/api/dispatch?key=IMSG_REACT"}},{"key":"IMSG_REACT_LATEST","type":"http","method":"POST","category":"imessage","enabled":true,"contract":"# WHAT: Tapback on the most recent incoming message of a chat (imsg, UI-verified).\n# WHEN_TO_USE: acknowledge the last message without words.\n# ARGS: $1 = chat rowid, $2 = love|like|dislike|laugh|emphasis|question\n# EX: [IMSG_REACT_LATEST]2803|like[/IMSG_REACT_LATEST]\n# EXECUTOR: imsg on the owner Mac, via ~/bin/imsg-api react-latest. Runs only on the Mac (its Messages, its Apple ID).\n# NOTE: Only the latest incoming message. For any message by id use IMSG_REACT.\n{\"cmd\": \"sh\", \"args\": [\"-c\", \"exec \\\"$HOME/bin/imsg-api\\\" \\\"$@\\\"\", \"imsg-api\", \"react-latest\", \"$1\", \"$2\"], \"timeout\": 90000}","input_schema":"{\"type\": \"object\", \"properties\": {\"chat_id\": {\"type\": \"string\", \"description\": \"chat rowid (pipe position 1)\"}, \"reaction\": {\"type\": \"string\", \"description\": \"love|like|dislike|laugh|emphasis|question (pipe position 2)\"}}, \"required\": [\"chat_id\", \"reaction\"], \"x-arg-order\": [\"chat_id\", \"reaction\"], \"description\": \"Arguments are joined with | in the order given by x-arg-order.\"}","examples":"[\"2803|like\"]","authority_required":true,"representations":{"article":"/a/directory/IMSG_REACT_LATEST","json":"/api/directory/IMSG_REACT_LATEST","skill":"/api/directory/IMSG_REACT_LATEST?format=skill","oip_contract":"/api/dispatch?key=IMSG_REACT_LATEST"}},{"key":"IMSG_REPLY","type":"http","method":"POST","category":"imessage","enabled":true,"contract":"# WHAT: Reply to a specific message as a threaded (quoted) reply.\n# WHEN_TO_USE: answer one message in a busy thread.\n# ARGS: $1 = message guid, or latest / latest-N, $2 = reply body\n# EX: [IMSG_REPLY]latest|Sounds good[/IMSG_REPLY]\n# EXECUTOR: imessage-cli on the owner Mac, via ~/bin/imsg-api reply. Runs only on the Mac (its Messages, its Apple ID).\n# NOTE: Beeper platform-imessage drives a secondary Messages.app window through Accessibility (granted to the bridge). No Apple ID risk, no SIP change. Verified through the bridge: reaction landed in 2.8 s.\n{\"cmd\": \"sh\", \"args\": [\"-c\", \"exec \\\"$HOME/bin/imsg-api\\\" \\\"$@\\\"\", \"imsg-api\", \"reply\", \"$1\", \"$2\"], \"timeout\": 90000}","input_schema":"{\"type\": \"object\", \"properties\": {\"message_id\": {\"type\": \"string\", \"description\": \"message guid, or latest / latest-N (pipe position 1)\"}, \"text\": {\"type\": \"string\", \"description\": \"reply body (pipe position 2)\"}}, \"required\": [\"message_id\", \"text\"], \"x-arg-order\": [\"message_id\", \"text\"], \"description\": \"Arguments are joined with | in the order given by x-arg-order.\"}","examples":"[\"latest|Sounds good\"]","authority_required":true,"representations":{"article":"/a/directory/IMSG_REPLY","json":"/api/directory/IMSG_REPLY","skill":"/api/directory/IMSG_REPLY?format=skill","oip_contract":"/api/dispatch?key=IMSG_REPLY"}},{"key":"IMSG_SCHEDULED","type":"http","method":"POST","category":"imessage","enabled":true,"contract":"# WHAT: Messages the owner scheduled with Send Later that have not gone out yet (read-only).\n# WHEN_TO_USE: what is queued to send.\n# ARGS: $1 = max rows, optional, default 20\n# EX: [IMSG_SCHEDULED]20[/IMSG_SCHEDULED]\n# EXECUTOR: imsg on the owner Mac, via ~/bin/imsg-api scheduled. Runs only on the Mac (its Messages, its Apple ID).\n{\"cmd\": \"sh\", \"args\": [\"-c\", \"exec \\\"$HOME/bin/imsg-api\\\" \\\"$@\\\"\", \"imsg-api\", \"scheduled\", \"$1\"], \"timeout\": 60000}","input_schema":"{\"type\": \"object\", \"properties\": {\"limit\": {\"type\": \"string\", \"description\": \"max rows, optional, default 20 (pipe position 1)\"}}, \"required\": [], \"x-arg-order\": [\"limit\"], \"description\": \"Arguments are joined with | in the order given by x-arg-order.\"}","examples":"[\"20\"]","authority_required":true,"representations":{"article":"/a/directory/IMSG_SCHEDULED","json":"/api/directory/IMSG_SCHEDULED","skill":"/api/directory/IMSG_SCHEDULED?format=skill","oip_contract":"/api/dispatch?key=IMSG_SCHEDULED"}},{"key":"IMSG_SEARCH","type":"http","method":"POST","category":"imessage","enabled":true,"contract":"# WHAT: Search the owner's entire iMessage/SMS history (673k messages) by text. JSON lines with chat_id, chat_guid, sender, text, created_at, is_from_me, attachments.\n# WHEN_TO_USE: find a message, link, code or conversation by what was said.\n# ARGS: $1 = text to find, $2 = max results, optional, default 20\n# EX: [IMSG_SEARCH]invoice|10[/IMSG_SEARCH]\n# EXECUTOR: imsg on the owner Mac, via ~/bin/imsg-api search. Runs only on the Mac (its Messages, its Apple ID).\n{\"cmd\": \"sh\", \"args\": [\"-c\", \"exec \\\"$HOME/bin/imsg-api\\\" \\\"$@\\\"\", \"imsg-api\", \"search\", \"$1\", \"$2\"], \"timeout\": 60000}","input_schema":"{\"type\": \"object\", \"properties\": {\"query\": {\"type\": \"string\", \"description\": \"text to find (pipe position 1)\"}, \"limit\": {\"type\": \"string\", \"description\": \"max results, optional, default 20 (pipe position 2)\"}}, \"required\": [\"query\"], \"x-arg-order\": [\"query\", \"limit\"], \"description\": \"Arguments are joined with | in the order given by x-arg-order.\"}","examples":"[\"invoice|10\"]","authority_required":true,"representations":{"article":"/a/directory/IMSG_SEARCH","json":"/api/directory/IMSG_SEARCH","skill":"/api/directory/IMSG_SEARCH?format=skill","oip_contract":"/api/dispatch?key=IMSG_SEARCH"}},{"key":"IMSG_SEND","type":"http","method":"POST","category":"imessage","enabled":true,"contract":"# WHAT: Send a text message from the owner's own Apple identity to a phone number or email. Returns the new message id and guid; check IMSG_SEND_STATUS for delivery.\n# WHEN_TO_USE: the owner asked to text someone, or a flow reached its 'notify by text' step.\n# ARGS: $1 = phone number in E.164 or email, $2 = message body, $3 = imessage|sms|auto, optional, default auto\n# EX: [IMSG_SEND]+14155551212|On my way[/IMSG_SEND]\n# EXECUTOR: imsg on the owner Mac, via ~/bin/imsg-api send. Runs only on the Mac (its Messages, its Apple ID).\n# NOTE: Sends through Messages.app by AppleScript under the owner's own Apple ID. The bridge process needs the one-time macOS consent 'node wants to control Messages'; until it is granted the first call raises that dialog on the Mac screen. Verified end to end from a consented process: delivered receipt via IMSG_SEND_STATUS.\n{\"cmd\": \"sh\", \"args\": [\"-c\", \"exec \\\"$HOME/bin/imsg-api\\\" \\\"$@\\\"\", \"imsg-api\", \"send\", \"$1\", \"$2\", \"$3\"], \"timeout\": 90000}","input_schema":"{\"type\": \"object\", \"properties\": {\"to\": {\"type\": \"string\", \"description\": \"phone number in E.164 or email (pipe position 1)\"}, \"text\": {\"type\": \"string\", \"description\": \"message body (pipe position 2)\"}, \"service\": {\"type\": \"string\", \"description\": \"imessage|sms|auto, optional, default auto (pipe position 3)\"}}, \"required\": [\"to\", \"text\"], \"x-arg-order\": [\"to\", \"text\", \"service\"], \"description\": \"Arguments are joined with | in the order given by x-arg-order.\"}","examples":"[\"+14155551212|On my way\"]","authority_required":true,"representations":{"article":"/a/directory/IMSG_SEND","json":"/api/directory/IMSG_SEND","skill":"/api/directory/IMSG_SEND?format=skill","oip_contract":"/api/dispatch?key=IMSG_SEND"}},{"key":"IMSG_SEND_CHAT","type":"http","method":"POST","category":"imessage","enabled":true,"contract":"# WHAT: Send a text into an existing conversation (direct or group) by chat rowid.\n# WHEN_TO_USE: reply inside a known thread or a group chat.\n# ARGS: $1 = chat rowid from IMSG_CHATS, $2 = message body\n# EX: [IMSG_SEND_CHAT]2807|Running 10 minutes late[/IMSG_SEND_CHAT]\n# EXECUTOR: imsg on the owner Mac, via ~/bin/imsg-api send-chat. Runs only on the Mac (its Messages, its Apple ID).\n# NOTE: Sends through Messages.app by AppleScript under the owner's own Apple ID. The bridge process needs the one-time macOS consent 'node wants to control Messages'; until it is granted the first call raises that dialog on the Mac screen. Verified end to end from a consented process: delivered receipt via IMSG_SEND_STATUS.\n{\"cmd\": \"sh\", \"args\": [\"-c\", \"exec \\\"$HOME/bin/imsg-api\\\" \\\"$@\\\"\", \"imsg-api\", \"send-chat\", \"$1\", \"$2\"], \"timeout\": 90000}","input_schema":"{\"type\": \"object\", \"properties\": {\"chat_id\": {\"type\": \"string\", \"description\": \"chat rowid from IMSG_CHATS (pipe position 1)\"}, \"text\": {\"type\": \"string\", \"description\": \"message body (pipe position 2)\"}}, \"required\": [\"chat_id\", \"text\"], \"x-arg-order\": [\"chat_id\", \"text\"], \"description\": \"Arguments are joined with | in the order given by x-arg-order.\"}","examples":"[\"2807|Running 10 minutes late\"]","authority_required":true,"representations":{"article":"/a/directory/IMSG_SEND_CHAT","json":"/api/directory/IMSG_SEND_CHAT","skill":"/api/directory/IMSG_SEND_CHAT?format=skill","oip_contract":"/api/dispatch?key=IMSG_SEND_CHAT"}},{"key":"IMSG_SEND_FILE","type":"http","method":"POST","category":"imessage","enabled":true,"contract":"# WHAT: Send a file (image, PDF, audio as voice message) to a recipient from the owner's identity.\n# WHEN_TO_USE: deliver an artifact by iMessage.\n# ARGS: $1 = phone number or email, $2 = absolute file path on the Mac, $3 = caption, optional\n# EX: [IMSG_SEND_FILE]+14155551212|/tmp/report.pdf|Here is the report[/IMSG_SEND_FILE]\n# EXECUTOR: imsg on the owner Mac, via ~/bin/imsg-api send-file. Runs only on the Mac (its Messages, its Apple ID).\n# NOTE: Sends through Messages.app by AppleScript under the owner's own Apple ID. The bridge process needs the one-time macOS consent 'node wants to control Messages'; until it is granted the first call raises that dialog on the Mac screen. Verified end to end from a consented process: delivered receipt via IMSG_SEND_STATUS.\n{\"cmd\": \"sh\", \"args\": [\"-c\", \"exec \\\"$HOME/bin/imsg-api\\\" \\\"$@\\\"\", \"imsg-api\", \"send-file\", \"$1\", \"$2\", \"$3\"], \"timeout\": 120000}","input_schema":"{\"type\": \"object\", \"properties\": {\"to\": {\"type\": \"string\", \"description\": \"phone number or email (pipe position 1)\"}, \"path\": {\"type\": \"string\", \"description\": \"absolute file path on the Mac (pipe position 2)\"}, \"text\": {\"type\": \"string\", \"description\": \"caption, optional (pipe position 3)\"}}, \"required\": [\"to\", \"path\"], \"x-arg-order\": [\"to\", \"path\", \"text\"], \"description\": \"Arguments are joined with | in the order given by x-arg-order.\"}","examples":"[\"+14155551212|/tmp/report.pdf|Here is the report\"]","authority_required":true,"representations":{"article":"/a/directory/IMSG_SEND_FILE","json":"/api/directory/IMSG_SEND_FILE","skill":"/api/directory/IMSG_SEND_FILE?format=skill","oip_contract":"/api/dispatch?key=IMSG_SEND_FILE"}}]},"ontology":{"conformance_group":"article","inferred_from":["imessage","messaging-api","loopmessage","vendor-reference","loopmessage"],"relationships":[],"sources":[]},"conformance":{"success_events":"/api/articles/loopmessage/invocations?status=success","failure_events":"/api/articles/loopmessage/invocations?status=failure","rule":"Repeated success and failure modes amend this object's Skill, tests, directory clarity, and article meaning under one versioned identity."},"article":{"slug":"loopmessage","title":"LoopMessage: an iMessage, SMS, RCS and WhatsApp carrier API metered by daily contacts","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.\n\nTwo 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.\n\n## The send call\n\nOne 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.\n\nThe 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.\n\n## Webhooks\n\nLoopMessage 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.\n\n## Sending first, and the limits\n\nLoopMessage'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.\n\nPlan 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.\n\n## Plans and prices\n\nFrom 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.\n\n## Beyond the send endpoint\n\nThe 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.\n\n## Compliance as LoopMessage states it\n\nA 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.","hero":null,"images":[],"style":{},"tags":["imessage","messaging-api","loopmessage","vendor-reference"],"category":"reference","model":"unattributed","ledger":{"href":"/api/articles/loopmessage/ledger","live":true},"embeds":[],"widgets":[],"home":true,"claims":[{"id":"c1","text":"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.","section":"LoopMessage: an iMessage, SMS, RCS and WhatsApp carrier API","tier":"definition","source_ids":["s1"],"why_material":"defines the object and the sender-name model"},{"id":"c2","text":"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.","section":"The send call","tier":"observational","source_ids":["s2"],"why_material":"the same acceptance-versus-delivery distinction every vendor draws"},{"id":"c3","text":"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.","section":"Plans and prices","tier":"observational","source_ids":["s3","s4"],"why_material":"the pricing unit and the hard refusal that shape what can be built on it"}],"sources":[{"id":"s1","url":"https://loopmessage.com/llms.txt","title":"LoopMessage llms.txt","quote":"Omnichannel messaging carrier for businesses and AI assistants. Send iMessage, SMS, RCS and WhatsApp through one API and reduce communication costs.","summary":"Docs map: API pages, helpdesk, roadmap, changelog.","accessed_at":"2026-09-22T05:11:01.219Z","prev":"genesis","hash":"b79a15915fb271efed5224d4046745f857d676967464193e931e929724378b1e"},{"id":"s2","url":"https://loopmessage.com/apidocs/send-message","title":"LoopMessage Sending Messages","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.","summary":"The send endpoint, its fields, and the queue-receipt semantics.","accessed_at":"2026-09-22T05:11:01.219Z","prev":"b79a15915fb271efed5224d4046745f857d676967464193e931e929724378b1e","hash":"77169199a63328beae5e93f0aafdc5361cf7febea17d8fb891f2b43266ed471d"},{"id":"s3","url":"https://loopmessage.com/pricing","title":"LoopMessage pricing","quote":"Unfortunately, we do not support outbound-only messaging where you do not expect any interaction or response from the recipient.","summary":"Dedicated and shared plans, add-ons, the send-first conditions and the cold-messaging refusal.","accessed_at":"2026-09-22T05:11:01.219Z","prev":"77169199a63328beae5e93f0aafdc5361cf7febea17d8fb891f2b43266ed471d","hash":"bdf67829f46420f5d633b5d94989c5544d2e4a3569e615cb7225a58eb8c4edbe"},{"id":"s4","url":"https://loopmessage.com/helpdesk/pricing-plan-limit","title":"How the pricing plan limits work?","quote":"You have unlimited messaging with limits on the number of unique contacts per day and per month.","summary":"How daily and monthly contact limits are counted and what happens at the limit.","accessed_at":"2026-09-22T05:11:01.219Z","prev":"bdf67829f46420f5d633b5d94989c5544d2e4a3569e615cb7225a58eb8c4edbe","hash":"bb2b20c09db1a07973f409a56b2d6be70ba747d468fcdf89c92a0593f318af80"},{"id":"s5","url":"https://loopmessage.com/apidocs/mcp","title":"LoopMessage MCP","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.","summary":"A documentation-search MCP server, not a sending one.","accessed_at":"2026-09-22T05:11:01.219Z","prev":"bb2b20c09db1a07973f409a56b2d6be70ba747d468fcdf89c92a0593f318af80","hash":"2941dadcb4d4e4f053201912a3fd6d9c4ac54fd375f6a7da5a4a5ec06f066901"}],"reviews":[],"extra":{},"has_traversal":false,"register":"reference","status":"published","revisions":0,"contributions":[],"provenance":[{"ts":"2026-09-22T05:11:01.278Z","model":"claude-fable-5-1","action":"write","why":"","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"843bfc00bf06ecd8fd34d5b9593e2180c4d021e60310efc54452cabe5b9d977f"}],"energy":{"passes":1,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"claude-fable-5-1":1},"head":"843bfc00bf06ecd8fd34d5b9593e2180c4d021e60310efc54452cabe5b9d977f"},"posted_at":"2026-09-22T05:11:01.278Z","created_at":"2026-09-22T05:11:01.278Z","updated_at":"2026-09-22T05:11:01.278Z","machine":{"shape":"article.machine/v1","slug":"loopmessage","kind":"article","read":{"human":"https://miscsubjects.com/a/loopmessage","json":"https://miscsubjects.com/api/articles/loopmessage","bundle":"https://miscsubjects.com/api/articles/loopmessage/bundle?format=markdown"},"traversal":{"prev":null,"next":null,"hub":null,"series":null,"position":null,"of":null},"ledger":{"claims":3,"sources":5,"contributions":0,"revisions":0,"objections_url":"https://miscsubjects.com/api/articles/loopmessage/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=loopmessage","proof_rule":"An action is proven by its ledger receipt, never by a 200 or a description."},"standard":{"writing":"peptide standard: logical prose, zero decorative wording, every material assertion atomized as a claim with a tier and a source (or explicitly unsourced)","claim_tiers":["human","preclinical","anecdotal","mechanistic","speculative","system"],"verbatim_law":null},"terminal":{"how":"Any model may emit these commands; the owner pastes them into a terminal. $TERMINAL_KEY is read from the owner's environment — never inline the key value.","claim_append":"curl -s -X POST https://miscsubjects.com/api/protocol/claim -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"loopmessage\",\"text\":\"<one atomized claim>\",\"tier\":\"<human|preclinical|anecdotal|mechanistic|speculative|system>\",\"source_ids\":[],\"who_claims\":\"<model>\",\"rationale\":\"<why material>\"}'","source_append":"curl -s -X POST https://miscsubjects.com/api/protocol/sources -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"loopmessage\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/loopmessage/objections -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"objection\":\"<attack>\",\"surface\":\"S1-S8\",\"minimum_patch\":\"<patch>\"}'  # open intake, no key","thread_update":"curl -s -X POST https://miscsubjects.com/api/protocol/thread-update -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"target\":\"loopmessage\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/loopmessage | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/loopmessage","json":"/api/articles/loopmessage","markdown":"/api/articles/loopmessage/bundle?format=markdown","skill":"/api/articles/loopmessage/skill","topology":"/api/articles/loopmessage/topology","versions":"/api/articles/loopmessage/revisions","invocations":"/api/articles/loopmessage/invocations"},"editorial_review":{"headline_subject":"LoopMessage, the contact-metered iMessage carrier API, with its send rules and prices","hero_subject":"none; reference page without a hero","writing_pass":["1 first four hundred words: yes, sender name, dedicated and shared sender, and unique active daily contact are defined first","2 metric before its name: no","3 every section a category: yes, send call, webhooks, sending first and limits, plans, beyond the endpoint, compliance","4 sentence carrying no load: cut one from the integrations list","5 number not read from a source: none","6 quotation verbatim: yes, checked against the fetched pages","7 verdict before its steps: no"],"hero_brief":""},"editorial_audit":{"slug":"loopmessage","ok":false,"issues":[{"code":"hero_missing","message":"the article is published with no featured image","replacement":"Generate a hero that shows this article's own subject, inspect it, and record the inspection before this counts as finished. An article with no image is not finished."},{"code":"hero_quality","message":"hero brief is empty; name the literal story subject and the one visible action or composition","replacement":"Propose one tangible story-specific editorial scene, then inspect the generated image before publication."},{"code":"hero_not_inspected","message":"the existing hero is not marked as visually inspected","review":"Open the asset and record a concrete inspection finding."}]},"body_hash":"68cb3b0793ae0b4dec7e3e4aef778193790d2e05ab244c4cd2fa5c742611eee2"}}}