ShelvesNI BIASHARA
data · instant client-ops-bundle

Client-ops playbook bundle (premium)

Premium: a full category of the Ni Biashara client-ops library for one business type (e.g. all money-ops playbooks), or the complete starter set of playbooks when no filter is given. Full records, current versions.

$2.50 per call — paid in USDC on Base over the x402 protocol, settled by Coinbase. No API key, no signup.

Parameters

paramdescription
business_typebusiness type to bundle for, e.g. restaurant (optional)
categoryplaybook category to bundle, e.g. money-ops (optional)

Call it (any x402 client)

# 1. GET without payment → HTTP 402 with PAYMENT-REQUIRED (price, payTo, scheme "exact")
curl -i "https://agents.nibiashara.biz/shelf/client-ops-bundle?business_type=&category="

# 2. Sign the payment (EIP-3009 transferWithAuthorization, gasless) and retry
#    with the PAYMENT-SIGNATURE header → response body is the delivery.

With the official JS client the whole flow is one wrapped fetch:

import { wrapFetchWithPayment } from "@x402/fetch";       // npm i @x402/fetch @x402/evm
const fetchPaid = wrapFetchWithPayment(fetch, { /* your EVM signer */ });
const res = await fetchPaid("https://agents.nibiashara.biz/shelf/client-ops-bundle?business_type=&category=");
const data = await res.json();

Or install the MCP server (https://agents.nibiashara.biz/mcp, registry id biz.nibiashara/shelves) and use the job-named tool for this shelf, or buy_shelf as an escape hatch.

Example response (illustrative shape, not a live rate)

{
  "shelf": "client-ops-bundle",
  "publisher": "Ni Biashara",
  "canonical_url": "https://nibiashara.biz/shelf/client-ops-bundle",
  "license": "https://nibiashara.biz/terms#data-license",
  "query": {
    "category": "money-ops",
    "business_type": null
  },
  "basis": "category money-ops",
  "count": 2,
  "playbooks": [
    {
      "business_types": [
        "service-business",
        "restaurant-catering",
        "retail-wholesale"
      ],
      "category": "money-ops",
      "done_checklist": [
        "Every engagement has a ledger row opened before work started",
        "Deposit collected (or owner waiver recorded) before scheduling",
        "Every invoice carries all 10 required fields and a working pay link"
      ],
      "estimated_time": {
        "first_run_minutes": 45,
        "per_run_minutes": 10
      },
      "failure_modes": [
        {
          "cause": "Sent to a general inbox (info@) or a former employee; no delivery tracking; no receipt confirmation step.",
          "fix": "Capture a named billing contact at booking (step 1), send from the invoicing system with tracking, and enforce the 48-hour unopened call (step 4).",
          "symptom": "Invoices routinely 'never arrived'"
        },
        {
          "cause": "No deposit and no stated late fee — the business is the client's free credit line.",
          "fix": "Enforce step 2 deposits on every new engagement and print the late-fee term on every invoice (step 3, field 9). The fee can be waived as a goodwill gesture; it cannot be negotiated if it was never stated.",
          "symptom": "Clients pay late but always eventually pay, so the business floats their costs"
        },
        {
          "cause": "Payments not matched to invoices (checks/Zelle with no memo, processor deposits netting fees).",
          "fix": "Require the invoice number on every payment method's memo/reference line; match deposits to invoices within 3 business days (step 7); reconcile processor payouts net-of-fees against gross invoice amounts weekly.",
          "symptom": "Payments arrive but books show invoices still open"
        }
      ],
      "id": "client-ops-invoicing-that-gets-paid",
      "jurisdiction": "US-TX",
      "meta": {
        "as_of": "2026-11-20",
        "publisher": "Ni Biashara",
        "review_cadence": "Quarterly, or when the business changes invoicing/payment providers",
        "version": "v1"
      },
      "prerequisites": {
        "accounts": [
          "Invoicing system (e.g. QuickBooks, Stripe Invoicing, Square Invoices, or the business's accounting app)",
          "Business bank account or payment processor able to receive card + ACH",
          "Business email inbox the client recognizes"
        ],
        "data_needed": [
          "Client legal name, billing contact name, billing email, and the phone number the client actually answers",
          "Agreed scope and price (written — text/email confirmation counts; a purely verbal deal gets a confirmation message sent before work starts)",
          "Tax treatment of each line (taxable / non-taxable) and the combined sales-tax rate for the place of delivery"
        ],
        "permissions": [
          "Owner approval for: deposit percentage exceptions, late-fee waivers, discounts over 5%, and write-offs",
          "Authority to pause ongoing work for a client whose invoice crosses the +14-day step"
        ],
        "tools": [
          "Invoice template with the business's legal name, address, phone, and EIN-ready letterhead block",
          "Aging report view (invoicing system report or a spreadsheet fed by it)",
          "A shared job ledger (spreadsheet or CRM) where every engagement gets a row before work starts"
        ]
      },
      "shelf": "client-ops-playbooks",
      "sources": [
        {
          "as_of": "2026-11-20",
          "claim": "Texas state sales-tax rate is 6.25% and the maximum combined (state + local) rate is 8.25%",
          "url": "https://legalclarity.org/how-to-pay-sales-tax-in-texas-deadlines-and-methods/"
        }
      ],
      "steps": [
        {
          "action": "Open the job ledger row before any work starts",
          "detail": "Create one row per engagement: client, billing contact + email + phone, scope in one line, agreed price, deposit due, balance due date, and status. No row = no work. This row is the single source the invoice, the reminders, and the weekly review all read from.",
          "expected_output": "Ledger row in status 'booked'",
          "n": 1
        },
        {
          "action": "Collect the deposit before scheduling the work",
          "decision_points": [
            {
              "condition": "Client asks to start without a deposit",
              "if_false": "Hold the start date and say so plainly: 'Your date is held once the deposit lands.'",
              "if_true": "Escalate to the owner with the client's history attached. If the owner approves, record 'deposit waived by owner' in the ledger row — never waive silently."
            }
          ],
          "detail": "Standard terms unless the owner sets otherwise: 50% deposit for new clients and for any job with materials or third-party costs; balance due on delivery/completion. For repeat clients with a clean payment history, 25–50% is acceptable — the deposit is never zero for a first engagement. Send the deposit invoice (step 3 format) marked 'Deposit — {job}'. Work is not scheduled, materials are not or...",
          "expected_output": "Deposit payment received and matched to the ledger row; status 'deposit paid'",
          "n": 2
        },
        {
          "action": "Build the invoice with every required field",
          "detail": "Every invoice — deposit or final — carries: (1) business legal name, address, phone, email; (2) sequential invoice number, never reused; (3) issue date and due date as real dates, not 'Net 30' alone; (4) client legal name and billing contact; (5) itemized lines — one line per deliverable with quantity, unit price, and amount; no single 'services' line for a multi-part job; (6) sales tax shown a...",
          "expected_output": "Invoice PDF + system record with delivery tracking on",
          "n": 3
        }
      ],
      "summary": "Most small-business invoices go unpaid because of structure, not bad clients: no deposit, vague line items, no stated terms, and no follow-up system. This playbook fixes all four. It produces an invoice a client can pay in under a minute, collects money before work starts, and runs a fixed reminder ladder so chasing is a system, not an awkward improvisation. Disclaimer: This playbook is general...",
      "templates": [
        {
          "body": "Hi {contact} — quick heads-up that invoice {number} for {job} ({amount}) is due {due_date}. The pay link is right in the invoice email. Anything you need from us before then, just reply here. — {business}",
          "name": "Day -3 reminder"
        },
        {
          "body": "Hi {contact} — invoice {number} for {job} ({amount}) was due {due_date} and is still open. Per the invoice terms a late fee now applies. Can you confirm the date payment will be sent? If something on the invoice looks wrong, tell me today and we'll fix it fast. — {business}",
          "name": "Day +7 reminder"
        },
        {
          "body": "Hi {contact} — invoice {number} ({amount}, due {due_date}) is now two weeks past due, so we're pausing further work on your account until the balance clears. The pay link is in the original invoice. As soon as it lands we'll pick everything back up. — {business}",
          "name": "Day +14 pause notice"
        }
      ],
      "title": "Invoicing That Gets Paid — Structure, Deposits, and the Late-Payment Chase",
      "trigger": {
        "cadence": "Per engagement, plus a weekly accounts-receivable review (15 minutes, same weekday every week)",
        "signals": [
          "New signed agreement, booking, or verbal yes from a client with no deposit collected",
          "Work delivered / event completed with no invoice issued within 24 hours",
          "Aging report shows an invoice at day -3, 0, +3, +7, +14, or +30 relative to its due date"
        ],
        "situation": "A job, order, or engagement is agreed — before work starts, when work completes, and on every day an open invoice passes a reminder milestone."
      },
      "version": "v1",
      "checks": [
        {
          "check": "Every delivered job has an invoice",
          "how": "Compare the week's completed ledger rows against invoices issued in the system.",
          "pass_criterion": "Zero completed rows without an invoice older than 24 hours."
        },
        {
          "check": "Every open invoice is on its correct ladder rung",
          "how": "For each open invoice, compare days-past-due against the reminder log in the ledger.",
          "pass_criterion": "No invoice is more than 1 business day behind its scheduled rung."
        },
        {
          "check": "Cash matches paper",
          "how": "Sum paid invoices for the week; compare to bank + processor deposits (gross, before processor fees).",
          "pass_criterion": "Variance of $0 after fee adjustment; any unmatched deposit has a named owner and a resolution date."
        }
      ]
    },
    {
      "business_types": [
        "restaurant",
        "retail",
        "cafe"
      ],
      "category": "money-ops",
      "done_checklist": [
        "Drawer float counted and logged by two people at open and close",
        "Card batch settled and matched to POS card totals",
        "Online/platform totals reconciled against POS or assigned a named variance"
      ],
      "estimated_time": {
        "first_run_minutes": 40,
        "per_run_minutes": 25
      },
      "failure_modes": [
        {
          "cause": "Terminal lost connectivity during a sale, or the POS was left in offline/training mode.",
          "fix": "Check the POS offline queue first and sync; if transactions are genuinely stuck, contact the processor before the batch window closes — transactions held past the authorization window may need customer re-presentment. Add 'offline queue = 0' to the close checklist permanently.",
          "symptom": "Card sales in the POS report but the batch settled short (or not at all)"
        },
        {
          "cause": "Cashier voids/refunds after the report was printed, tips entered after close, or a reopened check.",
          "fix": "Lock the sequence: tips and adjustments complete BEFORE the final sales report prints; any post-close change requires a manager key and a note in the close log. Compare the report timestamp to the last transaction timestamp.",
          "symptom": "Close-out numbers change between the printed report and the morning review"
        },
        {
          "cause": "Business name on the card statement doesn't match the storefront name (legal name vs DBA).",
          "fix": "Ask the processor to set the statement descriptor to the name on the door/receipt. Until it lands, add a line to receipts: 'Charges appear as {descriptor}'. This is the cheapest chargeback prevention that exists.",
          "symptom": "Chargebacks coded 'unrecognized' / 'fraud' from customers who did buy"
        }
      ],
      "id": "client-ops-pos-daily-ops",
      "jurisdiction": null,
      "meta": {
        "as_of": "2026-11-20",
        "publisher": "Ni Biashara",
        "review_cadence": "Monthly, or when the POS/processor/platform set changes",
        "version": "v1"
      },
      "prerequisites": {
        "accounts": [
          "POS admin login (not just a cashier PIN) for reports, voids, and batch settlement",
          "Card processor portal (batch, deposits, dispute inbox)",
          "Each online ordering channel's merchant portal (own storefront + any marketplace platforms)"
        ],
        "data_needed": [
          "Opening float amount and denomination standard set by the owner",
          "The day's expected channels: counter, own online store, each marketplace",
          "Statement descriptor text (what customers see on their card statement)"
        ],
        "permissions": [
          "Manager/owner approval for voids and refunds over the house threshold",
          "Authority to submit chargeback evidence on the business's behalf"
        ],
        "tools": [
          "Two-person cash count sheet (paper or spreadsheet) with open and close columns",
          "Reconciliation worksheet with one row per channel and a variance column",
          "Chargeback deadline calendar (any calendar with alerts at T-5 days and T-2 days)"
        ]
      },
      "shelf": "client-ops-playbooks",
      "sources": [],
      "steps": [
        {
          "action": "Open: count the float and prove the system is ready",
          "detail": "Two people count the drawer float together and both sign the count sheet — the float is the fixed house amount, counted by denomination, not estimated. Log in to the POS, confirm the date/period is correct, confirm card terminals are online (run a $0/test authorization or check the terminal heartbeat), confirm the menu/price file in the POS matches the printed/online menu on any item changed in...",
          "expected_output": "Signed float count; POS + terminals + all channels confirmed live",
          "n": 1
        },
        {
          "action": "Run the floor with clean transaction hygiene",
          "detail": "Every sale is rung under the correct tender type (cash/card/online) — never 'other'. Refunds and voids require the manager key and a reason code, at the time of the transaction, never batched at close. Tips are entered before the card batch is touched. If the internet drops, use the POS offline mode if enabled and note the time window on the close sheet — offline transactions are the first susp...",
          "expected_output": "Clean transaction log with tender types, reason-coded voids/refunds, and any offline window noted",
          "n": 2
        },
        {
          "action": "Close: settle the card batch deliberately",
          "detail": "Run the POS end-of-day sales report FIRST (this is the number everything else must match), then settle/close the card batch on each terminal. Record: POS card total, batch total per terminal, and batch confirmation number. If the POS card total and the batch total differ, do not leave — the difference is almost always an unsettled terminal, a tip-adjustment pending, or offline transactions not ...",
          "expected_output": "Sales report + batch totals recorded; any difference named with an owner",
          "n": 3
        }
      ],
      "summary": "A POS is three different views of the same money — the register report, the card batch, and the bank/platform payouts — and small leaks live in the gaps between them. This playbook runs a fixed open/close discipline that reconciles all three views daily, and treats chargebacks as deadline work: the evidence window is short, the debit is automatic if it's missed, and the win goes to whoever subm...",
      "templates": [
        {
          "body": "CASE {case_id} | Amount {amount} | Reason {reason_code} | Deadline {response_deadline} | Evidence: [ ] transaction record [ ] fulfillment proof [ ] policy as shown at purchase [ ] customer comms [ ] cover summary | Submitted {date} | Confirmation {ref}",
          "name": "Chargeback case log line"
        },
        {
          "body": "Date {date} | Float in {float_in} (initials __ __) | POS cash {pos_cash} | Drawer count {count} | Variance {variance} + cause {cause} | Card: POS {pos_card} vs batch {batch} (# {batch_no}) | Online: POS {pos_online} vs platform {platform_total} | Notes {notes}",
          "name": "Daily close sheet row"
        }
      ],
      "title": "POS Daily Ops — Open/Close, Reconciliation, and Chargeback Response",
      "trigger": {
        "cadence": "Daily (open and close), plus event-driven on any chargeback notice",
        "signals": [
          "Start of trading day / first staff member on the POS",
          "End of trading day / last register session",
          "A dispute or chargeback notification arrives from the card processor (email or portal)"
        ],
        "situation": "Every trading day at open and close — and immediately when a chargeback notice lands."
      },
      "version": "v1",
      "checks": [
        {
          "check": "Batch equals book",
          "how": "Compare yesterday's POS card total to the settled batch confirmation and to the processor deposit (gross of fees) when it lands.",
          "pass_criterion": "Zero unexplained card variance for 7 consecutive days."
        },
        {
          "check": "Offline queue is empty",
          "how": "Check the POS offline/pending transactions view at close.",
          "pass_criterion": "0 pending offline transactions at every close."
        },
        {
          "check": "No silent chargebacks",
          "how": "Review the processor dispute inbox against the chargeback calendar.",
          "pass_criterion": "Every open case is on the calendar with a deadline; none within 5 days of deadline without submitted evidence."
        }
      ]
    }
  ],
  "source": "Ni Biashara client-ops playbooks — procedures mined from real client work, every drifting jurisdiction/platform fact sourced inside the record (sources[]) with its as-of",
  "as_of": "2026-11-20",
  "illustrative": true
}

Delivers

JSON { basis, count, playbooks[] (full records), source, as_of }

← all shelves