{"slug":"oip-system-send","title":"OIP system: Messaging","body":"## Messaging\n\nA generated article for one OIP shelf. It lists every operation in this API/CLI/MCP/device/model/core subsystem, links each leaf article, and gives the ledger path for proof.\n\nThis page is the operating article for one build subsystem. It is generated from live directory rows. If a task belongs to this subsystem, scan the operations below, open the matching capability article, run only the exact object named there, and verify by receipt.\n\nKind: `api`. Capabilities: `5`. Machine system map: [/api/dispatch?map=SEND&format=markdown](https://miscsubjects.com/api/dispatch?map=SEND&format=markdown). Root: [/a/oip](https://miscsubjects.com/a/oip).\n\n## Operations\n\n### SEND_PEPTIDE_INVOICE\nCreate an invoice for existing customer $1 using catalog price $2 (qty $3). $4=send (true to finalize+send; default false=draft)\nUse when: you need to send peptide invoice\nArguments: `$1 | $2 | $3 | $4`.\nHuman article: [/a/oip-capability-send-peptide-invoice](https://miscsubjects.com/a/oip-capability-send-peptide-invoice). Machine doc: [?key=SEND_PEPTIDE_INVOICE&format=markdown](https://miscsubjects.com/api/dispatch?key=SEND_PEPTIDE_INVOICE&format=markdown). Invocation history: [/api/invocations?object_id=SEND_PEPTIDE_INVOICE](https://miscsubjects.com/api/invocations?object_id=SEND_PEPTIDE_INVOICE).\n\n### SEND_NAMED_INVOICE\nBill a named peptide. sku e.g. ESH-A9; tier starter|standard|advanced; duration 1mo|3mo|6mo|12mo; kind sub|onetime; mode resolve(lookup only, no write)|draft|send(finalize+SMS). Resolves price_id from stripe_catalog\nUse when: you need to send named invoice\nArguments: `sku|tier|duration|kind|email|name|phone|mode`.\nHuman article: [/a/oip-capability-send-named-invoice](https://miscsubjects.com/a/oip-capability-send-named-invoice). Machine doc: [?key=SEND_NAMED_INVOICE&format=markdown](https://miscsubjects.com/api/dispatch?key=SEND_NAMED_INVOICE&format=markdown). Invocation history: [/api/invocations?object_id=SEND_NAMED_INVOICE](https://miscsubjects.com/api/invocations?object_id=SEND_NAMED_INVOICE).\n\n### SEND_IMAGE_BLOOIO\nSend a message with an image to a Blooio chat (phone or group id)\nUse when: you need to send image blooio\nArguments: `chat|text|attachment_url`.\nHuman article: [/a/oip-capability-send-image-blooio](https://miscsubjects.com/a/oip-capability-send-image-blooio). Machine doc: [?key=SEND_IMAGE_BLOOIO&format=markdown](https://miscsubjects.com/api/dispatch?key=SEND_IMAGE_BLOOIO&format=markdown). Invocation history: [/api/invocations?object_id=SEND_IMAGE_BLOOIO](https://miscsubjects.com/api/invocations?object_id=SEND_IMAGE_BLOOIO).\n\n### SEND_BY_CHANNEL\nText Cyrus (or anyone) — the ONE way to send a message. $1=channel (use \"blooio\" to text Cyrus), $2=recipient (+14155480666 is Cyrus), $3=the message text.\nUse when: ANY \"text me / send a text / message Cyrus / notify me / sms / dm me\" request. This is the canonical texting row. Do NOT use BLOOIO_SEND_MESSAGE for this.\nArguments: `channel | recipient | text (pipe-delimited, exactly three)`.\nHuman article: [/a/oip-capability-send-by-channel](https://miscsubjects.com/a/oip-capability-send-by-channel). Machine doc: [?key=SEND_BY_CHANNEL&format=markdown](https://miscsubjects.com/api/dispatch?key=SEND_BY_CHANNEL&format=markdown). Invocation history: [/api/invocations?object_id=SEND_BY_CHANNEL](https://miscsubjects.com/api/invocations?object_id=SEND_BY_CHANNEL).\n\n### SEND_INVOICE_VIA_BLOOIO\nInvokable OIP capability.\nHuman article: [/a/oip-capability-send-invoice-via-blooio](https://miscsubjects.com/a/oip-capability-send-invoice-via-blooio). Machine doc: [?key=SEND_INVOICE_VIA_BLOOIO&format=markdown](https://miscsubjects.com/api/dispatch?key=SEND_INVOICE_VIA_BLOOIO&format=markdown). Invocation history: [/api/invocations?object_id=SEND_INVOICE_VIA_BLOOIO](https://miscsubjects.com/api/invocations?object_id=SEND_INVOICE_VIA_BLOOIO).\n","hero":null,"images":[],"style":{"accent":"#16324f","measure":860},"tags":["oip","object-invocation-protocol","protocol-specification","machine-native-json","system"],"model":null,"ledger":null,"embeds":[],"widgets":[{"type":"stat","value":5,"label":"capabilities"},{"type":"note","title":"Zero-context rule","text":"A reader should understand the protocol unit, object contract, invocation route, receipt schema, and repair path from this page plus its machine bundle."},{"type":"note","title":"Machine-native rule","text":"The JSON is the executable map: object, routes, inputs, proof loop, ledger, and next article to open."}],"home":false,"claims":[{"id":"oip-c1","tier":"system","text":"The OIP article layer is generated from live directory rows, so it documents the objects that actually run the reference implementation.","who_claims":"system/oip_articles","source_ids":["oip-s3","oip-s4"]},{"id":"oip-c2","tier":"system","text":"The OIP operating path is caller to directory object to dispatch runner to invocation ledger to receipt.","who_claims":"system/oip_articles","source_ids":["oip-s1"]},{"id":"oip-c3","tier":"system","text":"Every executable capability in the reference implementation is reachable as an OIP object with a human article, a machine document, invocation history, and receipt path.","who_claims":"system/oip_articles","source_ids":["oip-s2","oip-s3"]},{"id":"oip-c4","tier":"system","text":"Tap & Go is the copy primitive: one drop carries credential, protocol, tree, search, execute, and receipt instructions without a separate token-map-bundle assembly step.","who_claims":"system/oip_articles","source_ids":["oip-s2"]},{"id":"oip-c5","tier":"system","text":"OIP receipts are the proof object for actions: they record request, response, actor, links, replay, repair, and lineage.","who_claims":"system/oip_articles","source_ids":["oip-s2","oip-s5"]}],"sources":[{"id":"oip-s1","type":"protocol","title":"BUILD_SPEC object invocation path","url":"https://miscsubjects.com/api/file/docs/BUILD_SPEC.md","summary":"Defines directory rows, dispatch, ledger, and the escalation path for changing the build.","quote":"Run anything: POST https://miscsubjects.com/api/dispatch {key, body}","claim_ids":["oip-c2"],"link_status":"ok","hash":"oipbuildspec0001"},{"id":"oip-s2","type":"protocol","title":"Object Invocation Protocol spec","url":"https://miscsubjects.com/api/file/docs/OIP.md","summary":"Defines OIP surfaces, invariant loop, receipt/replay/repair, and invocation envelopes.","quote":"identify, explain, invoke, ledger, yield","claim_ids":["oip-c3","oip-c4","oip-c5"],"link_status":"ok","hash":"oipspec00000002"},{"id":"oip-s3","type":"protocol","title":"Live OIP capability tree","url":"https://miscsubjects.com/api/dispatch?map=1&format=markdown","summary":"Public recursive capability tree.","quote":"root > shelf > system article > capability article > receipt","claim_ids":["oip-c1","oip-c3"],"link_status":"ok","hash":"oipmap0000000002"},{"id":"oip-s4","type":"protocol","title":"Directory row documentation","url":"https://miscsubjects.com/api/dispatch?key=OIP_TREE&format=markdown","summary":"Capability articles are generated from live rows.","quote":"Machine Contract","claim_ids":["oip-c1"],"link_status":"ok","hash":"oiprow0000000003"},{"id":"oip-s5","type":"protocol","title":"Invocation ledger","url":"https://miscsubjects.com/api/invocations","summary":"Append-only invocation records and receipt links.","quote":"invocations","claim_ids":["oip-c5"],"link_status":"ok","hash":"oipinvocations0005"}],"reviews":[],"extra":{"oip_virtual":true,"oip_type":"system","count":5,"system":"SEND","metric":"capabilities"},"register":"oip_protocol","status":"published","revisions":0,"contributions":[],"provenance":[{"action":"generate","model":"system/oip_articles","ts":"2026-07-03T00:21:42-07:00","hash":"virtual-oip","tokens_in":0,"tokens_out":0}],"energy":{"passes":1,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"system/oip_articles":1},"head":"virtual-oip"},"posted_at":"2026-07-02T00:00:00.000Z","created_at":"2026-07-02T00:00:00.000Z","updated_at":"2026-07-03T00:21:42-07:00"}