agentpaywire commited on
Commit
b5e45d4
·
verified ·
1 Parent(s): f6c57c3

Sync library to 180 sources (site release b1c0be1)

Browse files
Files changed (5) hide show
  1. README.md +9 -9
  2. data/library.json +55 -4
  3. data/sources.csv +2 -0
  4. data/sources.jsonl +2 -0
  5. data/tags.json +21 -6
README.md CHANGED
@@ -26,7 +26,7 @@ configs:
26
 
27
  # Agent Paywire Knowledge Library
28
 
29
- A curated library of **178 verified sources** about how AI agents pay and get paid: machine-to-machine payment protocols (L402, x402 and others), Bitcoin and Lightning, stablecoins, agent protocols (e.g. MCP), and the surrounding security, IoT, robotics and regulation context. Each row is one source: a link to the original publication plus metadata and a short, neutral summary written for this library.
30
 
31
  This is the Hugging Face copy of the `agentpaywire-library` dataset published by [Agent Paywire](https://agentpaywire.com), a machine-readable reference site for AI agents on agent payments.
32
 
@@ -36,7 +36,7 @@ Linked pages, papers, repositories and specifications are **not** included and b
36
 
37
  - Built from the live site: https://agentpaywire.com/library (dataset card on the site: https://agentpaywire.com/datasets/agentpaywire-library/).
38
  - `data/sources.jsonl` is byte-identical to https://agentpaywire.com/dataset/library.jsonl (and https://agentpaywire.com/library.jsonl) at the time of this snapshot.
39
- - Snapshot taken 2026-11-07 (last updated 2026-11-07). `verified_at` dates: 2026-10-20 (111 rows), 2026-10-21 (9 rows), 2026-10-22 (15 rows), 2026-10-23 (6 rows), 2026-10-24 (5 rows), 2026-10-25 (2 rows), 2026-10-26 (2 rows), 2026-10-27 (1 row), 2026-10-28 (1 row), 2026-10-31 (7 rows), 2026-11-03 (7 rows), 2026-11-04 (2 rows), 2026-11-05 (4 rows), 2026-11-06 (2 rows), 2026-11-07 (4 rows); the library files (`library.json`, `tags.json`) report `generated_at` 2026-11-07T00:00:00Z.
40
  - The site is rebuilt when entries are published (on publish). This Hugging Face copy is a snapshot; the live site is authoritative and may be newer. For incremental sync use https://agentpaywire.com/changelog.json (filter by `verified_at`).
41
 
42
  ### Categories (snapshot)
@@ -44,8 +44,8 @@ Linked pages, papers, repositories and specifications are **not** included and b
44
  | category | entries |
45
  | --- | --- |
46
  | bitcoin-lightning (featured) | 43 |
47
- | payments | 72 |
48
- | agent-protocols | 33 |
49
  | robotics-autonomy | 4 |
50
  | iot | 4 |
51
  | datasets-benchmarks | 9 |
@@ -54,7 +54,7 @@ Linked pages, papers, repositories and specifications are **not** included and b
54
 
55
  ## Fields (`data/sources.jsonl`)
56
 
57
- One JSON object per line, 178 rows, single `train` split. Dates are `YYYY-MM-DD` strings in the file; the `datasets` JSON loader infers `date_published`, `verified_at` and `last_checked` as timestamps. JSON Schema: https://agentpaywire.com/schemas/library.schema.json (copy in `data/library.schema.json`).
58
 
59
  | field | type | description |
60
  | --- | --- | --- |
@@ -62,7 +62,7 @@ One JSON object per line, 178 rows, single `train` split. Dates are `YYYY-MM-DD`
62
  | `title` | string | Source title, copied from the page. |
63
  | `publisher` | string | Publisher name. |
64
  | `authors` | list of strings | People named on the source; empty list when none are named. |
65
- | `date_published` | string or null | `YYYY-MM-DD`; null when the source shows no publication date (79 of 178 rows). |
66
  | `url` | string | Canonical URL of the source. |
67
  | `type` | string | One of `announcement`, `directory`, `docs`, `regulatory`, `repo`, `report`, `research-paper`, `spec`. |
68
  | `category` | string | One of the categories above. |
@@ -79,9 +79,9 @@ One JSON object per line, 178 rows, single `train` split. Dates are `YYYY-MM-DD`
79
 
80
  | file | contents |
81
  | --- | --- |
82
- | `data/sources.jsonl` | Main table (default config). 178 rows. |
83
- | `data/sources.csv` | Same 178 rows as CSV (lists joined with `; `). Copy of https://agentpaywire.com/dataset/library.csv. |
84
- | `data/library.json` | Full library document with category list (8 categories) and 178 entries. From https://agentpaywire.com/api/library.json. |
85
  | `data/library.schema.json` | JSON Schema for the library documents. |
86
  | `data/tags.json` | Tag index, 70 tags with counts. From https://agentpaywire.com/api/library/tags.json. |
87
  | `data/protocol-facts.json` | Checked facts for 11 protocols (L402, BOLT 12, BIP 21, NWC, x402, MPP, AP2, ACP, UCP, MCP, A2A). From https://agentpaywire.com/api/protocol-facts.json. |
 
26
 
27
  # Agent Paywire Knowledge Library
28
 
29
+ A curated library of **180 verified sources** about how AI agents pay and get paid: machine-to-machine payment protocols (L402, x402 and others), Bitcoin and Lightning, stablecoins, agent protocols (e.g. MCP), and the surrounding security, IoT, robotics and regulation context. Each row is one source: a link to the original publication plus metadata and a short, neutral summary written for this library.
30
 
31
  This is the Hugging Face copy of the `agentpaywire-library` dataset published by [Agent Paywire](https://agentpaywire.com), a machine-readable reference site for AI agents on agent payments.
32
 
 
36
 
37
  - Built from the live site: https://agentpaywire.com/library (dataset card on the site: https://agentpaywire.com/datasets/agentpaywire-library/).
38
  - `data/sources.jsonl` is byte-identical to https://agentpaywire.com/dataset/library.jsonl (and https://agentpaywire.com/library.jsonl) at the time of this snapshot.
39
+ - Snapshot taken 2026-11-08 (last updated 2026-11-08). `verified_at` dates: 2026-10-20 (111 rows), 2026-10-21 (9 rows), 2026-10-22 (15 rows), 2026-10-23 (6 rows), 2026-10-24 (5 rows), 2026-10-25 (2 rows), 2026-10-26 (2 rows), 2026-10-27 (1 row), 2026-10-28 (1 row), 2026-10-31 (7 rows), 2026-11-03 (7 rows), 2026-11-04 (2 rows), 2026-11-05 (4 rows), 2026-11-06 (2 rows), 2026-11-07 (4 rows), 2026-11-08 (2 rows); the library files (`library.json`, `tags.json`) report `generated_at` 2026-11-08T00:00:00Z.
40
  - The site is rebuilt when entries are published (on publish). This Hugging Face copy is a snapshot; the live site is authoritative and may be newer. For incremental sync use https://agentpaywire.com/changelog.json (filter by `verified_at`).
41
 
42
  ### Categories (snapshot)
 
44
  | category | entries |
45
  | --- | --- |
46
  | bitcoin-lightning (featured) | 43 |
47
+ | payments | 73 |
48
+ | agent-protocols | 34 |
49
  | robotics-autonomy | 4 |
50
  | iot | 4 |
51
  | datasets-benchmarks | 9 |
 
54
 
55
  ## Fields (`data/sources.jsonl`)
56
 
57
+ One JSON object per line, 180 rows, single `train` split. Dates are `YYYY-MM-DD` strings in the file; the `datasets` JSON loader infers `date_published`, `verified_at` and `last_checked` as timestamps. JSON Schema: https://agentpaywire.com/schemas/library.schema.json (copy in `data/library.schema.json`).
58
 
59
  | field | type | description |
60
  | --- | --- | --- |
 
62
  | `title` | string | Source title, copied from the page. |
63
  | `publisher` | string | Publisher name. |
64
  | `authors` | list of strings | People named on the source; empty list when none are named. |
65
+ | `date_published` | string or null | `YYYY-MM-DD`; null when the source shows no publication date (80 of 180 rows). |
66
  | `url` | string | Canonical URL of the source. |
67
  | `type` | string | One of `announcement`, `directory`, `docs`, `regulatory`, `repo`, `report`, `research-paper`, `spec`. |
68
  | `category` | string | One of the categories above. |
 
79
 
80
  | file | contents |
81
  | --- | --- |
82
+ | `data/sources.jsonl` | Main table (default config). 180 rows. |
83
+ | `data/sources.csv` | Same 180 rows as CSV (lists joined with `; `). Copy of https://agentpaywire.com/dataset/library.csv. |
84
+ | `data/library.json` | Full library document with category list (8 categories) and 180 entries. From https://agentpaywire.com/api/library.json. |
85
  | `data/library.schema.json` | JSON Schema for the library documents. |
86
  | `data/tags.json` | Tag index, 70 tags with counts. From https://agentpaywire.com/api/library/tags.json. |
87
  | `data/protocol-facts.json` | Checked facts for 11 protocols (L402, BOLT 12, BIP 21, NWC, x402, MPP, AP2, ACP, UCP, MCP, A2A). From https://agentpaywire.com/api/protocol-facts.json. |
data/library.json CHANGED
@@ -1,13 +1,13 @@
1
  {
2
  "schema_version": "1",
3
- "generated_at": "2026-11-07T00:00:00Z",
4
  "disclaimer": {
5
  "text": "Not investment advice.",
6
  "url": "https://agentpaywire.com/disclaimer.json"
7
  },
8
  "$schema": "https://agentpaywire.com/schemas/library.schema.json",
9
  "license": "links + original short summaries; content belongs to publishers",
10
- "count": 178,
11
  "categories": [
12
  {
13
  "id": "bitcoin-lightning",
@@ -22,7 +22,7 @@
22
  "id": "payments",
23
  "label": "Payments",
24
  "featured": false,
25
- "count": 72,
26
  "json_url": "https://agentpaywire.com/api/library/payments.json",
27
  "markdown_url": "https://agentpaywire.com/library/payments.md",
28
  "html_url": "https://agentpaywire.com/library/payments/"
@@ -31,7 +31,7 @@
31
  "id": "agent-protocols",
32
  "label": "Agent protocols",
33
  "featured": false,
34
- "count": 33,
35
  "json_url": "https://agentpaywire.com/api/library/agent-protocols.json",
36
  "markdown_url": "https://agentpaywire.com/library/agent-protocols.md",
37
  "html_url": "https://agentpaywire.com/library/agent-protocols/"
@@ -1139,6 +1139,34 @@
1139
  "http_status": 200,
1140
  "archive_url": null
1141
  },
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1142
  {
1143
  "id": "stripe-link-cli",
1144
  "title": "stripe/link-cli",
@@ -3034,6 +3062,29 @@
3034
  "http_status": 200,
3035
  "archive_url": "http://web.archive.org/web/20261008125912/https://spec.openapis.org/oas/v3.1.0.html"
3036
  },
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
3037
  {
3038
  "id": "x402-scheme-exact-lnbtc",
3039
  "title": "x402 scheme: exact on Bitcoin Lightning (lnbtc)",
 
1
  {
2
  "schema_version": "1",
3
+ "generated_at": "2026-11-08T00:00:00Z",
4
  "disclaimer": {
5
  "text": "Not investment advice.",
6
  "url": "https://agentpaywire.com/disclaimer.json"
7
  },
8
  "$schema": "https://agentpaywire.com/schemas/library.schema.json",
9
  "license": "links + original short summaries; content belongs to publishers",
10
+ "count": 180,
11
  "categories": [
12
  {
13
  "id": "bitcoin-lightning",
 
22
  "id": "payments",
23
  "label": "Payments",
24
  "featured": false,
25
+ "count": 73,
26
  "json_url": "https://agentpaywire.com/api/library/payments.json",
27
  "markdown_url": "https://agentpaywire.com/library/payments.md",
28
  "html_url": "https://agentpaywire.com/library/payments/"
 
31
  "id": "agent-protocols",
32
  "label": "Agent protocols",
33
  "featured": false,
34
+ "count": 34,
35
  "json_url": "https://agentpaywire.com/api/library/agent-protocols.json",
36
  "markdown_url": "https://agentpaywire.com/library/agent-protocols.md",
37
  "html_url": "https://agentpaywire.com/library/agent-protocols/"
 
1139
  "http_status": 200,
1140
  "archive_url": null
1141
  },
1142
+ {
1143
+ "id": "arxiv-2611-05586-anduin-x402-reputation",
1144
+ "title": "Anduin: A Sybil-Resistant Agentic Marketplace Reputation System",
1145
+ "publisher": "Circle Research (arXiv)",
1146
+ "authors": [
1147
+ "Reza Ramji",
1148
+ "Preston Vander Vos",
1149
+ "Ziming Zeng",
1150
+ "Duc V. Le"
1151
+ ],
1152
+ "date_published": "2026-11-03",
1153
+ "url": "https://arxiv.org/abs/2611.05586",
1154
+ "type": "research-paper",
1155
+ "category": "payments",
1156
+ "status": "research",
1157
+ "summary": "Research paper, arXiv 2611.05586v1, submitted 2026-11-03. The PDF title is Anduin: A Sybil-Resistant Agentic Marketplace Reputation System. It lists Reza Ramji, Preston Vander Vos, Ziming Zeng, and Duc V. Le under Circle Research. A footnote says Ramji's work was done while the author was at Circle. The paper asks whether provider ratings can be built from payments already settled onchain, without changing the payment protocol. The introduction reports 66,073,201 x402 payments across 16 blockchains from 2026-03-23 through 2026-08-26, from 162,882 buyers and 50,390 providers, totalling $6.1 million, with a median payment of $0.01. Ratings come from a bipartite buyer-provider payment graph. Theorems 5.1 and 5.2 bound the max-flow rating by the attacker's outlay and, for that construction, by the querying buyer's own historical spend, under the paper's graph assumptions. This is not a production deployment. Section 6 uses a 90-day look-back ending 2026-06-21 and a cohort of 813 buyers. For the amplified construction with fee-inclusive dollar weights, Table 3 reports a top-1 capture cost of $8,259, 20 percent of those buyers' combined spend of $41,331, against $358 for collaborative filtering in the same row. Appendix A gives the authors' identification rules. On EVM they use EIP-3009 and the Permit2 exact and upto proxy addresses, and they keep direct EIP-3009 and multicall rows only when the facilitator or seller is already known. On Solana they keep an outgoing stablecoin transfer whose fee payer differs from the source authority when the fee payer is a known facilitator or the destination is a known seller. The appendix says EIP-3009, multicall, and Solana transfers with both an unknown facilitator and an unregistered seller are not captured.",
1158
+ "tags": [
1159
+ "x402",
1160
+ "research",
1161
+ "reputation",
1162
+ "sybil"
1163
+ ],
1164
+ "verified_at": "2026-11-08",
1165
+ "featured": false,
1166
+ "last_checked": "2026-11-08",
1167
+ "http_status": 200,
1168
+ "archive_url": null
1169
+ },
1170
  {
1171
  "id": "stripe-link-cli",
1172
  "title": "stripe/link-cli",
 
3062
  "http_status": 200,
3063
  "archive_url": "http://web.archive.org/web/20261008125912/https://spec.openapis.org/oas/v3.1.0.html"
3064
  },
3065
+ {
3066
+ "id": "x402-scheme-exact-svm",
3067
+ "title": "Exact Payment Scheme for Solana Virtual Machine (SVM) (`exact`)",
3068
+ "publisher": "x402 Foundation (GitHub)",
3069
+ "authors": [],
3070
+ "date_published": null,
3071
+ "url": "https://github.com/x402-foundation/x402/blob/main/specs/schemes/exact/scheme_exact_svm.md",
3072
+ "type": "spec",
3073
+ "category": "agent-protocols",
3074
+ "status": "spec_released",
3075
+ "summary": "Specification for the x402 exact scheme on Solana, read from main on 2026-11-08. The file does not state a publication date. Its latest commit is 2026-11-06, pull request #3615. PaymentRequirements extra includes feePayer and may include a memo of at most 256 bytes, a recentBlockhash, a lastValidBlockHeight decimal string, and splits. The resource server sends the payload to the sponsor's /verify endpoint and, after success, to /settle. The sponsor then signs as feePayer and submits the transaction. Section 3.1 classifies top-level instructions by program ID and discriminator instead of absolute position. Lighthouse instructions whose first data byte is 2 through 17, program L2TExMFKdjpN9kozasaurPirfHy9P8sbXoAN1qA3S95, may appear anywhere. The allowlist table calls that program Phantom assertions. MemoryWrite, MemoryClose, empty data, and unknown variants must be rejected. A sponsor may set preflight and postflight instruction-tuple allowlists. Both default to empty. Pull request #3615 also edits the Go, Python, and TypeScript facilitator source on main. Those notes are still unreleased fragments under go/.changes/unreleased, python/x402/changelog.d, and typescript/.changeset. npm @x402/svm 2.30.0 was published 2026-11-04, and PyPI x402 2.27.0 was uploaded the same day. instruction_layout.py is absent from tag pypi-x402@v2.27.0. This card does not say a published npm or PyPI package accepts Phantom Lighthouse guards. Pull request #4171, merged 2026-11-06, changes docs/schemes/exact.mdx only.",
3076
+ "tags": [
3077
+ "x402",
3078
+ "solana",
3079
+ "svm",
3080
+ "standards"
3081
+ ],
3082
+ "verified_at": "2026-11-08",
3083
+ "featured": false,
3084
+ "last_checked": "2026-11-08",
3085
+ "http_status": 200,
3086
+ "archive_url": null
3087
+ },
3088
  {
3089
  "id": "x402-scheme-exact-lnbtc",
3090
  "title": "x402 scheme: exact on Bitcoin Lightning (lnbtc)",
data/sources.csv CHANGED
@@ -43,6 +43,7 @@ nostr-nip-90-data-vending-machine,NIP-90: Data Vending Machine,GitHub (nostr-pro
43
  l402apps-com,L402 Apps,L402 Apps,,,https://www.l402apps.com/,directory,bitcoin-lightning,product_docs,Directory of apps and APIs presented as reachable through L402 payment gateways.,l402; lightning; directory,2026-10-20,true,2026-10-20,200,http://web.archive.org/web/20260615114727/https://www.l402apps.com/
44
  voltage-cli,Voltage CLI,Voltage,,,https://github.com/voltagecloud/voltage-cli,repo,bitcoin-lightning,product_docs,"Command-line client for the Voltage API. The README says it creates wallets and receives and sends Lightning payments, and on-chain payments where enabled, from a terminal, a script, or an AI agent. A change is only described until --execute is added. Every payment carries an ID, and the CLI never resubmits one on its own. Output is a table on a terminal and stable JSON when piped. License: MIT. Related: https://voltage.cloud/blog/prompt-to-payment-lightning-cli-agent-pack.",lightning; bitcoin; tools; agent-wallets,2026-10-23,,2026-10-23,200,
45
  x402-python-sdk-2-27-0,x402 Python SDK 2.27.0,x402 Foundation,,2026-11-04,https://pypi.org/project/x402/2.27.0/,repo,payments,product_docs,"Python package x402 2.27.0. PyPI lists the upload at 2026-11-04T20:03:25Z. The changelog heading is [2.27.0] - 2026-11-04. SVM exact payments in this SDK support Solana transaction version 1: facilitators advertise and accept extra.transactionVersions [0, 1] by default, and clients build the highest shared version. transaction_versions=[0] keeps a signer on version 0. The changelog describes this as the Python SDK, not as a requirement of every exact scheme. SIWX record_nonce runs after access is granted, and incomplete nonce-tracking is rejected. The upto Permit2 facilitator returns structured invalid_upto_evm_payload and invalid_upto_evm_required_amount errors. A throwing after_verify, after_settle, on_verify_failure, or on_settle_failure hook is logged and skipped; before_verify and before_settle still fail closed. x402[svm] requires solders>=0.29.0 and httpx and no longer installs solana. The GitHub releases API returned 404 for tag pypi-x402@v2.27.0 on 2026-11-06. Changelog: https://github.com/x402-foundation/x402/blob/main/python/x402/CHANGELOG.md. Related library entry: coinbase-x402-github (https://github.com/coinbase/x402).",x402; sdk,2026-11-06,,2026-11-06,200,
 
46
  stripe-link-cli,stripe/link-cli,Stripe (GitHub),,2026-10-29,https://github.com/stripe/link-cli,repo,payments,product_docs,"MIT-licensed CLI. The README says it lets an agent get payment credentials for one-time purchases and recurring payments without storing the card, and that it can run as a local MCP server with command link-cli and args --mcp. It says this is available to US and Canadian Link accounts. GitHub published @stripe/link-cli 1.0.0 on 2026-10-29: generated MCP configs run the installed binary instead of npx, and balance eligibility is removed from user info. 1.0.1 on 2026-10-30 fixes MPP payments rejected after approval and adds --use-approval-policy to mpp pay. The README documents mpp pay for Machine Payments Protocol purchases. A Tempo customer story says Link balances are settled in stablecoins on Tempo and are rolling out to Instinct users in eligible US regions. It does not name USDC for that balance.",agent-wallets; mcp; tools,2026-10-31,,2026-10-31,200,
47
  stripe-treasury-for-agents,Introducing Stripe Treasury for agents,Stripe,,2026-10-21,https://stripe.com/newsroom/news/treasury-for-agents,announcement,payments,news,"Stripe announced Stripe Treasury for agents, which lets a startup use an agent to check balances, pay invoices, transfer funds, and convert currencies. The business chooses which accounts and data the agent can access, whether it can read or take action, and when money movement requires human approval; the page says creating cards is coming soon and spending limits follow in the coming weeks.",agent-wallets; mcp; tools,2026-10-22,,2026-10-22,200,
48
  singularity-layer-training-lab-x402,"Training Lab, now over x402",Singularity Layer,,2026-10-21,https://www.x402layer.cc/blog/training-lab-x402,announcement,payments,news,"Singularity Layer's Training Lab post says an agent can request a training run, receive HTTP 402 with an exact price, and pay in USDC on Base or Solana or in USDG on Robinhood Chain. It states a limit of up to $500 per order and 3 paid runs per wallet per day over x402.",x402; stablecoins; micropayments; tools,2026-10-22,,2026-10-22,200,
@@ -128,6 +129,7 @@ cloudflare-agent-readiness,Introducing the Agent Readiness score. Check to see i
128
  mcp-specification-2025-06-18,Specification - Model Context Protocol (Version 2025-06-18),Model Context Protocol,,2025-06-18,https://modelcontextprotocol.io/specification/2025-06-18,spec,agent-protocols,spec_released,"Earlier dated revision of the MCP specification, covering authorization, transports, roots, sampling, elicitation, prompts and resources.",mcp; interop; tools,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20260924095810/https://modelcontextprotocol.io/specification/2025-06-18
129
  llms-txt,"The /llms.txt file, v2",llmstxt.org,Jeremy Howard,2024-09-03,https://llmstxt.org/,spec,agent-protocols,proposal,Proposal to standardise an /llms.txt file that gives agents information about how to use a website. The page was last modified on 10 August 2026.,llms-txt; interop,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261016034533/https://llmstxt.org/
130
  openapi-3-1-0,OpenAPI Specification v3.1.0,OpenAPI Initiative,,2021-02-15,https://spec.openapis.org/oas/v3.1.0.html,spec,agent-protocols,spec_released,"Standard, programming-language-agnostic interface description for HTTP APIs, widely used to describe tools and APIs for programmatic consumers.",openapi; interop,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261008125912/https://spec.openapis.org/oas/v3.1.0.html
 
131
  x402-scheme-exact-lnbtc,x402 scheme: exact on Bitcoin Lightning (lnbtc),x402 Foundation (GitHub),,,https://github.com/x402-foundation/x402/blob/main/specs/schemes/exact/scheme_exact_lnbtc.md,spec,agent-protocols,spec_released,"Specification for the x402 exact scheme on Lightning. It says the facilitator checks SHA-256(preimage) equals payment_hash and that the invoice signing key matches payTo. It supports only the bolt11 asset transfer method and the upfront flow. Mainnet MUST use lnbtc:000000000019d6689c085ae165831e93 and BOLT11 currency bc. Testnet MUST use lnbtc:000000000933ea01ad0ee984209779ba and currency tb. amount MUST be a decimal string of a positive integer number of millisatoshis, and bare numbers MUST NOT default to satoshis. The file does not state a publication date.",x402; lightning; standards,2026-11-03,true,2026-11-03,200,
132
  x402-scheme-batch-settlement,x402 scheme: batch-settlement,x402 Foundation (GitHub),,,https://github.com/x402-foundation/x402/blob/main/specs/schemes/batch-settlement/scheme_batch_settlement.md,spec,agent-protocols,spec_released,"Specification for the x402 batch-settlement scheme. The client provides a cryptographic payment commitment at request time, access is granted immediately, and value moves later through the network binding. The client commits up to PaymentRequirements.amount and the server may charge less. For exact and upto, the settlement result contains an onchain transaction hash. For batch-settlement it contains a commitment identifier. Bindings in the same directory are scheme_batch_settlement_evm.md, scheme_batch_settlement_svm.md, and scheme_batch_settlement_cloudflare.md. The file does not state a publication date.",x402; standards,2026-11-03,,2026-11-03,200,
133
  a2a-protocol-specification,Agent2Agent (A2A) Protocol Specification,A2A Protocol,,,https://a2a-protocol.org/latest/specification/,spec,agent-protocols,spec_released,"Official A2A specification (latest released version 1.0.0), an open standard for communication and interoperability between independent, potentially opaque AI agent systems built on different frameworks or by different vendors.",a2a; interop,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261009134313/https://a2a-protocol.org/latest/specification/
 
43
  l402apps-com,L402 Apps,L402 Apps,,,https://www.l402apps.com/,directory,bitcoin-lightning,product_docs,Directory of apps and APIs presented as reachable through L402 payment gateways.,l402; lightning; directory,2026-10-20,true,2026-10-20,200,http://web.archive.org/web/20260615114727/https://www.l402apps.com/
44
  voltage-cli,Voltage CLI,Voltage,,,https://github.com/voltagecloud/voltage-cli,repo,bitcoin-lightning,product_docs,"Command-line client for the Voltage API. The README says it creates wallets and receives and sends Lightning payments, and on-chain payments where enabled, from a terminal, a script, or an AI agent. A change is only described until --execute is added. Every payment carries an ID, and the CLI never resubmits one on its own. Output is a table on a terminal and stable JSON when piped. License: MIT. Related: https://voltage.cloud/blog/prompt-to-payment-lightning-cli-agent-pack.",lightning; bitcoin; tools; agent-wallets,2026-10-23,,2026-10-23,200,
45
  x402-python-sdk-2-27-0,x402 Python SDK 2.27.0,x402 Foundation,,2026-11-04,https://pypi.org/project/x402/2.27.0/,repo,payments,product_docs,"Python package x402 2.27.0. PyPI lists the upload at 2026-11-04T20:03:25Z. The changelog heading is [2.27.0] - 2026-11-04. SVM exact payments in this SDK support Solana transaction version 1: facilitators advertise and accept extra.transactionVersions [0, 1] by default, and clients build the highest shared version. transaction_versions=[0] keeps a signer on version 0. The changelog describes this as the Python SDK, not as a requirement of every exact scheme. SIWX record_nonce runs after access is granted, and incomplete nonce-tracking is rejected. The upto Permit2 facilitator returns structured invalid_upto_evm_payload and invalid_upto_evm_required_amount errors. A throwing after_verify, after_settle, on_verify_failure, or on_settle_failure hook is logged and skipped; before_verify and before_settle still fail closed. x402[svm] requires solders>=0.29.0 and httpx and no longer installs solana. The GitHub releases API returned 404 for tag pypi-x402@v2.27.0 on 2026-11-06. Changelog: https://github.com/x402-foundation/x402/blob/main/python/x402/CHANGELOG.md. Related library entry: coinbase-x402-github (https://github.com/coinbase/x402).",x402; sdk,2026-11-06,,2026-11-06,200,
46
+ arxiv-2611-05586-anduin-x402-reputation,Anduin: A Sybil-Resistant Agentic Marketplace Reputation System,Circle Research (arXiv),Reza Ramji; Preston Vander Vos; Ziming Zeng; Duc V. Le,2026-11-03,https://arxiv.org/abs/2611.05586,research-paper,payments,research,"Research paper, arXiv 2611.05586v1, submitted 2026-11-03. The PDF title is Anduin: A Sybil-Resistant Agentic Marketplace Reputation System. It lists Reza Ramji, Preston Vander Vos, Ziming Zeng, and Duc V. Le under Circle Research. A footnote says Ramji's work was done while the author was at Circle. The paper asks whether provider ratings can be built from payments already settled onchain, without changing the payment protocol. The introduction reports 66,073,201 x402 payments across 16 blockchains from 2026-03-23 through 2026-08-26, from 162,882 buyers and 50,390 providers, totalling $6.1 million, with a median payment of $0.01. Ratings come from a bipartite buyer-provider payment graph. Theorems 5.1 and 5.2 bound the max-flow rating by the attacker's outlay and, for that construction, by the querying buyer's own historical spend, under the paper's graph assumptions. This is not a production deployment. Section 6 uses a 90-day look-back ending 2026-06-21 and a cohort of 813 buyers. For the amplified construction with fee-inclusive dollar weights, Table 3 reports a top-1 capture cost of $8,259, 20 percent of those buyers' combined spend of $41,331, against $358 for collaborative filtering in the same row. Appendix A gives the authors' identification rules. On EVM they use EIP-3009 and the Permit2 exact and upto proxy addresses, and they keep direct EIP-3009 and multicall rows only when the facilitator or seller is already known. On Solana they keep an outgoing stablecoin transfer whose fee payer differs from the source authority when the fee payer is a known facilitator or the destination is a known seller. The appendix says EIP-3009, multicall, and Solana transfers with both an unknown facilitator and an unregistered seller are not captured.",x402; research; reputation; sybil,2026-11-08,,2026-11-08,200,
47
  stripe-link-cli,stripe/link-cli,Stripe (GitHub),,2026-10-29,https://github.com/stripe/link-cli,repo,payments,product_docs,"MIT-licensed CLI. The README says it lets an agent get payment credentials for one-time purchases and recurring payments without storing the card, and that it can run as a local MCP server with command link-cli and args --mcp. It says this is available to US and Canadian Link accounts. GitHub published @stripe/link-cli 1.0.0 on 2026-10-29: generated MCP configs run the installed binary instead of npx, and balance eligibility is removed from user info. 1.0.1 on 2026-10-30 fixes MPP payments rejected after approval and adds --use-approval-policy to mpp pay. The README documents mpp pay for Machine Payments Protocol purchases. A Tempo customer story says Link balances are settled in stablecoins on Tempo and are rolling out to Instinct users in eligible US regions. It does not name USDC for that balance.",agent-wallets; mcp; tools,2026-10-31,,2026-10-31,200,
48
  stripe-treasury-for-agents,Introducing Stripe Treasury for agents,Stripe,,2026-10-21,https://stripe.com/newsroom/news/treasury-for-agents,announcement,payments,news,"Stripe announced Stripe Treasury for agents, which lets a startup use an agent to check balances, pay invoices, transfer funds, and convert currencies. The business chooses which accounts and data the agent can access, whether it can read or take action, and when money movement requires human approval; the page says creating cards is coming soon and spending limits follow in the coming weeks.",agent-wallets; mcp; tools,2026-10-22,,2026-10-22,200,
49
  singularity-layer-training-lab-x402,"Training Lab, now over x402",Singularity Layer,,2026-10-21,https://www.x402layer.cc/blog/training-lab-x402,announcement,payments,news,"Singularity Layer's Training Lab post says an agent can request a training run, receive HTTP 402 with an exact price, and pay in USDC on Base or Solana or in USDG on Robinhood Chain. It states a limit of up to $500 per order and 3 paid runs per wallet per day over x402.",x402; stablecoins; micropayments; tools,2026-10-22,,2026-10-22,200,
 
129
  mcp-specification-2025-06-18,Specification - Model Context Protocol (Version 2025-06-18),Model Context Protocol,,2025-06-18,https://modelcontextprotocol.io/specification/2025-06-18,spec,agent-protocols,spec_released,"Earlier dated revision of the MCP specification, covering authorization, transports, roots, sampling, elicitation, prompts and resources.",mcp; interop; tools,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20260924095810/https://modelcontextprotocol.io/specification/2025-06-18
130
  llms-txt,"The /llms.txt file, v2",llmstxt.org,Jeremy Howard,2024-09-03,https://llmstxt.org/,spec,agent-protocols,proposal,Proposal to standardise an /llms.txt file that gives agents information about how to use a website. The page was last modified on 10 August 2026.,llms-txt; interop,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261016034533/https://llmstxt.org/
131
  openapi-3-1-0,OpenAPI Specification v3.1.0,OpenAPI Initiative,,2021-02-15,https://spec.openapis.org/oas/v3.1.0.html,spec,agent-protocols,spec_released,"Standard, programming-language-agnostic interface description for HTTP APIs, widely used to describe tools and APIs for programmatic consumers.",openapi; interop,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261008125912/https://spec.openapis.org/oas/v3.1.0.html
132
+ x402-scheme-exact-svm,Exact Payment Scheme for Solana Virtual Machine (SVM) (`exact`),x402 Foundation (GitHub),,,https://github.com/x402-foundation/x402/blob/main/specs/schemes/exact/scheme_exact_svm.md,spec,agent-protocols,spec_released,"Specification for the x402 exact scheme on Solana, read from main on 2026-11-08. The file does not state a publication date. Its latest commit is 2026-11-06, pull request #3615. PaymentRequirements extra includes feePayer and may include a memo of at most 256 bytes, a recentBlockhash, a lastValidBlockHeight decimal string, and splits. The resource server sends the payload to the sponsor's /verify endpoint and, after success, to /settle. The sponsor then signs as feePayer and submits the transaction. Section 3.1 classifies top-level instructions by program ID and discriminator instead of absolute position. Lighthouse instructions whose first data byte is 2 through 17, program L2TExMFKdjpN9kozasaurPirfHy9P8sbXoAN1qA3S95, may appear anywhere. The allowlist table calls that program Phantom assertions. MemoryWrite, MemoryClose, empty data, and unknown variants must be rejected. A sponsor may set preflight and postflight instruction-tuple allowlists. Both default to empty. Pull request #3615 also edits the Go, Python, and TypeScript facilitator source on main. Those notes are still unreleased fragments under go/.changes/unreleased, python/x402/changelog.d, and typescript/.changeset. npm @x402/svm 2.30.0 was published 2026-11-04, and PyPI x402 2.27.0 was uploaded the same day. instruction_layout.py is absent from tag pypi-x402@v2.27.0. This card does not say a published npm or PyPI package accepts Phantom Lighthouse guards. Pull request #4171, merged 2026-11-06, changes docs/schemes/exact.mdx only.",x402; solana; svm; standards,2026-11-08,,2026-11-08,200,
133
  x402-scheme-exact-lnbtc,x402 scheme: exact on Bitcoin Lightning (lnbtc),x402 Foundation (GitHub),,,https://github.com/x402-foundation/x402/blob/main/specs/schemes/exact/scheme_exact_lnbtc.md,spec,agent-protocols,spec_released,"Specification for the x402 exact scheme on Lightning. It says the facilitator checks SHA-256(preimage) equals payment_hash and that the invoice signing key matches payTo. It supports only the bolt11 asset transfer method and the upfront flow. Mainnet MUST use lnbtc:000000000019d6689c085ae165831e93 and BOLT11 currency bc. Testnet MUST use lnbtc:000000000933ea01ad0ee984209779ba and currency tb. amount MUST be a decimal string of a positive integer number of millisatoshis, and bare numbers MUST NOT default to satoshis. The file does not state a publication date.",x402; lightning; standards,2026-11-03,true,2026-11-03,200,
134
  x402-scheme-batch-settlement,x402 scheme: batch-settlement,x402 Foundation (GitHub),,,https://github.com/x402-foundation/x402/blob/main/specs/schemes/batch-settlement/scheme_batch_settlement.md,spec,agent-protocols,spec_released,"Specification for the x402 batch-settlement scheme. The client provides a cryptographic payment commitment at request time, access is granted immediately, and value moves later through the network binding. The client commits up to PaymentRequirements.amount and the server may charge less. For exact and upto, the settlement result contains an onchain transaction hash. For batch-settlement it contains a commitment identifier. Bindings in the same directory are scheme_batch_settlement_evm.md, scheme_batch_settlement_svm.md, and scheme_batch_settlement_cloudflare.md. The file does not state a publication date.",x402; standards,2026-11-03,,2026-11-03,200,
135
  a2a-protocol-specification,Agent2Agent (A2A) Protocol Specification,A2A Protocol,,,https://a2a-protocol.org/latest/specification/,spec,agent-protocols,spec_released,"Official A2A specification (latest released version 1.0.0), an open standard for communication and interoperability between independent, potentially opaque AI agent systems built on different frameworks or by different vendors.",a2a; interop,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261009134313/https://a2a-protocol.org/latest/specification/
data/sources.jsonl CHANGED
@@ -42,6 +42,7 @@
42
  {"id":"l402apps-com","title":"L402 Apps","publisher":"L402 Apps","authors":[],"date_published":null,"url":"https://www.l402apps.com/","type":"directory","category":"bitcoin-lightning","status":"product_docs","summary":"Directory of apps and APIs presented as reachable through L402 payment gateways.","tags":["l402","lightning","directory"],"verified_at":"2026-10-20","featured":true,"last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20260615114727/https://www.l402apps.com/"}
43
  {"id":"voltage-cli","title":"Voltage CLI","publisher":"Voltage","authors":[],"date_published":null,"url":"https://github.com/voltagecloud/voltage-cli","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"Command-line client for the Voltage API. The README says it creates wallets and receives and sends Lightning payments, and on-chain payments where enabled, from a terminal, a script, or an AI agent. A change is only described until --execute is added. Every payment carries an ID, and the CLI never resubmits one on its own. Output is a table on a terminal and stable JSON when piped. License: MIT. Related: https://voltage.cloud/blog/prompt-to-payment-lightning-cli-agent-pack.","tags":["lightning","bitcoin","tools","agent-wallets"],"verified_at":"2026-10-23","featured":false,"last_checked":"2026-10-23","http_status":200,"archive_url":null}
44
  {"id":"x402-python-sdk-2-27-0","title":"x402 Python SDK 2.27.0","publisher":"x402 Foundation","authors":[],"date_published":"2026-11-04","url":"https://pypi.org/project/x402/2.27.0/","type":"repo","category":"payments","status":"product_docs","summary":"Python package x402 2.27.0. PyPI lists the upload at 2026-11-04T20:03:25Z. The changelog heading is [2.27.0] - 2026-11-04. SVM exact payments in this SDK support Solana transaction version 1: facilitators advertise and accept extra.transactionVersions [0, 1] by default, and clients build the highest shared version. transaction_versions=[0] keeps a signer on version 0. The changelog describes this as the Python SDK, not as a requirement of every exact scheme. SIWX record_nonce runs after access is granted, and incomplete nonce-tracking is rejected. The upto Permit2 facilitator returns structured invalid_upto_evm_payload and invalid_upto_evm_required_amount errors. A throwing after_verify, after_settle, on_verify_failure, or on_settle_failure hook is logged and skipped; before_verify and before_settle still fail closed. x402[svm] requires solders>=0.29.0 and httpx and no longer installs solana. The GitHub releases API returned 404 for tag pypi-x402@v2.27.0 on 2026-11-06. Changelog: https://github.com/x402-foundation/x402/blob/main/python/x402/CHANGELOG.md. Related library entry: coinbase-x402-github (https://github.com/coinbase/x402).","tags":["x402","sdk"],"verified_at":"2026-11-06","featured":false,"last_checked":"2026-11-06","http_status":200,"archive_url":null}
 
45
  {"id":"stripe-link-cli","title":"stripe/link-cli","publisher":"Stripe (GitHub)","authors":[],"date_published":"2026-10-29","url":"https://github.com/stripe/link-cli","type":"repo","category":"payments","status":"product_docs","summary":"MIT-licensed CLI. The README says it lets an agent get payment credentials for one-time purchases and recurring payments without storing the card, and that it can run as a local MCP server with command link-cli and args --mcp. It says this is available to US and Canadian Link accounts. GitHub published @stripe/link-cli 1.0.0 on 2026-10-29: generated MCP configs run the installed binary instead of npx, and balance eligibility is removed from user info. 1.0.1 on 2026-10-30 fixes MPP payments rejected after approval and adds --use-approval-policy to mpp pay. The README documents mpp pay for Machine Payments Protocol purchases. A Tempo customer story says Link balances are settled in stablecoins on Tempo and are rolling out to Instinct users in eligible US regions. It does not name USDC for that balance.","tags":["agent-wallets","mcp","tools"],"verified_at":"2026-10-31","featured":false,"last_checked":"2026-10-31","http_status":200,"archive_url":null}
46
  {"id":"stripe-treasury-for-agents","title":"Introducing Stripe Treasury for agents","publisher":"Stripe","authors":[],"date_published":"2026-10-21","url":"https://stripe.com/newsroom/news/treasury-for-agents","type":"announcement","category":"payments","status":"news","summary":"Stripe announced Stripe Treasury for agents, which lets a startup use an agent to check balances, pay invoices, transfer funds, and convert currencies. The business chooses which accounts and data the agent can access, whether it can read or take action, and when money movement requires human approval; the page says creating cards is coming soon and spending limits follow in the coming weeks.","tags":["agent-wallets","mcp","tools"],"verified_at":"2026-10-22","last_checked":"2026-10-22","http_status":200,"archive_url":null}
47
  {"id":"singularity-layer-training-lab-x402","title":"Training Lab, now over x402","publisher":"Singularity Layer","authors":[],"date_published":"2026-10-21","url":"https://www.x402layer.cc/blog/training-lab-x402","type":"announcement","category":"payments","status":"news","summary":"Singularity Layer's Training Lab post says an agent can request a training run, receive HTTP 402 with an exact price, and pay in USDC on Base or Solana or in USDG on Robinhood Chain. It states a limit of up to $500 per order and 3 paid runs per wallet per day over x402.","tags":["x402","stablecoins","micropayments","tools"],"verified_at":"2026-10-22","last_checked":"2026-10-22","http_status":200,"archive_url":null}
@@ -127,6 +128,7 @@
127
  {"id":"mcp-specification-2025-06-18","title":"Specification - Model Context Protocol (Version 2025-06-18)","publisher":"Model Context Protocol","authors":[],"date_published":"2025-06-18","url":"https://modelcontextprotocol.io/specification/2025-06-18","type":"spec","category":"agent-protocols","status":"spec_released","summary":"Earlier dated revision of the MCP specification, covering authorization, transports, roots, sampling, elicitation, prompts and resources.","tags":["mcp","interop","tools"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20260924095810/https://modelcontextprotocol.io/specification/2025-06-18"}
128
  {"id":"llms-txt","title":"The /llms.txt file, v2","publisher":"llmstxt.org","authors":["Jeremy Howard"],"date_published":"2024-09-03","url":"https://llmstxt.org/","type":"spec","category":"agent-protocols","status":"proposal","summary":"Proposal to standardise an /llms.txt file that gives agents information about how to use a website. The page was last modified on 10 August 2026.","tags":["llms-txt","interop"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261016034533/https://llmstxt.org/"}
129
  {"id":"openapi-3-1-0","title":"OpenAPI Specification v3.1.0","publisher":"OpenAPI Initiative","authors":[],"date_published":"2021-02-15","url":"https://spec.openapis.org/oas/v3.1.0.html","type":"spec","category":"agent-protocols","status":"spec_released","summary":"Standard, programming-language-agnostic interface description for HTTP APIs, widely used to describe tools and APIs for programmatic consumers.","tags":["openapi","interop"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261008125912/https://spec.openapis.org/oas/v3.1.0.html"}
 
130
  {"id":"x402-scheme-exact-lnbtc","title":"x402 scheme: exact on Bitcoin Lightning (lnbtc)","publisher":"x402 Foundation (GitHub)","authors":[],"date_published":null,"url":"https://github.com/x402-foundation/x402/blob/main/specs/schemes/exact/scheme_exact_lnbtc.md","type":"spec","category":"agent-protocols","status":"spec_released","summary":"Specification for the x402 exact scheme on Lightning. It says the facilitator checks SHA-256(preimage) equals payment_hash and that the invoice signing key matches payTo. It supports only the bolt11 asset transfer method and the upfront flow. Mainnet MUST use lnbtc:000000000019d6689c085ae165831e93 and BOLT11 currency bc. Testnet MUST use lnbtc:000000000933ea01ad0ee984209779ba and currency tb. amount MUST be a decimal string of a positive integer number of millisatoshis, and bare numbers MUST NOT default to satoshis. The file does not state a publication date.","tags":["x402","lightning","standards"],"verified_at":"2026-11-03","featured":true,"last_checked":"2026-11-03","http_status":200,"archive_url":null}
131
  {"id":"x402-scheme-batch-settlement","title":"x402 scheme: batch-settlement","publisher":"x402 Foundation (GitHub)","authors":[],"date_published":null,"url":"https://github.com/x402-foundation/x402/blob/main/specs/schemes/batch-settlement/scheme_batch_settlement.md","type":"spec","category":"agent-protocols","status":"spec_released","summary":"Specification for the x402 batch-settlement scheme. The client provides a cryptographic payment commitment at request time, access is granted immediately, and value moves later through the network binding. The client commits up to PaymentRequirements.amount and the server may charge less. For exact and upto, the settlement result contains an onchain transaction hash. For batch-settlement it contains a commitment identifier. Bindings in the same directory are scheme_batch_settlement_evm.md, scheme_batch_settlement_svm.md, and scheme_batch_settlement_cloudflare.md. The file does not state a publication date.","tags":["x402","standards"],"verified_at":"2026-11-03","featured":false,"last_checked":"2026-11-03","http_status":200,"archive_url":null}
132
  {"id":"a2a-protocol-specification","title":"Agent2Agent (A2A) Protocol Specification","publisher":"A2A Protocol","authors":[],"date_published":null,"url":"https://a2a-protocol.org/latest/specification/","type":"spec","category":"agent-protocols","status":"spec_released","summary":"Official A2A specification (latest released version 1.0.0), an open standard for communication and interoperability between independent, potentially opaque AI agent systems built on different frameworks or by different vendors.","tags":["a2a","interop"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261009134313/https://a2a-protocol.org/latest/specification/"}
 
42
  {"id":"l402apps-com","title":"L402 Apps","publisher":"L402 Apps","authors":[],"date_published":null,"url":"https://www.l402apps.com/","type":"directory","category":"bitcoin-lightning","status":"product_docs","summary":"Directory of apps and APIs presented as reachable through L402 payment gateways.","tags":["l402","lightning","directory"],"verified_at":"2026-10-20","featured":true,"last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20260615114727/https://www.l402apps.com/"}
43
  {"id":"voltage-cli","title":"Voltage CLI","publisher":"Voltage","authors":[],"date_published":null,"url":"https://github.com/voltagecloud/voltage-cli","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"Command-line client for the Voltage API. The README says it creates wallets and receives and sends Lightning payments, and on-chain payments where enabled, from a terminal, a script, or an AI agent. A change is only described until --execute is added. Every payment carries an ID, and the CLI never resubmits one on its own. Output is a table on a terminal and stable JSON when piped. License: MIT. Related: https://voltage.cloud/blog/prompt-to-payment-lightning-cli-agent-pack.","tags":["lightning","bitcoin","tools","agent-wallets"],"verified_at":"2026-10-23","featured":false,"last_checked":"2026-10-23","http_status":200,"archive_url":null}
44
  {"id":"x402-python-sdk-2-27-0","title":"x402 Python SDK 2.27.0","publisher":"x402 Foundation","authors":[],"date_published":"2026-11-04","url":"https://pypi.org/project/x402/2.27.0/","type":"repo","category":"payments","status":"product_docs","summary":"Python package x402 2.27.0. PyPI lists the upload at 2026-11-04T20:03:25Z. The changelog heading is [2.27.0] - 2026-11-04. SVM exact payments in this SDK support Solana transaction version 1: facilitators advertise and accept extra.transactionVersions [0, 1] by default, and clients build the highest shared version. transaction_versions=[0] keeps a signer on version 0. The changelog describes this as the Python SDK, not as a requirement of every exact scheme. SIWX record_nonce runs after access is granted, and incomplete nonce-tracking is rejected. The upto Permit2 facilitator returns structured invalid_upto_evm_payload and invalid_upto_evm_required_amount errors. A throwing after_verify, after_settle, on_verify_failure, or on_settle_failure hook is logged and skipped; before_verify and before_settle still fail closed. x402[svm] requires solders>=0.29.0 and httpx and no longer installs solana. The GitHub releases API returned 404 for tag pypi-x402@v2.27.0 on 2026-11-06. Changelog: https://github.com/x402-foundation/x402/blob/main/python/x402/CHANGELOG.md. Related library entry: coinbase-x402-github (https://github.com/coinbase/x402).","tags":["x402","sdk"],"verified_at":"2026-11-06","featured":false,"last_checked":"2026-11-06","http_status":200,"archive_url":null}
45
+ {"id":"arxiv-2611-05586-anduin-x402-reputation","title":"Anduin: A Sybil-Resistant Agentic Marketplace Reputation System","publisher":"Circle Research (arXiv)","authors":["Reza Ramji","Preston Vander Vos","Ziming Zeng","Duc V. Le"],"date_published":"2026-11-03","url":"https://arxiv.org/abs/2611.05586","type":"research-paper","category":"payments","status":"research","summary":"Research paper, arXiv 2611.05586v1, submitted 2026-11-03. The PDF title is Anduin: A Sybil-Resistant Agentic Marketplace Reputation System. It lists Reza Ramji, Preston Vander Vos, Ziming Zeng, and Duc V. Le under Circle Research. A footnote says Ramji's work was done while the author was at Circle. The paper asks whether provider ratings can be built from payments already settled onchain, without changing the payment protocol. The introduction reports 66,073,201 x402 payments across 16 blockchains from 2026-03-23 through 2026-08-26, from 162,882 buyers and 50,390 providers, totalling $6.1 million, with a median payment of $0.01. Ratings come from a bipartite buyer-provider payment graph. Theorems 5.1 and 5.2 bound the max-flow rating by the attacker's outlay and, for that construction, by the querying buyer's own historical spend, under the paper's graph assumptions. This is not a production deployment. Section 6 uses a 90-day look-back ending 2026-06-21 and a cohort of 813 buyers. For the amplified construction with fee-inclusive dollar weights, Table 3 reports a top-1 capture cost of $8,259, 20 percent of those buyers' combined spend of $41,331, against $358 for collaborative filtering in the same row. Appendix A gives the authors' identification rules. On EVM they use EIP-3009 and the Permit2 exact and upto proxy addresses, and they keep direct EIP-3009 and multicall rows only when the facilitator or seller is already known. On Solana they keep an outgoing stablecoin transfer whose fee payer differs from the source authority when the fee payer is a known facilitator or the destination is a known seller. The appendix says EIP-3009, multicall, and Solana transfers with both an unknown facilitator and an unregistered seller are not captured.","tags":["x402","research","reputation","sybil"],"verified_at":"2026-11-08","featured":false,"last_checked":"2026-11-08","http_status":200,"archive_url":null}
46
  {"id":"stripe-link-cli","title":"stripe/link-cli","publisher":"Stripe (GitHub)","authors":[],"date_published":"2026-10-29","url":"https://github.com/stripe/link-cli","type":"repo","category":"payments","status":"product_docs","summary":"MIT-licensed CLI. The README says it lets an agent get payment credentials for one-time purchases and recurring payments without storing the card, and that it can run as a local MCP server with command link-cli and args --mcp. It says this is available to US and Canadian Link accounts. GitHub published @stripe/link-cli 1.0.0 on 2026-10-29: generated MCP configs run the installed binary instead of npx, and balance eligibility is removed from user info. 1.0.1 on 2026-10-30 fixes MPP payments rejected after approval and adds --use-approval-policy to mpp pay. The README documents mpp pay for Machine Payments Protocol purchases. A Tempo customer story says Link balances are settled in stablecoins on Tempo and are rolling out to Instinct users in eligible US regions. It does not name USDC for that balance.","tags":["agent-wallets","mcp","tools"],"verified_at":"2026-10-31","featured":false,"last_checked":"2026-10-31","http_status":200,"archive_url":null}
47
  {"id":"stripe-treasury-for-agents","title":"Introducing Stripe Treasury for agents","publisher":"Stripe","authors":[],"date_published":"2026-10-21","url":"https://stripe.com/newsroom/news/treasury-for-agents","type":"announcement","category":"payments","status":"news","summary":"Stripe announced Stripe Treasury for agents, which lets a startup use an agent to check balances, pay invoices, transfer funds, and convert currencies. The business chooses which accounts and data the agent can access, whether it can read or take action, and when money movement requires human approval; the page says creating cards is coming soon and spending limits follow in the coming weeks.","tags":["agent-wallets","mcp","tools"],"verified_at":"2026-10-22","last_checked":"2026-10-22","http_status":200,"archive_url":null}
48
  {"id":"singularity-layer-training-lab-x402","title":"Training Lab, now over x402","publisher":"Singularity Layer","authors":[],"date_published":"2026-10-21","url":"https://www.x402layer.cc/blog/training-lab-x402","type":"announcement","category":"payments","status":"news","summary":"Singularity Layer's Training Lab post says an agent can request a training run, receive HTTP 402 with an exact price, and pay in USDC on Base or Solana or in USDG on Robinhood Chain. It states a limit of up to $500 per order and 3 paid runs per wallet per day over x402.","tags":["x402","stablecoins","micropayments","tools"],"verified_at":"2026-10-22","last_checked":"2026-10-22","http_status":200,"archive_url":null}
 
128
  {"id":"mcp-specification-2025-06-18","title":"Specification - Model Context Protocol (Version 2025-06-18)","publisher":"Model Context Protocol","authors":[],"date_published":"2025-06-18","url":"https://modelcontextprotocol.io/specification/2025-06-18","type":"spec","category":"agent-protocols","status":"spec_released","summary":"Earlier dated revision of the MCP specification, covering authorization, transports, roots, sampling, elicitation, prompts and resources.","tags":["mcp","interop","tools"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20260924095810/https://modelcontextprotocol.io/specification/2025-06-18"}
129
  {"id":"llms-txt","title":"The /llms.txt file, v2","publisher":"llmstxt.org","authors":["Jeremy Howard"],"date_published":"2024-09-03","url":"https://llmstxt.org/","type":"spec","category":"agent-protocols","status":"proposal","summary":"Proposal to standardise an /llms.txt file that gives agents information about how to use a website. The page was last modified on 10 August 2026.","tags":["llms-txt","interop"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261016034533/https://llmstxt.org/"}
130
  {"id":"openapi-3-1-0","title":"OpenAPI Specification v3.1.0","publisher":"OpenAPI Initiative","authors":[],"date_published":"2021-02-15","url":"https://spec.openapis.org/oas/v3.1.0.html","type":"spec","category":"agent-protocols","status":"spec_released","summary":"Standard, programming-language-agnostic interface description for HTTP APIs, widely used to describe tools and APIs for programmatic consumers.","tags":["openapi","interop"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261008125912/https://spec.openapis.org/oas/v3.1.0.html"}
131
+ {"id":"x402-scheme-exact-svm","title":"Exact Payment Scheme for Solana Virtual Machine (SVM) (`exact`)","publisher":"x402 Foundation (GitHub)","authors":[],"date_published":null,"url":"https://github.com/x402-foundation/x402/blob/main/specs/schemes/exact/scheme_exact_svm.md","type":"spec","category":"agent-protocols","status":"spec_released","summary":"Specification for the x402 exact scheme on Solana, read from main on 2026-11-08. The file does not state a publication date. Its latest commit is 2026-11-06, pull request #3615. PaymentRequirements extra includes feePayer and may include a memo of at most 256 bytes, a recentBlockhash, a lastValidBlockHeight decimal string, and splits. The resource server sends the payload to the sponsor's /verify endpoint and, after success, to /settle. The sponsor then signs as feePayer and submits the transaction. Section 3.1 classifies top-level instructions by program ID and discriminator instead of absolute position. Lighthouse instructions whose first data byte is 2 through 17, program L2TExMFKdjpN9kozasaurPirfHy9P8sbXoAN1qA3S95, may appear anywhere. The allowlist table calls that program Phantom assertions. MemoryWrite, MemoryClose, empty data, and unknown variants must be rejected. A sponsor may set preflight and postflight instruction-tuple allowlists. Both default to empty. Pull request #3615 also edits the Go, Python, and TypeScript facilitator source on main. Those notes are still unreleased fragments under go/.changes/unreleased, python/x402/changelog.d, and typescript/.changeset. npm @x402/svm 2.30.0 was published 2026-11-04, and PyPI x402 2.27.0 was uploaded the same day. instruction_layout.py is absent from tag pypi-x402@v2.27.0. This card does not say a published npm or PyPI package accepts Phantom Lighthouse guards. Pull request #4171, merged 2026-11-06, changes docs/schemes/exact.mdx only.","tags":["x402","solana","svm","standards"],"verified_at":"2026-11-08","featured":false,"last_checked":"2026-11-08","http_status":200,"archive_url":null}
132
  {"id":"x402-scheme-exact-lnbtc","title":"x402 scheme: exact on Bitcoin Lightning (lnbtc)","publisher":"x402 Foundation (GitHub)","authors":[],"date_published":null,"url":"https://github.com/x402-foundation/x402/blob/main/specs/schemes/exact/scheme_exact_lnbtc.md","type":"spec","category":"agent-protocols","status":"spec_released","summary":"Specification for the x402 exact scheme on Lightning. It says the facilitator checks SHA-256(preimage) equals payment_hash and that the invoice signing key matches payTo. It supports only the bolt11 asset transfer method and the upfront flow. Mainnet MUST use lnbtc:000000000019d6689c085ae165831e93 and BOLT11 currency bc. Testnet MUST use lnbtc:000000000933ea01ad0ee984209779ba and currency tb. amount MUST be a decimal string of a positive integer number of millisatoshis, and bare numbers MUST NOT default to satoshis. The file does not state a publication date.","tags":["x402","lightning","standards"],"verified_at":"2026-11-03","featured":true,"last_checked":"2026-11-03","http_status":200,"archive_url":null}
133
  {"id":"x402-scheme-batch-settlement","title":"x402 scheme: batch-settlement","publisher":"x402 Foundation (GitHub)","authors":[],"date_published":null,"url":"https://github.com/x402-foundation/x402/blob/main/specs/schemes/batch-settlement/scheme_batch_settlement.md","type":"spec","category":"agent-protocols","status":"spec_released","summary":"Specification for the x402 batch-settlement scheme. The client provides a cryptographic payment commitment at request time, access is granted immediately, and value moves later through the network binding. The client commits up to PaymentRequirements.amount and the server may charge less. For exact and upto, the settlement result contains an onchain transaction hash. For batch-settlement it contains a commitment identifier. Bindings in the same directory are scheme_batch_settlement_evm.md, scheme_batch_settlement_svm.md, and scheme_batch_settlement_cloudflare.md. The file does not state a publication date.","tags":["x402","standards"],"verified_at":"2026-11-03","featured":false,"last_checked":"2026-11-03","http_status":200,"archive_url":null}
134
  {"id":"a2a-protocol-specification","title":"Agent2Agent (A2A) Protocol Specification","publisher":"A2A Protocol","authors":[],"date_published":null,"url":"https://a2a-protocol.org/latest/specification/","type":"spec","category":"agent-protocols","status":"spec_released","summary":"Official A2A specification (latest released version 1.0.0), an open standard for communication and interoperability between independent, potentially opaque AI agent systems built on different frameworks or by different vendors.","tags":["a2a","interop"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261009134313/https://a2a-protocol.org/latest/specification/"}
data/tags.json CHANGED
@@ -1,7 +1,7 @@
1
  {
2
  "schema_version": "1",
3
- "generated_at": "2026-11-07T00:00:00Z",
4
- "count": 78,
5
  "tags": [
6
  {
7
  "tag": "a2a",
@@ -283,9 +283,14 @@
283
  "count": 7,
284
  "json_url": "https://agentpaywire.com/api/library/tag/release.json"
285
  },
 
 
 
 
 
286
  {
287
  "tag": "research",
288
- "count": 22,
289
  "json_url": "https://agentpaywire.com/api/library/tag/research.json"
290
  },
291
  {
@@ -315,7 +320,7 @@
315
  },
316
  {
317
  "tag": "solana",
318
- "count": 1,
319
  "json_url": "https://agentpaywire.com/api/library/tag/solana.json"
320
  },
321
  {
@@ -340,7 +345,7 @@
340
  },
341
  {
342
  "tag": "standards",
343
- "count": 29,
344
  "json_url": "https://agentpaywire.com/api/library/tag/standards.json"
345
  },
346
  {
@@ -348,6 +353,16 @@
348
  "count": 1,
349
  "json_url": "https://agentpaywire.com/api/library/tag/streaming-payments.json"
350
  },
 
 
 
 
 
 
 
 
 
 
351
  {
352
  "tag": "tokenization",
353
  "count": 5,
@@ -390,7 +405,7 @@
390
  },
391
  {
392
  "tag": "x402",
393
- "count": 35,
394
  "json_url": "https://agentpaywire.com/api/library/tag/x402.json"
395
  }
396
  ]
 
1
  {
2
  "schema_version": "1",
3
+ "generated_at": "2026-11-08T00:00:00Z",
4
+ "count": 81,
5
  "tags": [
6
  {
7
  "tag": "a2a",
 
283
  "count": 7,
284
  "json_url": "https://agentpaywire.com/api/library/tag/release.json"
285
  },
286
+ {
287
+ "tag": "reputation",
288
+ "count": 1,
289
+ "json_url": "https://agentpaywire.com/api/library/tag/reputation.json"
290
+ },
291
  {
292
  "tag": "research",
293
+ "count": 23,
294
  "json_url": "https://agentpaywire.com/api/library/tag/research.json"
295
  },
296
  {
 
320
  },
321
  {
322
  "tag": "solana",
323
+ "count": 2,
324
  "json_url": "https://agentpaywire.com/api/library/tag/solana.json"
325
  },
326
  {
 
345
  },
346
  {
347
  "tag": "standards",
348
+ "count": 30,
349
  "json_url": "https://agentpaywire.com/api/library/tag/standards.json"
350
  },
351
  {
 
353
  "count": 1,
354
  "json_url": "https://agentpaywire.com/api/library/tag/streaming-payments.json"
355
  },
356
+ {
357
+ "tag": "svm",
358
+ "count": 1,
359
+ "json_url": "https://agentpaywire.com/api/library/tag/svm.json"
360
+ },
361
+ {
362
+ "tag": "sybil",
363
+ "count": 1,
364
+ "json_url": "https://agentpaywire.com/api/library/tag/sybil.json"
365
+ },
366
  {
367
  "tag": "tokenization",
368
  "count": 5,
 
405
  },
406
  {
407
  "tag": "x402",
408
+ "count": 37,
409
  "json_url": "https://agentpaywire.com/api/library/tag/x402.json"
410
  }
411
  ]