Spokes.wiki Search About

Log — Business Messaging Wiki

Append-only history. Entries: ## [YYYY-MM-DD] <op> | <title> — <op> ∈ {split, ingest, query, lint}.

[2026-07-01] split | business-messaging-wiki created from _inbox (3 sources)

Spun out of the hub messaging-apis _inbox cluster once it reached 3 coherent, no-other-home sources, all WhatsApp-platform infrastructure:

Founding corpus is 100% WhatsApp; domain framed as business/conversational messaging platforms & their APIs with WhatsApp as the deepest corner, broadenable to other channels. Founding Thing pages: whatsapp-business-platform (the platform), whatsapp-business-account (WABA), message-template, business-solution-provider (BSP roles), meta (owner/publisher).

Adjacency, not re-filed: the routed whatsapp-chatgpt-bot (a GPT-4o WhatsApp bot — an agent product, stays in agentic-tooling) and wassenger (a WhatsApp BSP/API vendor) ride on this platform; cross-linked both ways. The two parked _inbox records were deleted.

[2026-07-01] ingest | Wapi.go (WhatsApp Business API Go SDK)

See wapi-go. Go SDK abstracting the WhatsApp Business (Cloud) API — inbound messages/status/webhooks, account/template/phone-number management, multi-number two-way messaging, no hand-built payloads. By WapiKit. T2 (first-party SDK docs; license/maintainer detail thin on the intro page). Touched whatsapp-business-platform (client-SDK-over-platform), meta (upstream API owner). Cross-linked the agentic-tooling bot as the consumer of such SDKs.

[2026-07-01] ingest | WhatsApp Business Platform / WABA docs (Meta)

See whatsapp-business-platform-docs. Meta’s first-party Cloud API reference centered on the whatsapp-business-account: auth, phone numbers, message types, templates, webhooks, catalogs/commerce, calling, pricing, partner tiers. T1 vendor docs. Established the hub node whatsapp-business-platform and meta (owner).

[2026-07-01] ingest | WhatsApp Solution Partner / BSP get-started (Meta)

See whatsapp-solution-partner. Meta’s onboarding for the Solution-Partner role: embedded signup, permissions/access tokens, credit line, Tech-Provider vs Solution-Partner split. T1 vendor docs. Fleshed out business-solution-provider; cross-linked wassenger as a real-world BSP-class vendor.

[2026-07-30] ingest | four channel/pricing docs, batched — WhatsApp pricing, RCS ×2, Apple Messages

Research pass at the human’s request (“expand business messaging by means of research in net”) — the first sources this spoke has taken since it spun out on 2026-07-01, and the first not supplied by the human. Targets were chosen from this wiki’s own open questions: the unsourced pricing model, and whether non-WhatsApp channels exist to justify the broad domain.

Sources (all T1, all first-party operator documentation):

  • whatsapp-pricing-docs — Meta. Per-message billing replaced conversation-based pricing on 1 July 2025; category decides the rate; free inside the customer-service-window and in the 72-hour free entry point; volume tiers on utility/authentication.
  • rcs-business-messaging-docs — Google. Agents, APIs, Developer Console, and the carrier’s own administration role.
  • rcs-brand-verification — Google. The authorization email to a named individual at the brand, Google- vs carrier-managed launch, the verified checkmark.
  • apple-messages-for-business-docs — Apple. Brand/MSP/Apple roles, registration, the one-to-two week experience review, entry points, Apple Pay and pickers.

New pages (7): 4 sources + rcs-business-messaging · apple-messages-for-business · per-message-pricing · customer-service-window · sender-verification. Entity: apple (Corporation); google linked cross-wiki to llm-providers-wiki, not duplicated (1.00 index match). Budget: 1 of 8.

Updated: whatsapp-business-platform (pricing model, window, the three-channel frame) · message-template (category is now the billing unit) · business-solution-provider (the intermediary role across all three channels — optional on WhatsApp, mandatory on Apple) · synthesis · index.

Two of the spoke’s three open questions are now answered. Pricing is documented. And the breadth question resolves toward business messaging across channels: with three operators in hand, the gates turn out not to be WhatsApp-specific — each channel polices identity, content, and the intermediary, differing only in where it enforces (WhatsApp per message, Apple up front, RCS at launch with carriers holding a second veto). CLAUDE.md’s domain line and the hub registry were updated to match. The agentic-tooling seam question is untouched — no borderline source arrived.

Recorded weaknesses. The comparison is thin: one to two sources per non-WhatsApp channel against four for WhatsApp, so the symmetry in synthesis rests on a small corpus. No pricing is sourced for RCS or Apple, which leaves the “billing is policy” claim resting on one channel. Capabilities commonly attributed to RCS (carousels, typing indicators, carrier reach) are not in Google’s own docs and were deliberately left out; “server-to-server REST” for Apple is likewise a vendor gloss the primary page does not state.

avoid-ai-writing run over the new prose.

[2026-08-05] ingest | Chatery WhatsApp

Routed from the hub (runner-up: none — agentic-tooling-wiki was considered and does not apply, since the project contains no model). chatery-whatsapp — an Express.js 5 WhatsApp API backend over baileys 7.x: multi-session, Socket.IO events, group admin, media, queued bulk send, webhooks, OpenAPI docs, Docker. MIT, 214★, T3.

This is the spoke’s first source from outside the sanctioned path, and it is the most consequential ingest since the multi-channel turn. No WABA, no template approval, no BSP, nothing metered — it QR-pairs an ordinary WhatsApp account as a linked device and speaks the WhatsApp Web protocol.

Created baileys as a Thing page: the library is the actual subject here, and it is the second door into WhatsApp that every page in this wiki had implicitly assumed away. Added the comparison table (account / auth / business-initiated message / cost / identity gate / sanctioned) against the Cloud API path.

synthesis gained a section on the unofficial path and its first genuine contradiction: the founding thesis calls WhatsApp “a permissioned, metered channel, not an open socket,” and this source reaches the same users through something close to an open socket. Both recorded — they describe different doors. The thesis narrowed rather than broke: the gates sell permission and durability, not access. whatsapp-business-platform now carries the qualifier so the platform page cannot be read as the whole story.

Also resolved the open question about the agentic-tooling seam, though on an easy case — no model means transport by construction. Noted as such rather than as a real test.

Entities: created fajri-rinaldi-chan (Person; entity-index returned no match ≥ threshold). WhiskeySockets recorded as prose on the baileys page, not noded — a maintainer collective with no other evidence in the corpus. Budget: 1 of 8.

Caveat carried on both new pages: the README documents capabilities and is silent on the consequences — Meta’s terms prohibit unofficial clients, and no ban-rate, deliverability or enforcement data exists anywhere in this corpus.

Related pages

Links to