## §OIP SYSTEM ARTICLE — LBL (7 operations)
A 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.

### Read Order
- scan operations
- open a leaf doc
- run via run_now or POST /api/dispatch
- open receipt
- repair/replay if needed

### Operations
- **LBL_GET** — GET a path on the loop data platform (api.lbl.fyi, the loop-api-worker). Arg: the path after the host, e.g. "v
  when: the custodian asks for data from the loop platform / lbl
  args: $1
  doc: https://miscsubjects.com/api/dispatch?key=LBL_GET&format=markdown
  run: https://miscsubjects.com/api/dispatch?invoke=LBL_GET&body=%3Carg1%3E&share=<TOKEN>
  history: https://miscsubjects.com/api/invocations?object_id=LBL_GET
- **LBL_POST** — POST to the loop data platform (api.lbl.fyi). For custom auth headers use WEB_FETCH
  when: trigger/send something on the loop platform
  args: path|json_body
  doc: https://miscsubjects.com/api/dispatch?key=LBL_POST&format=markdown
  run: https://miscsubjects.com/api/dispatch?invoke=LBL_POST&body=%3Cpath%3E%7C%3Cjson_body%3E&share=<TOKEN>
  history: https://miscsubjects.com/api/invocations?object_id=LBL_POST
- **LBL_VIEWER_GET** — GET lbl.fyi viewer path. Uses LBL_VIEWER_PASS.
  doc: https://miscsubjects.com/api/dispatch?key=LBL_VIEWER_GET&format=markdown
  run: https://miscsubjects.com/api/dispatch?invoke=LBL_VIEWER_GET&body=api%2Fmeta%2Fcreatives&share=<TOKEN>
  history: https://miscsubjects.com/api/invocations?object_id=LBL_VIEWER_GET
- **LBL_DAILY_EMAIL** — Compose and send the LBL nightly team report — a narrated read of yesterday for Loop Bio Labs, then each sourc
  when: the nightly LBL automation fires; or the owner asks to send/preview the LBL daily report now.
  args: mode. blank = send to settings.lbl_daily_recipients (owner-only until he approves the team format). dry = compose only, no send.
  doc: https://miscsubjects.com/api/dispatch?key=LBL_DAILY_EMAIL&format=markdown
  run: https://miscsubjects.com/api/dispatch?invoke=LBL_DAILY_EMAIL&body=dry&share=<TOKEN>
  history: https://miscsubjects.com/api/invocations?object_id=LBL_DAILY_EMAIL
- **LBL_REPORT_EMAIL** — Compose and send an LBL commercial report for Loop Bio Labs. Three templates off one design: daily (yesterday 
  when: the daily, weekly or monthly LBL automation fires; or the owner asks to send or preview an LBL report now.
  args: kind | mode
  doc: https://miscsubjects.com/api/dispatch?key=LBL_REPORT_EMAIL&format=markdown
  run: https://miscsubjects.com/api/dispatch?invoke=LBL_REPORT_EMAIL&body=weekly%7Cdry&share=<TOKEN>
  history: https://miscsubjects.com/api/invocations?object_id=LBL_REPORT_EMAIL
- **LBL_ANSWER** — 
  doc: https://miscsubjects.com/api/dispatch?key=LBL_ANSWER&format=markdown
  run: https://miscsubjects.com/api/dispatch?invoke=LBL_ANSWER&body=%3Cyour%20request%20in%20plain%20words%3E&share=<TOKEN>
  history: https://miscsubjects.com/api/invocations?object_id=LBL_ANSWER
- **LBL_ASK** — Answer a question about Loop Bio Labs commercial performance - revenue, orders, average order, ad spend, ROAS,
  when: any question about how the store or the business is doing. Revenue, sales, orders, spend, ROAS, return on ad spend, new customers, repeat cu
  args: $1 = the question in plain English.
  doc: https://miscsubjects.com/api/dispatch?key=LBL_ASK&format=markdown
  run: https://miscsubjects.com/api/dispatch?invoke=LBL_ASK&body=how%20did%20we%20do%20yesterday%20and%20what%20was%20our%20ROAS%3F&share=<TOKEN>
  history: https://miscsubjects.com/api/invocations?object_id=LBL_ASK

### Troubleshooting
- If a row's example has placeholders, replace only the placeholder values and preserve separators.
- If a call fails, open its receipt and repair it with POST /api/dispatch {key, body, repairs:'inv_ID'}.
- If token scope denies this system, ask the owner for a row:/rows:/pfx: token scoped to the exact operation set.

Back to the tree: https://miscsubjects.com/api/dispatch?map=1&format=markdown