# io.github.lonniev/beesknees-mcp

> The Bee's Knees — a monetized multiplayer race to the queen, on Tollbooth DPYC

- name: io.github.lonniev/beesknees-mcp
- version: 0.3.2
- connection class: R2 (oauth_consent_once)
- trust: 94/100
- quality: 70/100 (needs work)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.lonniev%2Fbeesknees-mcp
- tools: https://api.protogrid.dev/v1/servers/io.github.lonniev%2Fbeesknees-mcp/tools

**An agent can connect after a one-time OAuth consent by a human.** Remote endpoint behind OAuth 2. Tokens stay with the agent; the registry only exposes the authorization metadata.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "beesknees-mcp": {
      "type": "http",
      "url": "https://beesknees-mcp.fastmcp.app/mcp"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 100
- freshness: 100
- provenance: 80
- drivers: +repository +namespace-matches-repo +reachable +uptime-100% +updated-16d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 70/100 (needs work)

### protocol: n/a (weight 25)

- n/a `protocol.modern`, `protocol.stateless`, `protocol.transport`, `protocol.list_ttl`: no remote answered a protocol handshake (not probed yet, unreachable, or local-only)

### authorization: 83 (weight 15)

- pass `auth.prm`: Protected Resource Metadata (RFC 9728) published
- pass `auth.as_metadata`: authorization server metadata reachable
- warn `auth.cimd`: only Dynamic Client Registration, deprecated in 2026-07-28 in favour of CIMD
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 86 (weight 30)

- pass `tools.descriptions`: every tool has a description
- warn `tools.description_length`: 4 tools have descriptions over 1,024 characters, which crowds the context
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 71 of 71 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- warn `tools.token_cost`: about 17,567 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 25 (weight 15)

- warn `stability.changes`: 72 tool changes in 30 days
- fail `stability.rug_pull`: 1 tools kept their name but changed most of their description in 30 days; review before trusting them

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 71, about 17,567 tokens to load them all
- tool set hash: 9846440097b8c2cb8f96c636f8c32035
- tools last changed: 2026-10-15T00:04:00.903Z
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.lonniev/beesknees-mcp.svg)](https://protogrid.dev/servers/io.github.lonniev/beesknees-mcp)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-15 `beesknees_find_honey` changed (title, inputSchema, annotations)
- 2026-10-15 `beesknees_set_payout` changed (title, inputSchema, annotations)
- 2026-10-15 `beesknees_payout` changed (title, inputSchema, annotations)
- 2026-10-15 `beesknees_set_charity` changed (title, inputSchema, annotations)
- 2026-10-15 `beesknees_payout_history` changed (title, inputSchema, annotations)
- 2026-10-15 `beesknees_pay_charity` changed (title, inputSchema, annotations)
- 2026-10-15 `beesknees_pay_out` changed (title, inputSchema, annotations)
- 2026-10-15 `beesknees_treasury` changed (title, inputSchema, annotations)
- 2026-10-15 `beesknees_charity` changed (title, inputSchema, annotations)
- 2026-10-15 `beesknees_tick` changed (title, inputSchema, annotations)

Full history: https://api.protogrid.dev/v1/servers/io.github.lonniev%2Fbeesknees-mcp/changes

## Remotes

- https://beesknees-mcp.fastmcp.app/mcp (streamable-http, auth oauth2, reachable true, uptime30d 1)

## Packages

_none_

## Tools (71)

- `beesknees_account_statement`: Generate a patron's account statement at this operator.

Returns the patron's purchase history, active credit tranches,
per-tool usage breakdown, and recent daily usage logs. This is
the patron's spending account — not the operator's Authority
tax balance.

Free — no credits consumed. Proof of npub ownership is required
to prevent statement-scraping of arbitrary patrons.
- `beesknees_account_statement_infographic`: Generate a visual SVG infographic of your account statement.

Returns the same data as account_statement, rendered as a dark-themed
SVG graphic with balance hero, metrics cards, health gauge, tranche
table, and tool usage breakdown. Costs 1 api_sat per call. Proof is
verified by ``debit_or_deny`` before any cost is incurred.
- `beesknees_adoption_status`: Check this operator's adoption-request status at a chosen Authority.

Free. Polls the Authority MCP-to-MCP for the status of this operator's
request (pending / approved / rejected / provisioned).
- `beesknees_charity`: Who the charity share goes to, and where to check them.

Free on purpose. A claim about where somebody's money goes that costs money
to verify is not a claim anybody should have to take on trust.
- `beesknees_check_authority_balance`: Check this operator's tax balance at the Authority.

Returns the sats available for certifying patron credit purchases.
When this balance reaches zero, patron top-ups cannot be certified
and the operator must call purchase_credits on the Authority.

This is the operator's own funding — not a patron balance. Free.
- `beesknees_check_balance`: Check a patron's credit balance at this operator.

This is the patron's spending balance — credits purchased via
Lightning for tool calls at this operator. For the operator's
own balance at the Authority (needed to certify patron purchases),
use authority_check_balance instead.

Free — no credits required. Proof of npub ownership is required
to prevent anyone-with-the-registry from enumerating balances.
- `beesknees_check_now`: Ask the hives to advance now rather than at the next tick.

Carries no authority: it can only cause work that was already due — start a
match whose grace has run out, or end one whose ceiling has fallen.
- `beesknees_check_payment`: Check the payment status of a Lightning invoice.

Call after paying the invoice from purchase_credits.
Free — no credits required. Proof of npub ownership is required
to prevent credit-grant front-running by an observer of the
invoice ID.
- `beesknees_check_price`: Preview the effective cost of a tool call.

Shows the base cost and any constraint effects (discounts, free
trials, surge pricing). Free — no credits required.
- `beesknees_check_proof_status`: Check whether a proof grant is still valid.

Mirrors ``check_oauth_status`` for the npub-proof flow: a calling
agent can ask "will my next paid call accept this dpop_token?"
before burning credits on a guaranteed failure. Expiry is read from
the grant itself; the only store consulted is the patron's
revocation watermark.

Free, no side effects — touches no relay.
- `beesknees_claim_prize`: Take the winner's share as credit, or send it on to the charity.
- `beesknees_delete_coupon`: Delete a coupon.  Cascades to all patron redemptions.

Any chain step referencing the deleted coupon_id becomes a
no-op (the constraint returns neutral on unknown ids) — the
Studio surfaces orphan references as warnings.

RESTRICTED to operator — requires proof.
- `beesknees_delete_operator_credential`: Remove a single operator secret field.

Deletes one key from the operator's encrypted credential blob without
touching the others — the field-level counterpart to
``forget_credentials``, which wipes the whole row. Use it to retire a
leftover after an SDK cutover (a Prefect key after Modal, or a stored
but untemplated orphan like ``anthropic_api_key``) without taking the
operator down for a full re-delivery.

Stored-but-untemplated fields are first-class: the delete is keyed on
what is vaulted, not on what the current template declares. Idempotent
— already-absent fields report ``removed: false`` without rewriting
the vault. RESTRICTED to the operator — requires the operator's proof
(a kind-27235 event or a proof grant); patron proofs are rejected.
A deletion is as destructive as a write.
- `beesknees_delete_patron_credential`: Remove a single patron credential field.

Deletes one field from stored credentials without affecting
other fields. Free. Proof of npub ownership is required —
this is a write to the patron's sensitive credential vault.
- `beesknees_dig`: Cut one fresh cell of comb — slower than flying, and open to everyone after.
- `beesknees_find_honey`: Three honey sellers near a place, each with an address and a website.

Four directories hold a corner of the answer each — the USDA's local-food
listings, OpenStreetMap, Google Places and sellers' own Nostr listings — so
this asks all four at once, merges what agrees, checks that each website
still answers and ranks by evidence, completeness, agreement and distance.
`sources` says who answered; `verify` on a seller says what to check first.

A place that does not resolve, or a radius with nothing in it, is a
refusal and the fare goes back. The game is a race for honey; this is
where the real thing is.
- `beesknees_fly`: Move one cell through open air or an open tunnel.
- `beesknees_forget_coupon`: Remove a coupon from this patron's redemption list.

Cosmetic only — the coupon itself still exists at the operator,
and the patron can re-redeem the same code later while the
window allows.  Free — requires proof of ``npub``.
- `beesknees_forget_credentials`: Delete vaulted credentials for a specific service and npub.

For operator credentials, pass the operator's own npub. For patron
credentials, pass the patron's npub. Always requires proof of
npub ownership — a deletion is as destructive as a write.
- `beesknees_get_nostr_profile`: Read an npub's public Nostr profile (NIP-01 kind-0 metadata).

Free, no proof — the data is already public on relays. Returns the
latest metadata fields (name, display_name, about, picture, banner,
nip05, website, lud16) or an empty profile if none is published.
- `beesknees_get_notarization_proof`: Generate a Merkle inclusion proof that a patron's balance was
included in a Bitcoin-notarized snapshot.
- `beesknees_get_operator_onboarding_status`: Report this operator's configuration readiness.

Shows which operator settings are configured, which are missing,
and how to deliver each missing value. For patron-level credential
status, use get_patron_onboarding_status instead. Free.
- `beesknees_get_patron_credential_fields`: List stored patron credential field names (not values).

Returns the names of fields stored for a patron, plus each
field's ``delivered_at`` ISO-8601 timestamp when known (null
for secrets vaulted before timestamps were recorded). Values
are never exposed — use this to verify which fields are
configured and how old each one is. Free. Proof of npub
ownership is required: the list of configured fields is itself
sensitive (reveals which integrations a patron has set up).
- `beesknees_get_patron_onboarding_status`: Report a patron's credential readiness for this operator.

For set-once services (eXcalibur, TheBrain), shows which patron
secrets are configured and which are missing. For dynamic/OAuth2
services (Schwab), reports that no patron credentials are needed.
Free. Proof of npub ownership is required because credential
presence is sensitive information about the patron's setup.
- `beesknees_get_pricing_model`: Get the active pricing model for this operator. Free.

If no model exists, self-initializes a scaffold with all
registered tools at 0 sats.  No economic data from code.
- `beesknees_guide`: What this service is and how to play it, in prose.

The same text the website serves at ``/llms.txt`` — one file, published on
both surfaces, because an agent that arrives through the MCP door should
not have to go and scrape the front door to find out where it is.

It is the front-door answer to a problem the web app cannot solve on its
own: a single-page app hands a fetcher an empty mount div, so everything a
program could learn about this site came from the ``<head>``. The prose
pages are now server-rendered, and this is the same orientation delivered
with provenance instead of by scraping.

Returns the text verbatim. Nothing here is per-patron and nothing is
computed, so two callers get the same bytes.
- `beesknees_join_match`: Buy a drone a seat in the next match.

Seats fill the fullest hive that still has room, so a match reaches its
quorum and starts rather than leaving everyone waiting in five thin hives.
- `beesknees_list_canonical_identities`: Return canonical (tool_id, mcp_name, …) for every tool the wheel exposes.

The authoritative source for any client (Studio, agents, FE)
that needs to know how this MCP identifies its tools.
Reconcile uses this output to UUID-join against the stored
pricing model — no name-based UUID derivation, no guessing.

Includes both ToolIdentity-seeded tools and any UUID recorded by
``@paid_tool`` that is missing from the registry. The latter appear
with ``registered: false`` (and in the top-level ``unregistered``
array) so Reconcile can flag deploy drift instead of silently
reporting clean when a live tool was never seeded (#174).

If the operator renames a function or rebrands a slug, the
mcp_name in this output changes but tool_id stays. That's the
whole point of the canonical-UUID design.

Also diffs the live FastMCP wire surface against the registry.
Tools exposed on the wire but absent from the registry appear in
``unregistered`` so Reconcile can flag deploy drift instead of
silently under-reporting (issue #175).

Free, no side effects.
- `beesknees_list_constraint_types`: List all available constraint types and their parameter schemas.

Returns the type, category, description, and parameter specs for
every constraint that can be used in a pricing pipeline.
Free — no credits required.
- `beesknees_list_coupons`: List every coupon this operator has minted (newest first).

Each row carries the current ``times_redeemed`` counter — the
Studio renders a progress bar from this against ``total_uses``.
RESTRICTED to operator — requires proof.
- `beesknees_list_my_coupons`: List the coupons this patron has redeemed on this operator.

Returns both active and exhausted redemptions with a per-row
``status`` (``active`` / ``window_closed`` / ``patron_limit`` /
``total_limit``).  Free — requires proof of ``npub``.
- `beesknees_list_notarizations`: List recent Bitcoin notarization records.
- `beesknees_match_list`: Matches forming or running, and how many seats are left in each hive.
- `beesknees_match_state`: The live board — every hive, every bee, and when to ask again.

Poll this rather than guessing a cadence: the answer carries `poll_after_ms`,
computed from how hot the match actually is. One algorithm, owned here, so
sixty clients throttle themselves and the server keeps a valve it can turn.
- `beesknees_mint_coupon`: Create a new operator-owned discount coupon.

The coupon owns its binding: ``tool_ids`` names the tools it
discounts, and re-pricing a tool never touches it. A coupon bound
to no tool discounts nothing, however many patrons redeem it.
- `beesknees_my_bee`: Where your bee stands, what it is carrying, and when it may move again.
- `beesknees_notarize_ledger`: Build a Merkle tree of all patron balances and submit the root
to Bitcoin via OpenTimestamps.

Operator-only background task. Bitcoin confirmation takes 1-6 hours.
Free — no credits required.
- `beesknees_oracle_about`: Describe the DPYC ecosystem via the Oracle. Free.
- `beesknees_oracle_get_tax_rate`: Get the current DPYC certification tax rate. Free.
- `beesknees_oracle_how_to_join`: Get DPYC onboarding instructions from the Oracle. Free.
- `beesknees_oracle_lookup_member`: Look up a DPYC community member by npub. Free.
- `beesknees_oracle_network_advisory`: Get active network advisories from the Oracle. Free.
- `beesknees_pay_charity`: Operator: pay everything owed to the charity, in one Lightning payment.

`restricted`, so the runtime requires the caller to be the operator, proven.

The charity share accrues match by match and settles as a batch, which is
the shape this always needed: a single match's share can be smaller than the
fee floor it would cost to route, so paying per match can cost more than it
delivers.

Every unpaid leg is claimed in ONE statement before the sats move, on the
same primary key a single-match `pay_out` uses — so the two cannot pay the
same match twice, and a second press collides on the key rather than at the
node. The accounting stays per match while the payment happens once.

A failure after the claim marks those legs failed rather than deleting them,
so the debt comes back on its own and the attempt stays on the record.
- `beesknees_pay_out`: Operator: send a settled match's charity or winner share over Lightning.

`restricted`, so the runtime requires the caller to be the operator, proven.
This is the only tool here that moves real sats, and the only one whose
effect cannot be undone by writing another row.

The amount is READ from the settlement, never recomputed, so a payment can
never be for a figure the ledger does not already carry. The charity leg
pays the beneficiary the match itself recorded, so a match settled under a
previous charity still pays the charity it promised.

Before anything moves the wallet is asked whether it can cover the payment
plus its routing fee, and the payment is claimed in the database before the
sats leave — so a retry, a double press, or two operators at once collide on
a primary key rather than at the node. Calling it again after a success
reports the existing payment rather than making a second.

Nothing here is automatic. A payment leaves because somebody asked.
- `beesknees_payout`: What you have said should happen to your winnings.

`set` is False for a patron who has never said — which still reads as
`donate`, because that is the default, but lets a screen show the difference
between a choice made and a choice never faced.
- `beesknees_payout_history`: Every payment attempted, and how it went.

Free on purpose. A service that says 80% of every pot goes to a charity
should let anybody check that sats actually left, not merely that a row was
written saying they were owed. Failures are listed too — a payout history
that only shows successes is a claim, not a record.
- `beesknees_publish_nostr_profile`: Publish a CLIENT-SIGNED kind-0 profile to relays for an npub.

The wheel never holds a patron nsec. The frontend signs the kind-0
metadata event with the patron's session key or a NIP-07 extension and
passes the signed event (JSON) here; the wheel verifies the signature
matches the npub, then relays it to public relays. The signature is the
authorization — no proof token, no key custody. Free.
- `beesknees_purchase_credits`: Buy credits via Bitcoin Lightning.

Creates a Lightning invoice. Pay it with any Lightning wallet,
then call check_payment to confirm. Proof of npub ownership is
required so credits land in the correct ledger.

Free — no credits required to call.
- `beesknees_receive_credentials`: Pick up credentials from the Secure Courier.

Completes the CREDENTIAL-DELIVERY flow (the ownership-proof
counterpart is ``receive_npub_proof``).

**Call this only after the user confirms they have replied.**
Deterministic, one-shot retrieval: name the response you want with
``(sender_npub, service, dpop_token)`` and the tool drains ONLY the
rendezvous relay that channel was pinned to. Every popped DM with the
wrong session phrase is deleted and its sender is NACK'd; the first DM
with the matching phrase is accepted (ACK'd) and the scan stops. If
none match, the queue is drained and a ``courier_not_found`` result is
returned. Do NOT poll, loop, or retry.

If a credential_card (ncred1...) is provided, it is redeemed directly
without any relay access (dpop_token not required for that path). On
success, the payment processor client is reinitialized from the new
credentials — no server restart needed.
- `beesknees_receive_npub_proof`: Receive npub ownership confirmation from a patron.

Completes the npub-OWNERSHIP-PROOF flow (the credential-delivery
counterpart is ``receive_credentials``).

**Call this only after the user confirms they have replied.**
Deterministic, one-shot retrieval: name the response with
``(patron_npub, dpop_token)`` — the ``dpop_token`` being the value
returned by ``request_npub_proof``. The tool drains ONLY the pinned
rendezvous relay that challenge was published on, stopping at the DM
whose phrase matches. Mismatched DMs are deleted and NACK'd (without
revealing the expected phrase). If called before the user replies,
their message will never be found. Do NOT poll, loop, or retry.

The signed DM itself proves npub ownership (the patron's nsec
signed it). On success, returns a new ``dpop_token``: an
Operator-signed **proof grant envelope** ``{"grant": …, "nonce": …}``
bound to the patron, this challenge, and the duration the patron
named. The calling application MUST remember that whole string and
pass it as ``dpop_token`` on every subsequent paid tool call. The
grant is self-verifying; nothing about it is stored here. Free.
- `beesknees_redeem_coupon`: Claim a coupon by its name (the code the operator shared).

Looks up the operator's coupon by ``code``, validates the window
and total cap, and records a per-patron redemption row.
Subsequent paid tool calls on this MCP auto-apply the discount
until ``uses_per_patron`` is exhausted.

Free — no credits required.  Requires proof of ``npub``.
Idempotent: redeeming the same code twice returns the existing
redemption.
- `beesknees_report_issue`: File a field report about this service as a GitHub issue on the operator's repo.

Found a tool's metadata or response wrong or confusing? Report it where the tool
lives. The **author of record is your npub** — no npub / no proof, no issue — and it
is stamped into the issue so the report is attributed to you, not the operator. Costs
a small fee (a free write to an issue tracker would be abused). The report is PUBLIC
and goes to the maintainers' normal triage; nothing is verified here.

Returns the filed issue's repo, number, and url. If this operator has not enabled
field reports, returns an "issue reporting not configured" situation and you are not
charged.
- `beesknees_request_adoption`: Ask a chosen Authority to adopt this operator (deferred courtship).

RESTRICTED to the operator — requires proof the caller controls this
operator's npub. Resolves the Authority's MCP endpoint from the
community registry, mints an inline ownership proof with this
operator's nsec, and delivers the request MCP-to-MCP. The Authority
records it as pending; its owner approves on their own time. Poll
``adoption_status`` for progress; the operator flips to ``ready``
once the Authority provisions it.
- `beesknees_request_credential_channel`: Open a Secure Courier channel for credential delivery.

This is the CREDENTIAL-DELIVERY flow — use it to hand over a service
secret (API keys, tokens). To merely prove you control an npub (the
usual answer to a ``proof_required`` error), use ``request_npub_proof``
instead. Note: dynamic/OAuth2 services (e.g. Schwab) need NO couriered
secret — check ``service_status`` first.

Sends a welcome DM with a credential template. The recipient
must read the DM in their Nostr client, fill in the fields,
and reply manually. **This is a human-in-the-loop flow.**

After calling this tool, STOP and tell the user what to do.
Wait for the user to confirm they have replied before calling
``receive_credentials``. Do NOT poll or retry — each
``receive_credentials`` call destructively drains the relay
mailbox.
- `beesknees_request_echo`: Echo what the client sent with this request. Free.

Reports the URL path and query, the headers, the cookies and the MCP
request ``_meta``. Values are SHA-256 fingerprints, so nothing a client
sends is repeated back; equal fingerprints mean equal values. Call it
from two conversations and compare: a value that stays the same within
one and changes between them identifies the conversation.
- `beesknees_request_npub_proof`: Request npub ownership proof from a patron via Nostr DM.

This is the npub-OWNERSHIP-PROOF flow — use it when a call returns
``proof_required``. It proves the caller controls an npub; it does
NOT deliver any service secret. To hand an operator its API keys or
OAuth secrets, use ``request_credential_channel`` instead.

Sends a challenge DM that the patron must sign and reply to
using their Nostr client. **This is a human-in-the-loop flow.**

After calling this tool, STOP and tell the user to check their
Nostr client and reply to the challenge. Wait for the user to
confirm they have replied before calling ``receive_npub_proof``.
Do NOT poll or retry — each ``receive_npub_proof`` call
destructively drains the relay mailbox.

**Returns** a ``dpop_token`` — the one-time challenge nonce shown in
the DM. Pass it to ``receive_npub_proof`` to collect the reply. It
is a matching token, not a credential: on its own it authorizes
nothing.

**Lifecycle:** ``receive_npub_proof`` returns the proof grant, which
expires after the duration the patron named in their reply. When it
expires, call ``request_npub_proof`` again for a fresh challenge,
then wait for the user, then call ``receive_npub_proof``.

Free.
- `beesknees_reset_pricing_model`: Erase all pricing models and restore a viable default.

Deletes every stored model, then self-initializes a fresh one
from the tool registry — all tools at 0 sats with proper UUIDs.
Returns the new model.

RESTRICTED to operator — requires proof (nsec-signed).
- `beesknees_restore_credits`: Credit a patron's ledger from a BTCPay-settled invoice.

**RESTRICTED to the operator** — the operator owns the books and is
the only party who can issue a manual credit grant. Patrons who
believe they paid but never got credits must escalate to the
operator's support, who then invokes this tool on their behalf.

Use cases: cold-start vault races during check_payment, ncred
delivery hiccups, patrons closing Top-Off sheets before settle,
any infrastructure incident that left an invoice settled at BTCPay
but uncredited on the operator's ledger.

Idempotent — if the invoice is already credited (in the patron's
``credited_invoices``), returns success with credits_granted=0.
- `beesknees_restore_neon_schema`: Prepare this operator's database schema again, ignoring the breadcrumb.

Diagnostic / recovery tool for when Neon keeps answering 4xx and the
operator suspects a table or grant is missing. Every statement is
idempotent, so a clean re-run is harmless; the breadcrumb is rewritten
at the end. Returns one step per concern, with Neon's own error text
inline for any that failed.

RESTRICTED to operator — requires proof (nsec-signed).
- `beesknees_seal`: Bring down an open tunnel cell, so the bees behind you must cut it again.

Costs one move and a fare, and sets a rival back several — a bee has a body,
so a bee stuck behind a seal is also a wall for everyone behind it.
- `beesknees_service_status`: Check the health and configuration of this service. Free.
- `beesknees_session_status`: Check operator readiness. Returns the operator lifecycle
state and clear guidance on what to do next. Free.

Lifecycle states:
- ready: Vault AND pricing model verified on this call. Proceed with
  tool calls — this is the answer the moment the vault is up.
- warming_up: Persistence could not be reached on this call (a
  transient failure, seen, not assumed). Retry; the next call
  completes the bootstrap. Never reported on a clock.
- misconfigured: Persistence rejected a query with a permanent SQL
  error (permission denied, missing relation). Paid tools will fail
  until the operator repairs the database — retrying does not help.
- quota_exceeded: The persistence provider (Neon) answered HTTP 402 —
  the operator's database has exhausted its compute/storage quota, so
  the books are locked for billing. Paid tools fail; retrying does NOT
  help. The operator's Authority must restore capacity (upgrade the
  plan or wait for the quota reset). Free tools remain available.
- not_registered: Operator has no Authority relationship yet. Call register_operator first.
- no_identity: Operator nsec is not configured. Deployment issue.
- `beesknees_set_charity`: Operator: name the beneficiary, its website and its Lightning address.

`restricted`, so the runtime requires the caller to be the operator, proven.

It was a constant in the source, which made changing who the money goes to a
deployment. A charity can be replaced, renamed, or rotate its wallet, and
none of that should need anybody to touch code.

Changing this never rewrites history: every settlement records the
beneficiary it actually paid at the time, so a player can always check where
the money went rather than where it goes now.
- `beesknees_set_payout`: Say now what should happen if you win.

Decided BEFORE the round, deliberately. Asking in the moment is asking
somebody to make a decision about money with a trophy on the screen, and a
winner who has never thought about it should still end the round with their
share settled rather than owed.

Donating is the default. Keeping it needs somewhere to send it, so a patron
who turns donation off without giving an address is told so rather than
quietly left with an unclaimable prize.
- `beesknees_set_pricing_model`: Set the active pricing model. RESTRICTED to operator.

Requires a valid proof (Schnorr-signed kind-27235 event)
proving the caller holds the operator's nsec.
- `beesknees_settlement_history`: What every settled match paid, and to whom.

Free on purpose. A claim about where the money went that costs money to
check is not a claim anybody should believe.

Sorted and paged by the SERVER. This is the one table that grows without
bound — a row per settled match, kept when everything else about the match
is purged — so sending all of it and cutting it up in the browser has an end
date. `total` comes back with the page so a reader knows how much there is.
- `beesknees_tick`: Operator: open, close and settle matches.

`restricted`, so the runtime requires the caller to be the operator, proven.
This is the cron entry point; `check_now` is the same work without authority.
- `beesknees_treasury`: Operator: what the wallet can send, and what is owed out of it.

`restricted`, so the runtime requires the caller to be the operator, proven.

`sendable_sats` is the local end of the node's channels — the only balance a
Lightning payment can draw on. `owed_sats` is what this service's own
settlements say is still to go out, computed from its own tables.

`node_reachable: false` means the balance could not be asked for at all — an
unreachable node, or an API key without `canuselightningnode` — and
`pay_out` refuses on it. An unknown balance is not an optimistic one.

`covers_everything_owed` is reported, not enforced: an operator should see
that they owe more than they hold, but refusing to pay one charity because a
second is also owed helps neither of them.
- `beesknees_update_coupon`: Patch a coupon's editable fields.

Pass only the fields you want to change.  To set a cap to
unlimited (NULL in the schema), pass ``clear_uses_per_patron=true``
or ``clear_total_uses=true``.  Renaming the code is allowed —
existing patron redemption rows survive (they key on coupon id).
``tool_ids`` replaces the coupon's binding — tool ids or MCP tool
names, ``["*"]`` for every paid tool, ``[]`` to unbind it.

RESTRICTED to operator — requires proof.
- `beesknees_update_operator_credential`: Add or update a single operator secret field.

Merges into the operator's stored credentials without touching the
others — the field-level counterpart to re-delivering the whole
bundle over Secure Courier. Use it to rotate one secret (a reissued
``btcpay_api_key``, say) without restating the six you did not
change, where any field omitted from a courier reply is destroyed.

The value is never echoed back. RESTRICTED to the operator —
requires the operator's proof (a kind-27235 event or a proof grant);
patron proofs are rejected.
- `beesknees_update_patron_credential`: Add or update a single patron credential field.

Merges into existing stored credentials without affecting
other fields. Useful for setting an account identifier
after OAuth, changing a default brain, etc. Free. Proof of
npub ownership is required — this is a write to the patron's
sensitive credential vault.