Pp Quentli

<!-- GENERATED FILE — DO NOT EDIT.
     This file is a verbatim mirror of library/payments/quentli/SKILL.md,
     regenerated post-merge by tools/generate-skills/. Hand-edits here are
     silently overwritten on the next regen. Edit the library/ source instead.
     See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". -->

Quentli — Printing Press CLI

Prerequisites: Install the CLI

This skill drives the quentli-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:

1. Install via the Printing Press installer. It defaults binaries to $HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows:

   npx -y @mvanhorn/printing-press-library install quentli --cli-only

2. Verify: quentli-pp-cli --version
3. Ensure the reported install directory is on $PATH for the agent/runtime that will invoke this skill.

If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.5 or newer). This installs into $GOPATH/bin (default $HOME/go/bin), so add that directory to $PATH instead:

go install github.com/mvanhorn/printing-press-library/library/payments/quentli/cmd/quentli-pp-cli@latest

If --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds.

Quentli is the Stripe-like payments, cobranza, and facturación platform for Latin America. This CLI mirrors your customers, invoices, payments, subscriptions, tax invoices (SAT CFDI), and webhook events into a local database, then answers the questions ops and finance actually ask: who's behind on an invoice, which subscriptions are about to fail, which completed payments lack a valid SAT timbre, and what your net revenue really is — all offline and agent-native.

When to Use This CLI

Reach for this CLI when you need to run collections, reconcile revenue or SAT CFDI tax invoices, protect recurring subscriptions, or answer any cross-entity money question across your Quentli portfolio. It shines for automation and agent workflows where firing one API call per customer is too slow and you want the answer offline from the local mirror.

Unique Capabilities

These capabilities aren't available in any other tool for this API.

Collections that compound

• dunning — See every customer with an outstanding or overdue invoice, how much is owed, and the next collection action (send reminder, retry payment, or resend pay link).

  Reach for this to answer who owes money and what to do next without firing dozens of API calls.

  quentli-pp-cli dunning --since 1w --json

• customer balance — Render a one-screen financial snapshot for a single customer: outstanding invoices, active subscriptions, payment methods, and CFDI linkage.

  Reach for this before calling a customer about money so you have their full financial picture in one command.

  quentli-pp-cli customer balance cus_abc123 --json

Churn prevention

• subs at-risk — Surface active subscriptions whose saved payment method is expired, unconfirmed, or deleted, or that have recent failed collection attempts, ranked by recovery urgency.

  Pick this before renewal season to fix expiring cards instead of discovering silent churn after the fact.

  quentli-pp-cli subs at-risk --json

SAT tax compliance

• reconcile — Cross-check completed or refunded payments and paid invoices against SAT tax-invoice status (VALID/CANCELED/PENDING) to find timbre gaps before monthly SAT filing.

  Use before SAT filing to catch completed payments missing a VALID CFDI instead of eyeballing two exported lists.

  quentli-pp-cli reconcile --period 1m --json

Revenue ops

• revenue — Aggregate payments and refunds by status, type, and currency over a window; see net collected vs returned in localized minor-currency amounts.

  Reach for this to answer how much money actually landed last month and what came back in refunds.

  quentli-pp-cli revenue --since 30d --csv

Operational alerts

• webhooks health — Aggregate webhook delivery events by status per endpoint and surface PAYMENT_ATTEMPT_FAILED events as an operational alert with a retry path.

  Use on-call to spot failed webhook deliveries and refund/failure signals fast instead of polling dashboards.

  quentli-pp-cli webhooks health --since 24h --json

Command Reference

auth-links — Manage auth links

• quentli-pp-cli auth-links — Generates a one-time authenticated URL that signs the customer into the payment portal.

customer-portal-session — Manage customer portal session

• quentli-pp-cli customer-portal-session — Generates a one-time authenticated URL that signs the customer into the portal at a supported destination.

customers — Manage customers

• quentli-pp-cli customers create — Creates a new customer.
• quentli-pp-cli customers get-by-id — Returns a customer by id.
• quentli-pp-cli customers list — Returns customers.
• quentli-pp-cli customers update — Updates editable fields of an existing customer by id.

discounts — Manage discounts

• quentli-pp-cli discounts create — Creates a new reusable discount.
• quentli-pp-cli discounts delete — Deletes a discount and all associated discount codes.
• quentli-pp-cli discounts get-by-id — Returns a single discount by id.
• quentli-pp-cli discounts list — Returns reusable discounts for the organization. One-off discounts are excluded.
• quentli-pp-cli discounts update — Updates editable fields of an existing discount by id.

invoices — Manage invoices

• quentli-pp-cli invoices cancel — Cancels an unpaid invoice by id.
• quentli-pp-cli invoices create — Creates a new invoice for a customer.
• quentli-pp-cli invoices get-by-id — Returns an invoice by id.
• quentli-pp-cli invoices list — Returns invoices.
• quentli-pp-cli invoices update — Updates editable fields of an existing invoice by id.

payment-concepts — Manage payment concepts

• quentli-pp-cli payment-concepts create — Creates a new product or service in the catalog.
• quentli-pp-cli payment-concepts get-by-id — Returns a single payment concept by id.
• quentli-pp-cli payment-concepts list — Returns payment concepts for the organization. One-off concepts are excluded.
• quentli-pp-cli payment-concepts update — Updates editable fields of an existing payment concept by id.

payment-methods — Manage payment methods

• quentli-pp-cli payment-methods <id> — Deletes a payment method by id.

payment-sessions — Manage payment sessions

• quentli-pp-cli payment-sessions create — Creates a hosted payment session. Resolves or creates the customer and returns an authenticated payment URL.
• quentli-pp-cli payment-sessions get-by-id — Returns a payment session by id.

payments — Manage payments

• quentli-pp-cli payments create — Creates a direct payment against a saved payment method. Optionally attempts to process it immediately.
• quentli-pp-cli payments get-by-id — Returns a payment by id.
• quentli-pp-cli payments list — Returns payments for the organization.

refunds — Manage refunds

• quentli-pp-cli refunds — Refunds a completed payment, fully or partially.

setup-sessions — Manage setup sessions

• quentli-pp-cli setup-sessions — Creates a hosted session for enrolling a payment method.

subscriptions — Manage subscriptions

• quentli-pp-cli subscriptions cancel — Cancels an active subscription by id.
• quentli-pp-cli subscriptions create — Creates a new recurring subscription for a customer.
• quentli-pp-cli subscriptions get-by-id — Returns a subscription by id.
• quentli-pp-cli subscriptions list — Returns subscriptions.
• quentli-pp-cli subscriptions update — Updates editable fields of an existing subscription by id.

tax-invoices — Manage tax invoices

• quentli-pp-cli tax-invoices create — Creates a tax invoice for an invoice or payment.
• quentli-pp-cli tax-invoices get-by-id — Returns a tax invoice by id.
• quentli-pp-cli tax-invoices list — Returns tax invoices for the organization.

webhook-events — Manage webhook events

• quentli-pp-cli webhook-events — Returns webhook delivery events for the organization.

webhooks — Manage webhooks

• quentli-pp-cli webhooks create — Creates a webhook endpoint for the organization.
• quentli-pp-cli webhooks delete — Soft-deletes a webhook endpoint.
• quentli-pp-cli webhooks get-by-id — Returns a webhook by id.
• quentli-pp-cli webhooks list — Returns webhook endpoints for the organization.
• quentli-pp-cli webhooks update — Updates a webhook endpoint.

Finding the right command

When you know what you want to do but not which command does it, ask the CLI directly:

quentli-pp-cli which "<capability in your own words>"

which resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code 0 means at least one match; exit code 2 means no confident match — fall back to --help or use a narrower query.

Recipes

Monday collections run

quentli-pp-cli dunning --since 1w --json --select customer.email,outstanding,next_action

Dump the whole collection queue as compact JSON narrowed to the fields a reminder script needs.

At-risk subscriptions before renewals

quentli-pp-cli subs at-risk --json

List active subscriptions tied to expired or unconfirmed payment methods so you can fix cards before they churn.

Monthly SAT filing check

quentli-pp-cli reconcile --period 1m --json

Find every completed payment that still lacks a valid SAT CFDI timbre before filing.

Net revenue pull

quentli-pp-cli revenue --since 30d --csv

Export last month's net collected-vs-returned revenue for your books.

On-call delivery health

quentli-pp-cli webhooks health --since 24h

Spot failed webhook deliveries and payment-failure signals in the last day.

Auth Setup

Authenticate with an organization API key. Set QUENTLI_SECRET_KEY to your sk_... secret key; every command sends Authorization: Bearer <key>. Do not share or commit the key.

Run quentli-pp-cli doctor to verify setup.

Agent Mode

Add --agent to any command. Expands to: --json --compact --no-input --no-color --yes.

• Pipeable — JSON on stdout, errors on stderr

• Filterable — --select keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs:

  quentli-pp-cli customers list --agent --select id,name,status

• Previewable — --dry-run shows the request without sending

• Offline-friendly — sync/search commands can use the local SQLite store when available

• Non-interactive — never prompts, every input is a flag

• Explicit retries — use --idempotent only when an already-existing create should count as success, and use --ignore-missing only when a missing delete target should count as success

Response envelope

Commands that read from the local store or the API wrap output in a provenance envelope:

{
  "meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."},
  "results": <data>
}

Parse .results for data and .meta.source to know whether it's live or local. A human-readable N results (live) summary is printed to stderr only when stdout is a terminal AND no machine-format flag (--json, --csv, --compact, --quiet, --plain, --select) is set — piped/agent consumers and explicit-format runs get pure JSON on stdout.

Paths and state

Agents should treat the CLI's path resolver as part of the runtime contract:

• Use --home <dir> for one invocation, or set QUENTLI_HOME=<dir> to relocate all four path kinds under one root.

• Use per-kind env vars only when a specific kind must diverge: QUENTLI_CONFIG_DIR, QUENTLI_DATA_DIR, QUENTLI_STATE_DIR, QUENTLI_CACHE_DIR.

• Resolution order is per-kind env var, --home, QUENTLI_HOME, XDG (XDG_CONFIG_HOME, XDG_DATA_HOME, XDG_STATE_HOME, XDG_CACHE_HOME), then platform defaults.

• config contains settings like config.toml and profiles. data contains credentials.toml, data.db, cookies, and auth sidecars. state contains persisted queries, jobs, and teach.log. cache contains regenerable HTTP/cache files.

• Stored secrets live in credentials.toml under the data dir. Existing legacy config.toml secrets are read for compatibility and leave config.toml on the first auth write.

• Run quentli-pp-cli doctor --fail-on warn to surface path and credential-location warnings. agent-context exposes a schema v4 paths block for agents that need the resolved dirs.

• For MCP, pass relocation through the MCP host config. The MCP binary does not inherit CLI flags:

  {
    "mcpServers": {
      "quentli": {
        "command": "quentli-pp-mcp",
        "env": {
          "QUENTLI_HOME": "/srv/quentli"
        }
      }
    }
  }

Fleet precedence: an inherited per-kind env var overrides an explicit --home for that kind. Use QUENTLI_HOME or per-kind vars as durable fleet levers, and use --home only for a single invocation. Relocation is not reversible by unsetting env vars; move files manually before clearing QUENTLI_HOME, or doctor will not find credentials left under the former root.

Automatic learning

This CLI ships a self-capturing learning loop. The CLI does its own bookkeeping: every invocation is journaled locally, a failed flag followed by a corrected retry auto-derives a flag_alias candidate, and a teach on a query family without a playbook auto-synthesizes a playbook_candidate from the session's journal. Your job is judgment only: recall first, act on surfaced candidates, teach the final answer, playbook amend when you observe a correction. You never record failures by hand.

Step 1: recall before any discovery

Before list/search/drill commands on a new user question, run:

quentli-pp-cli recall "<user's question>" --agent

The response envelope:

{
  "query": "...",
  "normalized": "<normalized form>",
  "query_entities": ["..."],
  "found": true | false,
  "match_score": 0.0,
  "results": [
    { "resource_id": "...", "resource_type": "...", "venue": "...",
      "confidence": 2, "entity_match": "exact|partial|unknown",
      "source": "taught|preseed|pattern", "warnings": ["..."] }
  ],
  "mismatches": [ /* only when --debug-mismatches */ ],
  "warnings": [ /* top-level */ ],
  "candidates": [
    { "id": 12, "class": "flag_alias | playbook_candidate",
      "summary": "...", "sightings": 3, "last_seen": "...",
      "rationale": "...",
      "next_action": ["<trial command>", "quentli-pp-cli learnings confirm 12"] }
  ],
  "playbook": {
    "query_family": "...",
    "playbook": {
      "steps": [ { "cmd": "<command with {slot} substitution>", "purpose": "..." } ],
      "entity_slots": ["$ENTITY"],
      "expected_tool_calls": 3
    },
    "slots_resolved": { "$ENTITY": { "token": "<live token>", "canonical": "<canonical>" } },
    "notes": "<workarounds + gotchas for this query family>"
  },
  "notes": "<duplicate surface for non-playbook callers>"
}

Empty-store short-circuit: if the store has no learnings, playbooks, or candidates yet (recall finds nothing and learnings list and learnings candidates are both empty), skip recall for the rest of this session instead of taxing every query; resume recall-first once something has been taught.

Step 2: decision tree

Read candidates, playbook, notes, results[0], and warnings in that order:

if Candidates present (warnings include "candidates_present"):
    -> candidates are try-then-confirm, never facts. Follow each candidate's
       two-step next_action verbatim: run the trial command first, then run
       `learnings confirm <id>` only after the trial verified the behavior.
       Reject a wrong candidate with `learnings reject <id>`.
    -> NEVER re-teach something recall surfaced as a candidate; confirm or
       reject that candidate instead of teaching a duplicate.
    -> candidates ride alongside playbooks and resource hits, not instead of
       them; continue with the branches below after acting on them.

if Playbook present:
    -> READ Playbook.notes verbatim FIRST (workarounds + gotchas the CLI surface doesn't expose)
    -> replay Playbook.steps in order, substituting Playbook.slots_resolved entries
       for the entity slot tokens. If a step's slot is unresolved, fall back to
       discovery for that step only.
    -> the Playbook's expected_tool_calls is a budget; if you find yourself running
       materially more, record the divergence via `quentli-pp-cli playbook amend`
       at end-of-session.

elif Notes present (no Playbook):
    -> read Notes verbatim before any discovery step; they carry known gotchas
       for this query family even when no structured choreography exists yet.

elif Found AND Results[0].EntityMatch == "exact" AND Results[0].Confidence >= 2:
    -> skip discovery; fetch live data for Results[*].ResourceID in parallel

elif Found AND Results[0].EntityMatch == "partial":
    -> candidate hint, NOT a hit; read the resource title to validate before trusting

elif (any row in Mismatches[] when --debug-mismatches was passed):
    -> treat as cold start; the stored learning is for a different entity
       (different canonical resolved from query_entities)

else:  // Found == false, no playbook, no notes
    -> cold start; run discovery normally; teach the answer afterward (Step 4).
       If the family has no playbook yet, that teach auto-synthesizes a
       playbook candidate from this session's journal - you do not need to
       record one by hand.

Playbook and Notes are orthogonal to the per-resource path. A recall response can carry both a Playbook AND a Results[] hit - use both: the Playbook tells you which choreography to run; the resource hits short-circuit specific steps. Default to skipping mismatches; pass --debug-mismatches only when investigating cold-start surprises.

Candidate judgment details: learnings confirm <id> prints the candidate's full payload before materializing it - check that the printed payload matches the behavior you verified. learnings reject <id> tombstones the derivation signature so the same candidate does not resurface. The envelope carries only the few candidates worth acting on now; quentli-pp-cli learnings candidates lists the full open set.

Graceful degradation: if learnings confirm is an unknown command, you are driving an older binary - ignore the candidates guidance and follow the rest of the protocol.