ShelvesNI BIASHARA
data · instant client-ops-catalog

Client-ops playbook catalog

The searchable index of the Ni Biashara client-ops playbook library: invoicing, POS daily operations, Google Business Profile upkeep and Texas local compliance — titles, categories, business types, triggers, jurisdictions, versions and review cadences. The discovery shelf for the playbook family.

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

Parameters

paramdescription
qfree text over title, summary and category (optional)
business_typebusiness type on the record, e.g. restaurant (optional)
categoryplaybook category, e.g. money-ops, presence-ops, compliance-ops (optional)
jurisdictionjurisdiction on the record, e.g. US-TX (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-catalog?q=&business_type=&category=&jurisdiction="

# 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-catalog?q=&business_type=&category=&jurisdiction=");
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.

Calling this repeatedly? Buy a Shelf Pass once ($0.99 for 110 credits) and send X-SHELF-PASS: <token> instead of paying per call — this shelf costs 10 credits per call.

Example response (illustrative shape, not a live rate)

{
  "shelf": "client-ops-catalog",
  "publisher": "Ni Biashara",
  "canonical_url": "https://nibiashara.biz/shelf/client-ops-catalog",
  "license": "https://nibiashara.biz/terms#data-license",
  "query": {
    "q": null,
    "category": null,
    "business_type": null,
    "jurisdiction": null
  },
  "count": 4,
  "playbooks": [
    {
      "id": "client-ops-google-business-profile-updates",
      "title": "Google Business Profile Updates — Hours, Photos, Posts, and Review Responses",
      "category": "presence-ops",
      "business_types": [
        "restaurant",
        "retail",
        "cafe"
      ],
      "jurisdiction": null,
      "trigger": {
        "cadence": "Weekly maintenance (20 min) + monthly photo/content run (30 min) + review responses within 24–48 hours of posting",
        "signals": [
          "Weekly cadence tick (same weekday as the AR review works well)",
          "A new Google review notification arrives",
          "A holiday, weather event, or schedule change affects opening hours"
        ],
        "situation": "Ongoing ownership of the business's Google presence — a weekly maintenance run, a monthly photo/content run, and immediate runs when hours change or a review lands."
      },
      "summary": "For most local businesses the Google Business Profile is the storefront: it is what Maps and Search show before the website, and it carries the hours, photos, and reviews customers act on. Stale hours and unanswered reviews are silent revenue loss. This playbook runs a fixed weekly/monthly discipline that keeps the profile accurate, fresh, and responded-to — and inside Google's rules, so the li...",
      "estimated_time": {
        "first_run_minutes": 60,
        "per_run_minutes": 20
      },
      "version": "v1",
      "as_of": "2026-11-20",
      "review_cadence": "Quarterly, or when Google changes profile features/policies"
    },
    {
      "id": "client-ops-invoicing-that-gets-paid",
      "title": "Invoicing That Gets Paid — Structure, Deposits, and the Late-Payment Chase",
      "category": "money-ops",
      "business_types": [
        "service-business",
        "restaurant-catering",
        "retail-wholesale"
      ],
      "jurisdiction": "US-TX",
      "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."
      },
      "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...",
      "estimated_time": {
        "first_run_minutes": 45,
        "per_run_minutes": 10
      },
      "version": "v1",
      "as_of": "2026-11-20",
      "review_cadence": "Quarterly, or when the business changes invoicing/payment providers"
    },
    {
      "id": "client-ops-pos-daily-ops",
      "title": "POS Daily Ops — Open/Close, Reconciliation, and Chargeback Response",
      "category": "money-ops",
      "business_types": [
        "restaurant",
        "retail",
        "cafe"
      ],
      "jurisdiction": null,
      "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."
      },
      "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...",
      "estimated_time": {
        "first_run_minutes": 40,
        "per_run_minutes": 25
      },
      "version": "v1",
      "as_of": "2026-11-20",
      "review_cadence": "Monthly, or when the POS/processor/platform set changes"
    }
  ],
  "library_size": 4,
  "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 { count, playbooks[] (id, title, category, business_types, jurisdiction, trigger, summary, version, as_of, review_cadence), library_size, source, as_of }

← all shelves