@aifinpay/skill 2.10.1 → 2.10.2

package/.claude-plugin/marketplace.json

@@ -12,7 +12,7 @@
       "name": "aifinpay",
       "source": "./",
       "description": "Payment rail skills for paying agents and API merchants.",
-      "version": "2.10.1",
+      "version": "2.10.2",
       "author": {
         "name": "AiFinPay Support",
         "email": "contact@aifinpay.io"

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "aifinpay",
   "description": "Payment rail for AI agents: pay for x402 APIs or charge agents for yours.",
-  "version": "2.10.1",
+  "version": "2.10.2",
   "author": { "name": "AiFinPay Support" },
   "homepage": "https://aifinpay.io",
   "repository": "https://github.com/AiFinPay/skill",

package/CHANGELOG.md

@@ -1,3 +1,21 @@
+## 2.10.2 — funding at today's rate, working limits in the dashboard
+
+- Payer guide: step 4 no longer names a POL amount or a POL/USD rate. The
+  amount to fund is what `payment_setup_status` prices in `funding` (MCP
+  2.11.3): the smallest batch at today's rate plus the gas cap. When no rate
+  can be read, the agent asks the owner for "the batch price in POL at
+  today's rate plus the gas cap" and names no number. On 2026-10-19 one
+  `$0.10` batch was 1.08 POL while the guide still said 0.5.
+- Payer guide: the env USD values are a ceiling the owner sets once (the
+  example block shows `5` and `20` and says they are not a budget); the
+  working limits — per-payment cap, daily cap, pause, allowed sites — are the
+  dashboard Controls once the agent is claimed with `agent_claim_self`,
+  enforced by the backend on every quote and payment. The "link it to the
+  owner's dashboard" section says so instead of telling the agent to keep the
+  limits in its configuration.
+- Release target MCP 2.11.3 / Node SDK 2.9.0; published baseline checked
+  2026-10-19 (MCP 2.11.2, Node SDK 2.8.0).
+
 ## 2.10.1 — restart after env changes, AIFINPAY_HOME on init
 
 - Payer guide: owner limits are read when the MCP server starts, so after the

package/README.md

@@ -9,8 +9,10 @@ any client that loads `SKILL.md`).
 | `aifinpay` | Paying — agent buys x402-gated API access | `agent/skills/aifinpay/SKILL.md` |
 | `aifinpay-merchant` | Earning — merchant charges agents per request | `agent/skills/aifinpay-merchant/SKILL.md` |
 
-Version **2.10.1** describes the first-payment path for a fresh agent.
-Release target: MCP **2.11.1**, Node SDK **2.8.0**, Python **2.7.0**.
+Version **2.10.2** describes the first-payment path for a fresh agent, with
+the funding amount priced at today's rate and the owner's working limits in
+the dashboard.
+Release target: MCP **2.11.3**, Node SDK **2.9.0**, Python **2.7.0**.
 Reporting release target: Node gate **0.4.0**, Python gate **0.1.3**.
 The merchant guide describes explicit opt-in observations, consent, queue loss
 and producer health using the SDK's reporting v2 contract. It adds no MCP tools

package/agent/skills/aifinpay/SKILL.md

@@ -6,7 +6,7 @@ description: Pay for x402-gated APIs and sites as an agent (AIFP-1 on an owner-s
   wallet, payment history, prepaid quotas and Agent Passport records through
   the AiFinPay MCP server or SDK.
 license: MIT
-version: 2.10.1
+version: 2.10.2
 author: AiFinPay Support
 metadata:
   hermes:
@@ -61,17 +61,17 @@ your language. There is no "install together" scenario.
 
 ## Version and release status
 
-Release target: MCP **2.11.1**, Node SDK **2.8.0**, Python **2.7.0**.
+Release target: MCP **2.11.3**, Node SDK **2.9.0**, Python **2.7.0**.
 This skill describes that coordinated package cohort. Check the installed
 versions before using its additional-network instructions; a release target
 does not establish npm/PyPI publication or production network activation.
-Published baseline checked 2026-10-19: MCP **2.11.0**, Node SDK **2.8.0**.
+Published baseline checked 2026-10-19: MCP **2.11.2**, Node SDK **2.8.0**.
 `payable_fetch` has shipped since MCP 2.2.0, and Base since MCP 2.5.0.
 Published packages remain usable within their documented capabilities.
 
 | Surface | Can it pay? |
 |---|---|
-| MCP `@aifinpay/mcp` 2.11.x | `payable_fetch`, only with a persistent wallet and every owner limit set; it is always listed and, until then, answers with the setup checklist instead of signing. `payment_setup_status` is the read-only checklist with one `next_step`. Polygon is the default; other networks require explicit `AIFINPAY_PAY_CHAIN`. The merchant and backend must authorize and serve that network. `scope: "merchant"` buys a site-wide batch. |
+| MCP `@aifinpay/mcp` 2.11.x | `payable_fetch`, only with a persistent wallet and every owner limit set; it is always listed and, until then, answers with the setup checklist instead of signing. `payment_setup_status` is the read-only checklist with one `next_step` and, from 2.11.3, `funding`: the amount to fund at today's rate. Polygon is the default; other networks require explicit `AIFINPAY_PAY_CHAIN`. The merchant and backend must authorize and serve that network. `scope: "merchant"` buys a site-wide batch. |
 | Node `@aifinpay/agent` 2.8.x | `fetchPaid` with a v14 journal, gas cap and owner budgets. Select another network with `v14.chain`; select a pinned stablecoin with `v14.asset`. Native payments require an independent native/USD rate. |
 | Python `aifinpay-agent` 2.7.x | `agent.fetch_paid(url, allowed_origins=…, max_amount_usd=…, daily_amount_usd=…)`; use explicit `chain` and the chain's native gas cap for another network, or a pinned stablecoin `asset`. `agent.recover_paid(journal_path)` recovers the original transaction. |
 
@@ -192,8 +192,9 @@ step — no key handling of your own, no funding of an ephemeral address.
    example `$0.10` for 200 standard requests).
 2. **Check the setup.** Call `payment_setup_status`. It returns the wallet
    (`persistent` or ephemeral), `payments_enabled`, which owner limits are
-   set, the balance when the RPC answers, `ready`, and `next_step` — the one
-   thing still missing. Follow `next_step`; do not skip ahead.
+   set, the balance when the RPC answers, `funding` (what a persistent wallet
+   needs, priced now), `ready`, and `next_step` — the one thing still
+   missing. Follow `next_step`; do not skip ahead.
 3. **Persistent wallet.** If `wallet.persistent` is false, run the exact
    command in `next_step` (it is `npx @aifinpay/mcp init`, prefixed with
    `AIFINPAY_HOME=…` when the server uses its own wallet directory — keep
@@ -208,11 +209,17 @@ step — no key handling of your own, no funding of an ephemeral address.
    its `next_step` and start a new wallet directory. Never fund an ephemeral
    address.
 4. **Fund and enable.** Tell the owner `addresses.evm` and the amount: the
-   batch price in the pay chain's native currency plus the gas cap (on
-   Polygon, about `0.5 POL` covers one `$0.10` batch plus a `0.3 POL` cap).
-   When the owner confirms funding, they add the payment settings from
-   "Paying with payable_fetch" below — with their real origin and limits —
-   to the same `env`. **Limits are read only when the server starts**:
+   batch price in the pay chain's native currency at today's rate plus the
+   gas cap. Take it from `payment_setup_status` — its `funding` field prices
+   the smallest batch now and adds the owner's gas cap into `amount`. The
+   rate moves (on 2026-10-19 one `$0.10` batch was 1.08 POL), so never
+   quote a remembered number; if `funding` has a `rate_error` and no
+   `amount`, ask the owner to fund "the batch price in POL at today's rate
+   plus the gas cap" and name no number. When the owner confirms funding,
+   they add the payment settings from "Paying with payable_fetch" below —
+   with their real origin, and USD values that are a ceiling they will not
+   need to revisit (the working limits are set in the dashboard, see "After
+   creating a wallet") — to the same `env`. **Limits are read only when the server starts**:
    `agent_reload` re-reads the keystore and nothing else, so after the env
    changes the client has to restart the `aifinpay` MCP server (restart the
    client, or disable and re-enable the server in it). Until that restart
@@ -271,21 +278,28 @@ default `scope`.
 
 ## Paying with payable_fetch
 
-The owner configures these MCP environment values (example limits only):
+The owner configures these MCP environment values once (example values; the
+USD ones are a ceiling, not a budget):
 
 ```json
 {
   "AIFINPAY_PAYMENTS_ENABLED": "1",
   "AIFINPAY_GATEWAY_ORIGINS": "https://merchant.example",
   "AIFINPAY_GATEWAY_PATH_MODE": "direct",
-  "AIFINPAY_MAX_USD": "0.15",
-  "AIFINPAY_DAILY_USD": "1.00",
+  "AIFINPAY_MAX_USD": "5",
+  "AIFINPAY_DAILY_USD": "20",
   "AIFINPAY_MAX_GAS_POL": "0.3"
 }
 ```
 
-The smallest batch is **$0.10 plus gas** on **Polygon**; keep `AIFINPAY_MAX_USD`
-a little above the batch you expect to buy. The gas cap has to cover the
+`AIFINPAY_MAX_USD` and `AIFINPAY_DAILY_USD` are the ceiling the SDK requires
+before it signs with the owner's key: set once, high enough not to need
+revisiting, and left alone. The day-to-day limits — per-payment cap, daily
+cap, pause, allowed sites — are the dashboard **Controls** once the agent is
+claimed (see "After creating a wallet" below); the backend enforces them on
+every quote and payment, with no env change and no server restart. A payment
+has to pass both. The smallest batch is **$0.10 plus gas** on **Polygon**;
+`AIFINPAY_MAX_USD` only has to be at or above the batch. The gas cap has to cover the
 worst-case fee: at ~280 gwei that is about 0.10 POL for a POL payment and
 0.21 POL for USDC, and a lower cap refuses before anything is signed. The fee
 charged is usually a fraction of that, but the wallet must hold the batch plus
@@ -298,8 +312,9 @@ wallet or create one with `npx @aifinpay/mcp init` (on a terminal it asks for
 a passphrase; without one it generates it and prints the `env` block to put
 into the MCP client config — the server's env needs that same
 `AIFINPAY_WALLET_PASSPHRASE`, or every start mints a new ephemeral wallet);
-fund its EVM address on Polygon with POL, or with USDC plus some POL. Funding a wallet does not establish
-unlimited spend authority. Use the owner's actual approved limits and origins,
+fund its EVM address on Polygon with POL, or with USDC plus some POL, in the
+amount `payment_setup_status` prices. Funding a wallet does not establish
+unlimited spend authority. Use the owner's actual approved origins and ceiling,
 then call `payable_fetch({"url":"https://merchant.example/api/data"})`.
 
 For another network, the owner sets `AIFINPAY_PAY_CHAIN` to an exact name in
@@ -370,10 +385,16 @@ at https://dash.aifinpay.io → My Agents:
   `agent.sign_dashboard_claim(challenge)` (Python). These sign only
   `AiFinPay-claim:polygon:<own address>:<nonce>`.
 
-Keep local owner spending limits in the agent's configuration (`AIFINPAY_MAX_USD`,
-`AIFINPAY_DAILY_USD`). Claimed-wallet controls in the dashboard are additional
-backend restrictions on quotes and gateway access; they do not replace local
-limits or control transactions sent directly outside AiFinPay.
+Once the agent is claimed, the dashboard is where the owner manages its
+working limits: **Controls** on the agent's page sets the per-payment cap, the
+daily cap, pause and the allowed sites, and the backend enforces that policy
+on every `/v1/quote` and `/v1/pay` for the claimed agent — no env change, no
+server restart. The env values (`AIFINPAY_MAX_USD`, `AIFINPAY_DAILY_USD`, the
+gas cap, the origins) stay as the ceiling the SDK requires before it signs;
+they do not replace the dashboard, and the dashboard does not replace them —
+a payment has to pass both. Dashboard controls do not reach transactions sent
+directly outside AiFinPay. After `agent_claim_self`, point the owner at
+Controls rather than at the config file when they want to change a limit.
 
 Discover routes on the exact requested origin: `/.well-known/x402.json` and any
 API catalog linked by that site. A dev hostname does not imply testnet. If a

package/agent/skills/aifinpay-merchant/SKILL.md

@@ -4,7 +4,7 @@ description: Configure an HTTP 402 gate for agent access to a website or API,
   with owner-selected routes, verified payouts and explicitly accepted EVM
   networks. Agents settle from their own wallets; the merchant receives 99%.
 license: MIT
-version: 2.10.1
+version: 2.10.2
 author: AiFinPay Support
 metadata:
   hermes:
@@ -155,7 +155,7 @@ Gate 0.3.3 source adds `instructions_url` (payer skill),
 links to maintained public instructions, not stored wallet or receipt data.
 Existing sites must upgrade/redeploy gate to emit those new fields.
 
-Release target: MCP **2.11.1**, Node SDK **2.8.0**, Python **2.7.0**.
+Release target: MCP **2.11.3**, Node SDK **2.9.0**, Python **2.7.0**.
 This coordinated target does not establish publication or reporting rollout.
 Those clients
 reuse the signed v1.4 payment kernel for nine EVM network descriptors; network

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aifinpay/skill",
-  "version": "2.10.1",
+  "version": "2.10.2",
   "description": "AiFinPay agent skills: pay for x402-gated APIs as an agent (aifinpay) and charge agents for your API as a merchant (aifinpay-merchant).",
   "type": "module",
   "files": [