@rozoai/checkout 0.1.10 → 0.1.11

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -2,11 +2,34 @@
2
2
 
3
3
  **English** | [简体中文](docs/README.zh.md) | [日本語](docs/README.ja.md) | [Español](docs/README.es.md)
4
4
 
5
- Pay an **OpenRouter Coinbase Payment Link** with a coin that link cannot take
6
- directly — BTC over Lightning, or USDT/USDC on Solana, BNB Chain, Ethereum,
7
- Polygon, Base or Stellar. A Coinbase Payment Link only accepts USDC on Base;
8
- this routes the coin you actually hold through a bridge, and a funder wallet
9
- settles the invoice for you. No account, no API key, no browser.
5
+ ### When your agent needs to pay OpenRouter (or any Coinbase invoice) with the crypto you already hold
6
+
7
+ OpenRouter crypto top-ups and other Coinbase-hosted invoices settle in USDC on
8
+ Base. This skill pays them from whatever you hold instead, and it does three
9
+ things the official path cannot:
10
+
11
+ - **Pay from the chain you are already on.** USDT or USDC on Solana, BNB Chain,
12
+ Ethereum or Polygon, USDC on Base or Stellar, or BTC over Lightning. Coinbase's
13
+ own direct pay takes USDC on Base.
14
+ - **No Coinbase account.** Pay the deposit address from any wallet or straight
15
+ from an exchange withdrawal. No sign-up, no API key, no browser.
16
+ - **Scriptable.** OpenRouter's crypto credits API (`POST /api/v1/credits/coinbase`)
17
+ now returns `410 Gone`, so top-ups can no longer be automated there. Once you
18
+ have the payment link, paying it is one command an agent or a cron job can
19
+ run: without a terminal it stops for confirmation, so an unattended caller
20
+ reviews the quote and then passes `--yes`.
21
+
22
+ Merchants we have been paid through so far: **OpenRouter, Venice.ai, Porkbun
23
+ and Alchemy**. Any `payments.coinbase.com` link is quoted the same way.
24
+
25
+ Before you pay, know two things:
26
+
27
+ - **The fee is in the live quote.** You pay the full invoice, no discount and no
28
+ markup on it; the bridge and network fee is added to the deposit amount, which
29
+ is shown in the order summary before the deposit address is released. Send
30
+ exactly that amount, nothing more is charged.
31
+ - **Crypto payments to OpenRouter are never refundable.** That is OpenRouter's
32
+ policy, not ours; check the credit amount before you send.
10
33
 
11
34
  ```bash
12
35
  npx @rozoai/checkout pay <coinbase-link>
@@ -62,6 +85,21 @@ already hold and pay from wherever it already lives.
62
85
 
63
86
  ## Use it from your agent
64
87
 
88
+ Install it as a skill, or just run the CLI:
89
+
90
+ ```text
91
+ # Claude Code
92
+ /plugin marketplace add RozoAI/rozo-checkout-skill
93
+ /plugin install rozo-checkout@rozo
94
+
95
+ # OpenClaw / ClawHub
96
+ clawhub install rozo-checkout
97
+
98
+ # Any agent that can run a shell: review the quote, then pay unattended
99
+ npx @rozoai/checkout quote <coinbase-link>
100
+ npx @rozoai/checkout pay <coinbase-link> --with usdt-solana --yes
101
+ ```
102
+
65
103
  The payload is the same everywhere: the one-liner above, or point the agent at
66
104
  [llms.txt](llms.txt). Agents and scripts should always pass `--with` — the
67
105
  picker only appears on a terminal, and there is deliberately no default coin. **Paying from your own wallet never needs a key.** Only
@@ -274,7 +312,7 @@ Stellar and Lightning are Mode A only.
274
312
  <summary><b>Terminal — no agent at all</b> — run the scripts step by step</summary>
275
313
 
276
314
  Drive each step yourself. The bundles are self-contained; nothing to install
277
- beyond Node 18+.
315
+ beyond Node 20.18+.
278
316
 
279
317
  ```bash
280
318
  git clone https://github.com/RozoAI/rozo-checkout-skill && cd rozo-checkout-skill
@@ -348,6 +386,12 @@ The full list of what this refuses to do, and why, is in
348
386
 
349
387
  ## Changelog
350
388
 
389
+ - **0.1.11**: each order now carries `attribution.client`
390
+ (`rozo-checkout-skill/<version>`) so skill-created orders can be told apart
391
+ from the web checkout. Installable as a Claude Code plugin
392
+ (`/plugin marketplace add RozoAI/rozo-checkout-skill`). README and skill
393
+ description rewritten around paying Coinbase invoices from the crypto you
394
+ already hold.
351
395
  - **0.1.3** — fixes found by the first real payment. The built bundles no
352
396
  longer crash with `__filename is not defined` on Node 22+ (the esbuild banner
353
397
  now shims `__filename`/`__dirname` as well as `require`, and every bundle is
@@ -372,3 +416,7 @@ The full list of what this refuses to do, and why, is in
372
416
  ## License
373
417
 
374
418
  MIT.
419
+
420
+ ## Secret scanning
421
+
422
+ Enable the local gitleaks pre-commit hook once per clone: `brew install gitleaks pre-commit && pre-commit install` (config in `.pre-commit-config.yaml`). CI also runs a report-only scan in `.github/workflows/secret-scan.yml`.
@@ -0,0 +1,77 @@
1
+ # Review history
2
+
3
+ [← back to the README](../README.md) · [Safety design](safety.md)
4
+
5
+ This tool moves other people's money. It was reviewed adversarially before it
6
+ was written, again after it was written, and again after the first real payment.
7
+ This page is the record of that.
8
+
9
+ ## Design review — 3 rounds, before any code existed
10
+
11
+ The design was written as a plan document and reviewed by an independent model
12
+ with a standing instruction to hunt for anything that could lose funds. No code
13
+ was written until the plan passed with no P0 findings.
14
+
15
+ | Round | Verdict |
16
+ |---|---|
17
+ | 1 | 6 P0, 7 P1, 2 P2 — plan revised |
18
+ | 2 | still had P0s: several round-1 fixes were incomplete, plus one new P0 — plan revised again |
19
+ | 3 | no P0 — implementation began |
20
+
21
+ The P0s were about the plan being wrong regarding the payment rails, not about
22
+ style. Among them: the reuse rule was mis-stated (an existing order is reused
23
+ whenever it is merely unexpired, not only when it is unpaid); the binding
24
+ confirmation was placed before the deposit details existed, so it could not
25
+ bind them; and the payment link could be consumed by another payer between the
26
+ quote and the signature, which needed a re-check immediately before paying.
27
+
28
+ ## Code review — 2 rounds, after implementation
29
+
30
+ | Round | Verdict |
31
+ |---|---|
32
+ | 1 | 8 P0, 10 P1, 5 P2 |
33
+ | 2 | 20 of 23 resolved; 3 residual findings, then fixed |
34
+
35
+ The round-1 P0s were the interesting ones, and each is now a real code path
36
+ with its own error code and tests:
37
+
38
+ - the confirmation gate and the `--send` opt-in were documented but not
39
+ actually enforced
40
+ - the send-once claim was a check-then-act race that two concurrent processes
41
+ could both pass
42
+ - an unreadable `amountReceived` was treated as "no money received" rather than
43
+ as money
44
+ - the post-create comparison ignored security-critical fields when they were
45
+ simply absent
46
+ - payability was not re-proved immediately before signing, and incomplete
47
+ upstream state read as payable
48
+ - deposit instructions were not validated for completeness before being shown
49
+ - provider errors could leak credential-bearing URLs
50
+ - the tracked-secret check failed open when it could not consult git
51
+
52
+ ## First real payment
53
+
54
+ A live payment then settled in about a minute — and surfaced four more defects,
55
+ all fixed in 0.1.3:
56
+
57
+ - the built bundles crashed on newer Node because the bundler's CommonJS shim
58
+ was incomplete; it had never been caught because only `--help` was ever run
59
+ against a built bundle. The test suite now executes every bundle.
60
+ - the Stellar memo type was not stated anywhere, and sending that memo with the
61
+ wrong type loses the payment. It is `MEMO_TEXT`, and the deposit block now
62
+ says so.
63
+ - reusing an existing unpaid order, and asking for a coin that differs from it,
64
+ both read as errors rather than as the ordinary situations they are
65
+ - nothing showed how long an order had left, and a real payment nearly missed
66
+ its window
67
+
68
+ ## What this means for a reader
69
+
70
+ Every finding above is closed, and the behaviours they produced are covered by
71
+ the test suite, which runs entirely offline against recorded fixtures. The full
72
+ list of what this tool refuses to do, and why, is in
73
+ [docs/safety.md](safety.md).
74
+
75
+ The detailed review transcripts are kept internally; they quote source from
76
+ private repositories and so are not published here. The findings themselves are
77
+ summarised above in full — nothing material is omitted.
package/llms.txt CHANGED
@@ -1,8 +1,10 @@
1
1
  # rozo-checkout
2
2
 
3
- > Pay an OpenRouter Coinbase Payment Link (payments.coinbase.com/payment-links/pl_* or
4
- > /payment-sessions/paymentSession_*) with BTC over Lightning, or USDT/USDC on Solana,
5
- > BNB Chain, Ethereum, Polygon, Base, or Stellar. Public HTTP endpoints, no API key.
3
+ > When your agent needs to pay OpenRouter (or any Coinbase invoice) with the crypto you
4
+ > already hold. Pays a Coinbase Payment Link (payments.coinbase.com/payment-links/pl_* or
5
+ > /payment-sessions/paymentSession_*) with BTC over Lightning, USDT/USDC on Solana,
6
+ > BNB Chain, Ethereum or Polygon, or USDC on Base or Stellar. No Coinbase account, public HTTP
7
+ > endpoints, no API key. Crypto payments to OpenRouter are never refundable.
6
8
  > The payer funds a one-time deposit address; a bridge and a funder wallet settle the
7
9
  > Coinbase link automatically. No discount: you pay the invoice amount, plus the
8
10
  > deposit normally carries a small bridge/source-chain fee on top.
package/package.json CHANGED
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "name": "@rozoai/checkout",
3
- "version": "0.1.10",
3
+ "version": "0.1.11",
4
4
  "type": "module",
5
- "description": "Pay an OpenRouter Coinbase Payment Link with BTC Lightning, or USDT/USDC on Solana, BNB Chain, Ethereum, Polygon, Base or Stellar.",
5
+ "description": "Pay OpenRouter, or any Coinbase invoice, with the crypto you already hold: USDT/USDC on Solana, BNB Chain, Ethereum or Polygon, USDC on Base or Stellar, or BTC over Lightning. No Coinbase account.",
6
6
  "license": "MIT",
7
7
  "author": "Rozo AI",
8
8
  "homepage": "https://github.com/RozoAI/rozo-checkout-skill#readme",
@@ -15,13 +15,29 @@
15
15
  },
16
16
  "keywords": [
17
17
  "openrouter",
18
+ "openrouter-credits",
18
19
  "coinbase",
19
- "x402",
20
- "lightning",
21
- "solana",
22
- "usdt",
20
+ "coinbase-payment-link",
23
21
  "usdc",
24
- "crypto-payments"
22
+ "usdt",
23
+ "solana",
24
+ "bnb-chain",
25
+ "ethereum",
26
+ "polygon",
27
+ "base",
28
+ "stellar",
29
+ "lightning",
30
+ "bitcoin",
31
+ "crypto-payments",
32
+ "agent",
33
+ "ai-agent",
34
+ "agent-skill",
35
+ "claude-skill",
36
+ "claude-code",
37
+ "payments",
38
+ "cli",
39
+ "mcp-free",
40
+ "x402"
25
41
  ],
26
42
  "bin": {
27
43
  "rozo-checkout": "scripts/dist/cli.js"
@@ -35,7 +51,7 @@
35
51
  "LICENSE"
36
52
  ],
37
53
  "engines": {
38
- "node": ">=18"
54
+ "node": ">=20.18.0"
39
55
  },
40
56
  "publishConfig": {
41
57
  "access": "public"
@@ -47,9 +63,13 @@
47
63
  "prepack": "npm run build"
48
64
  },
49
65
  "devDependencies": {
50
- "@solana/spl-token": "^0.4.9",
51
66
  "@solana/web3.js": "^1.95.0",
52
67
  "esbuild": "^0.28.2",
53
68
  "viem": "^2.21.0"
69
+ },
70
+ "overrides": {
71
+ "jayson": {
72
+ "uuid": "^11.1.1"
73
+ }
54
74
  }
55
75
  }