feat: fetch --dry-run previews the price without paying

[reneaaron]

What

Adds fetch --dry-run: sends the request unpaid and reports the 402 challenge instead of settling it. Needs no wallet.

$ alby fetch --dry-run "https://www.l402apps.com/api/apis"
{
  "url": "https://www.l402apps.com/api/apis",
  "status": 402,
  "payment_required": true,
  "amount_in_sats": 10,
  "description": "L402 Apps — Get APIs directory"
}

• Price in sats is extracted from wherever the protocol puts the lightning invoice: WWW-Authenticate (L402 ... invoice= / MPP Payment ... invoice=) or a lightning-native x402's base64 Payment-Required header.
• When no lightning invoice is offered (e.g. a USDC-only x402 hit directly instead of through the l402.space bridge), the raw challenge is surfaced so the terms are still visible.
• A free endpoint reports payment_required: false.
• Payment flags (--max-amount/--currency/--unit/--network/--credentials) are rejected alongside --dry-run since a dry run never pays.

Why

From the review discussion on getAlby/payments-skill#28: prices listed on 402index.io can be missing, stale, or dynamic — the 402 challenge is the authoritative price at request time, but checking it previously meant hand-crafting a curl. Use case: comparing prices between two providers before paying.

Per that discussion this is deliberately not documented in the skill for now — the --max-amount default already guards automated flows.

Test

• yarn test green (111 pass, 2 skipped); 5 new unit tests cover L402, MPP, base64-x402 extraction, no-lightning-challenge fallback, and free endpoints (using a real BOLT-11 so decoding is exercised).
• Verified live against all three challenge shapes without paying: native L402 (10 sats), bridged x402 via l402.space (19 sats), lightning-native x402 (15 sats).

[coderabbitai]

Warning

Review limit reached

@rolznz, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 58 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a4529c19-405e-49e2-a8e3-85d0a343b50d

📥 Commits

Reviewing files that changed from the base of the PR and between 03d89db and 1750150.

📒 Files selected for processing (3)

• src/commands/fetch.ts
• src/test/fetch-dry-run.test.ts
• src/tools/lightning/fetch.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/fetch-dry-run

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}