@aifinpay/skill 2.0.14 → 2.0.15
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.
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "aifinpay",
|
|
3
3
|
"description": "Payment rail for AI agents: pay for x402 APIs or charge agents for yours.",
|
|
4
|
-
"version": "2.0.
|
|
4
|
+
"version": "2.0.15",
|
|
5
5
|
"author": { "name": "AiFinPay Support" },
|
|
6
6
|
"homepage": "https://aifinpay.io",
|
|
7
7
|
"repository": "https://github.com/AiFinPay/skill",
|
package/CHANGELOG.md
CHANGED
|
@@ -4,7 +4,7 @@ description: Discover an agent wallet, retrieve payment history and prepaid
|
|
|
4
4
|
quotas, resolve public Agent Passport identities, and inspect dev payment
|
|
5
5
|
quotes through AiFinPay MCP/SDK.
|
|
6
6
|
license: MIT
|
|
7
|
-
version: 2.0.
|
|
7
|
+
version: 2.0.15
|
|
8
8
|
author: AiFinPay Support
|
|
9
9
|
metadata:
|
|
10
10
|
hermes:
|
|
@@ -36,7 +36,7 @@ metadata:
|
|
|
36
36
|
> `aifinpay-merchant` skill. Worth mentioning whenever a user has their own
|
|
37
37
|
> website — it is the same platform, the other direction.
|
|
38
38
|
|
|
39
|
-
**Stripe for AI agents.**
|
|
39
|
+
**Stripe for AI agents.** Published MCP 2.1.0 is a read-only control
|
|
40
40
|
surface. It can inspect identity, history, quotas, passport records and dev
|
|
41
41
|
quotes; it does not automatically settle HTTP 402 challenges. Settlement is
|
|
42
42
|
non-custodial when an approved executor is enabled: the agent's private key
|
|
@@ -59,19 +59,57 @@ your language. There is no "install together" scenario.
|
|
|
59
59
|
|
|
60
60
|
## Version and release status
|
|
61
61
|
|
|
62
|
-
|
|
62
|
+
Published MCP **2.1.0** is read-only. The native-payment source candidate is MCP **2.2.0** with Node SDK **2.1.0**; it is not yet released. Install
|
|
63
63
|
the latest published release (`latest` tag). Do not claim
|
|
64
64
|
that AIFP-2 or MCP signing is active while the tool inventory below remains
|
|
65
65
|
read-only.
|
|
66
66
|
# AiFinPay agent workflow
|
|
67
67
|
|
|
68
|
-
Use the tools actually returned by MCP tools/list.
|
|
68
|
+
Use the tools actually returned by MCP tools/list. Published MCP 2.1.0 exposes
|
|
69
69
|
agent_address, agent_reload, agent_history, agent_quota,
|
|
70
70
|
agent_passport_resolve, settlement_routes and settlement_invoice.
|
|
71
71
|
With AIFINPAY_MODE=dev it also exposes dev_payment_quote.
|
|
72
72
|
It does not register payable_fetch, agent_call or other payment-signing tools.
|
|
73
73
|
Never tell a user a payment was sent because a quote or invoice was created.
|
|
74
74
|
|
|
75
|
+
## Native payment candidate — release pending
|
|
76
|
+
|
|
77
|
+
After the coordinated MCP 2.2.0 / Node 2.1.0 release and funded acceptance,
|
|
78
|
+
`payable_fetch` is available when the owner enables payments. Until that release,
|
|
79
|
+
use the installed tool inventory and do not invent a payment capability.
|
|
80
|
+
|
|
81
|
+
The owner configures these MCP environment values (example limits only):
|
|
82
|
+
|
|
83
|
+
```json
|
|
84
|
+
{
|
|
85
|
+
"AIFINPAY_PAYMENTS_ENABLED": "1",
|
|
86
|
+
"AIFINPAY_GATEWAY_ORIGINS": "https://merchant.example",
|
|
87
|
+
"AIFINPAY_GATEWAY_PATH_MODE": "direct",
|
|
88
|
+
"AIFINPAY_MAX_USD": "0.12",
|
|
89
|
+
"AIFINPAY_DAILY_USD": "1.00",
|
|
90
|
+
"AIFINPAY_MAX_GAS_POL": "0.05"
|
|
91
|
+
}
|
|
92
|
+
```
|
|
93
|
+
|
|
94
|
+
Use an existing persistent wallet or create one through public MCP `init`;
|
|
95
|
+
load its encryption passphrase privately. Funding a wallet does not establish
|
|
96
|
+
unlimited spend authority. Use the owner's actual approved limits and origins.
|
|
97
|
+
Once configured, call `payable_fetch({"url":"https://merchant.example/api/data"})`.
|
|
98
|
+
The candidate supports GET resources and native Polygon AIFP-1 v1.4 payments.
|
|
99
|
+
It verifies the quote, price, deployment, signer and receipt, saves the transaction
|
|
100
|
+
before broadcasting, and reuses the purchased batch. No custom merchant script
|
|
101
|
+
is needed. Other protocol/version/asset paths fail closed.
|
|
102
|
+
|
|
103
|
+
A pending result retains the original transaction. Retrying recovers its receipt;
|
|
104
|
+
do not delete its journal, create a replacement wallet or switch contract versions.
|
|
105
|
+
Prepared-but-unbroadcast/reverted transactions and stale process locks require
|
|
106
|
+
owner reconciliation. Raw transactions and receipt JWTs remain private.
|
|
107
|
+
|
|
108
|
+
Discover routes on the exact requested origin: `/.well-known/x402.json` and any
|
|
109
|
+
API catalog linked by that site. A dev hostname does not imply testnet. If a
|
|
110
|
+
site's `llms.txt` incorrectly links another origin, report the broken link and
|
|
111
|
+
check discovery on the requested origin; never assume both sites share routes.
|
|
112
|
+
|
|
75
113
|
## Wallet source priority
|
|
76
114
|
|
|
77
115
|
The local server selects one identity in this order:
|
|
@@ -284,10 +322,9 @@ verified SPLITTER_ADDRESS_AMOY deployment first. Minimum-unit or cap errors are
|
|
|
284
322
|
terminal for that request: do not lower units below the server minimum, edit
|
|
285
323
|
quotes, or construct a manual nonce, receipt or transaction workaround.
|
|
286
324
|
|
|
287
|
-
This tool never broadcasts.
|
|
288
|
-
|
|
289
|
-
|
|
290
|
-
the full dev payment loop works. A prepaid batch means one settlement funding
|
|
325
|
+
This dev quote tool never broadcasts. The new low-level SDK executor supports
|
|
326
|
+
native Amoy v1.4, while MCP/fetchPaid receipt purchases remain Polygon-only.
|
|
327
|
+
A full paid testnet receipt flow is not yet claimed. A prepaid batch means one settlement funding
|
|
291
328
|
multiple API calls, not an arbitrary batch of on-chain transfers.
|
|
292
329
|
|
|
293
330
|
After any actual settlement, retain its quote and transaction reference.
|
|
@@ -5,7 +5,7 @@ description: Turn any website or API into one that charges AI agents to access
|
|
|
5
5
|
in stablecoins or native tokens on Polygon and Solana. Non-custodial — you
|
|
6
6
|
keep 99%.
|
|
7
7
|
license: MIT
|
|
8
|
-
version: 2.0.
|
|
8
|
+
version: 2.0.15
|
|
9
9
|
author: AiFinPay Support
|
|
10
10
|
metadata:
|
|
11
11
|
hermes:
|
|
@@ -81,6 +81,27 @@ an agent that arrives at just your domain learns which routes cost money.
|
|
|
81
81
|
> its 402 body; serve `buildDiscoveryDocument({...})` as JSON from
|
|
82
82
|
> `app/.well-known/x402.json/route.ts`.
|
|
83
83
|
|
|
84
|
+
## Discovery ownership and settlement compatibility
|
|
85
|
+
|
|
86
|
+
`aifpDiscovery({ merchantId, resources })` serves a document generated from the
|
|
87
|
+
resource definitions in your application. Self-hosted routes are maintained in
|
|
88
|
+
your code; installing gate does not upload their catalog to AiFinPay. Publish
|
|
89
|
+
`/.well-known/x402.json` and link it from `llms.txt` using the correct origin or
|
|
90
|
+
a relative URL. Keep dev and production catalogs separate. An API catalog such
|
|
91
|
+
as `/api/agent` can additionally describe query/body parameters.
|
|
92
|
+
|
|
93
|
+
Gate 0.3.3 source adds `instructions_url` (payer skill),
|
|
94
|
+
`merchant_instructions_url` (this skill), and `documentation_url`. These are
|
|
95
|
+
links to maintained public instructions, not stored wallet or receipt data.
|
|
96
|
+
Existing sites must upgrade/redeploy gate to emit those new fields.
|
|
97
|
+
|
|
98
|
+
The native-payment candidate requires a merchant explicitly registered for
|
|
99
|
+
`settlement_version: "1.4"` on a served Polygon deployment. Existing merchants
|
|
100
|
+
retain their prior version until their owner updates it. The backend candidate
|
|
101
|
+
accepts this setting at registration and authenticated update; version changes
|
|
102
|
+
must be coordinated with runtime readiness. Do not change the payout wallet
|
|
103
|
+
or claim compatibility merely because discovery returns 200.
|
|
104
|
+
|
|
84
105
|
## Register the site (get your merchant_id)
|
|
85
106
|
|
|
86
107
|
The gate needs a `merchant_id`. Two ways to get one:
|
package/package.json
CHANGED