Skip to content

Docs/agent prices from server - #404

Merged
Rassl merged 2 commits into
mainfrom
docs/agent-prices-from-server
Sep 10, 2026
Merged

Rassl merged 2 commits into
mainfrom
docs/agent-prices-from-server

Conversation

@Rassl

@Rassl Rassl commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

No description provided.

The per-unlock payout is a boltwall code constant rather than a price
row, but agents were still quoting it as a fixed figure. State it as a
flat server-set amount and tell agents to read it from the payout rows'
`amount` in /api/transactions, matching the no-hardcoded-prices rule
applied to route fees in the previous commit. BOLT11 unit conversions
and the illustrative transactions example are unchanged.

Claude-Session: https://claude.ai/code/session_01VNeAPuAPwtkDW1ctC3ZkAX
Boltwall has had a withdraw route (L402 header + BOLT11 payment_request
body, server-side minimum, debit-then-pay with refund on failure) but
neither agent file mentioned it, so agents assumed earnings were trapped
on the token.

- llms.txt: Payment-table row with the full error-code list, a worked
  "cash out my sats" example, and `withdrawal` added to the debit actions.
- agents.txt: cheatsheet row and a "Withdrawing" section under Earnings,
  including how to ask the human for a receiving invoice.

The minimum is described as server-set and read from the BELOW_MINIMUM
response, per the no-hardcoded-amounts rule.

Claude-Session: https://claude.ai/code/session_01VNeAPuAPwtkDW1ctC3ZkAX
@Rassl
Rassl merged commit 3acbcb1 into main Sep 10, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant