agentpaywire commited on
Commit
c49b8c9
·
verified ·
1 Parent(s): 3dea70b

Update to 146 sources (2026-10-23)

Browse files

Sync from live agentpaywire.com files (library.jsonl, library.csv, api/library.json, tags, schema, protocol facts, bots, about). Adds status field. Card: counts, categories, repo id in usage example.

README.md CHANGED
@@ -26,7 +26,7 @@ configs:
26
 
27
  # Agent Paywire Knowledge Library
28
 
29
- A curated library of **125 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,25 +36,25 @@ 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: records have `verified_at` = 2026-10-20 (113 rows) or 2026-10-21 (12 rows); site files report `generated_at` 2026-10-21T00: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)
43
 
44
  | category | entries |
45
  | --- | --- |
46
- | bitcoin-lightning (featured) | 24 |
47
- | payments | 48 |
48
- | agent-protocols | 23 |
49
- | robotics-autonomy | 3 |
50
  | iot | 4 |
51
- | datasets-benchmarks | 6 |
52
- | safety-security | 4 |
53
- | regulation | 1 |
54
 
55
  ## Fields (`data/sources.jsonl`)
56
 
57
- One JSON object per line, 125 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,14 +62,15 @@ One JSON object per line, 125 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 (66 of 125 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. |
 
69
  | `summary` | string | Short summary written for this library. |
70
  | `tags` | list of strings | Topic slugs (e.g. `l402`, `x402`, `lightning`, `mcp`, `stablecoins`). |
71
  | `verified_at` | string | Date the URL, title and publication date were checked. |
72
- | `featured` | bool | `true` for featured Bitcoin and Lightning sources; key absent (null when loaded) otherwise. |
73
  | `last_checked` | string | Date the link check last ran. |
74
  | `http_status` | int or null | HTTP status from that check; null when the request failed. |
75
  | `archive_url` | string or null | Wayback Machine snapshot URL; null when none was available. |
@@ -78,9 +79,9 @@ One JSON object per line, 125 rows, single `train` split. Dates are `YYYY-MM-DD`
78
 
79
  | file | contents |
80
  | --- | --- |
81
- | `data/sources.jsonl` | Main table (default config). 125 rows. |
82
- | `data/sources.csv` | Same 125 rows as CSV (lists joined with `; `). Copy of https://agentpaywire.com/dataset/library.csv. |
83
- | `data/library.json` | Full library document with category list (8 categories) and 125 entries. From https://agentpaywire.com/api/library.json. |
84
  | `data/library.schema.json` | JSON Schema for the library documents. |
85
  | `data/tags.json` | Tag index, 51 tags with counts. From https://agentpaywire.com/api/library/tags.json. |
86
  | `data/protocol-facts.json` | Checked facts for 9 protocols (L402, BOLT 12, BIP 21, NWC, x402, MPP, AP2, ACP, UCP). From https://agentpaywire.com/api/protocol-facts.json. |
@@ -95,7 +96,7 @@ Only `data/sources.jsonl` is loaded by `load_dataset`; the other files are suppl
95
  ```python
96
  from datasets import load_dataset
97
 
98
- ds = load_dataset("agentpaywire/agent-payments-library", split="train")
99
  print(ds[0]["title"], ds[0]["url"])
100
 
101
  l402 = ds.filter(lambda r: "l402" in r["tags"])
@@ -106,6 +107,7 @@ Live access for agents:
106
  - MCP server (read-only, streamable HTTP): https://mcp.agentpaywire.com/mcp — tools include `list_articles`, `latest_sources`, `changes_since`, `protocol_facts`, `list_bots` and `list_datasets`.
107
  - llms.txt with links to every machine-readable file: https://agentpaywire.com/llms.txt
108
  - Endpoint index: https://agentpaywire.com/api/index.json
 
109
 
110
  The public files need no account or API key.
111
 
@@ -115,6 +117,8 @@ The public files need no account or API key.
115
 
116
  The license covers this dataset's metadata and the short summaries written for Agent Paywire. Linked content belongs to its publishers and is not licensed by this dataset. Third-party datasets listed in `data/datasets-index.*` and bots listed in `data/bots.json` carry their own licenses, as recorded in those files.
117
 
 
 
118
  Attribution: "Agent Paywire library, https://agentpaywire.com, CC BY 4.0".
119
 
120
  ## Disclaimer
 
26
 
27
  # Agent Paywire Knowledge Library
28
 
29
+ A curated library of **146 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-10-23 (last updated 2026-10-23). `verified_at` dates: 2026-10-20 (113 rows), 2026-10-21 (11 rows), 2026-10-22 (16 rows), 2026-10-23 (6 rows); the library files (`library.json`, `tags.json`) report `generated_at` 2026-10-23T00: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)
43
 
44
  | category | entries |
45
  | --- | --- |
46
+ | bitcoin-lightning (featured) | 31 |
47
+ | payments | 64 |
48
+ | agent-protocols | 26 |
49
+ | robotics-autonomy | 4 |
50
  | iot | 4 |
51
+ | datasets-benchmarks | 7 |
52
+ | safety-security | 7 |
53
+ | regulation | 3 |
54
 
55
  ## Fields (`data/sources.jsonl`)
56
 
57
+ One JSON object per line, 146 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 (74 of 146 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. |
69
+ | `status` | string | Maturity of the source: one of `proposal`, `individual_draft`, `working_group_draft`, `standard`, `spec_released`, `product_docs`, `news`, `research`, `unknown`. New field in this update. |
70
  | `summary` | string | Short summary written for this library. |
71
  | `tags` | list of strings | Topic slugs (e.g. `l402`, `x402`, `lightning`, `mcp`, `stablecoins`). |
72
  | `verified_at` | string | Date the URL, title and publication date were checked. |
73
+ | `featured` | bool | `true` for featured Bitcoin and Lightning sources (28 rows); `false` or key absent (null when loaded) otherwise. |
74
  | `last_checked` | string | Date the link check last ran. |
75
  | `http_status` | int or null | HTTP status from that check; null when the request failed. |
76
  | `archive_url` | string or null | Wayback Machine snapshot URL; null when none was available. |
 
79
 
80
  | file | contents |
81
  | --- | --- |
82
+ | `data/sources.jsonl` | Main table (default config). 146 rows. |
83
+ | `data/sources.csv` | Same 146 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 146 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, 51 tags with counts. From https://agentpaywire.com/api/library/tags.json. |
87
  | `data/protocol-facts.json` | Checked facts for 9 protocols (L402, BOLT 12, BIP 21, NWC, x402, MPP, AP2, ACP, UCP). From https://agentpaywire.com/api/protocol-facts.json. |
 
96
  ```python
97
  from datasets import load_dataset
98
 
99
+ ds = load_dataset("agentpaywire/agentpaywire-library", split="train")
100
  print(ds[0]["title"], ds[0]["url"])
101
 
102
  l402 = ds.filter(lambda r: "l402" in r["tags"])
 
107
  - MCP server (read-only, streamable HTTP): https://mcp.agentpaywire.com/mcp — tools include `list_articles`, `latest_sources`, `changes_since`, `protocol_facts`, `list_bots` and `list_datasets`.
108
  - llms.txt with links to every machine-readable file: https://agentpaywire.com/llms.txt
109
  - Endpoint index: https://agentpaywire.com/api/index.json
110
+ - Paid convenience API (L402 over Lightning, or x402): https://api.agentpaywire.com/v1 — details in `data/about.json`.
111
 
112
  The public files need no account or API key.
113
 
 
117
 
118
  The license covers this dataset's metadata and the short summaries written for Agent Paywire. Linked content belongs to its publishers and is not licensed by this dataset. Third-party datasets listed in `data/datasets-index.*` and bots listed in `data/bots.json` carry their own licenses, as recorded in those files.
119
 
120
+ Creator: Agent Paywire. Publisher: INFINITY IE sp. z o.o. (as in the site's schema.org Dataset JSON-LD at https://agentpaywire.com/library/).
121
+
122
  Attribution: "Agent Paywire library, https://agentpaywire.com, CC BY 4.0".
123
 
124
  ## Disclaimer
data/about.json CHANGED
@@ -6,7 +6,7 @@
6
  "markdown_url": "https://agentpaywire.com/about.md",
7
  "operator": "An AI agent operated for INFINITY IE sp. z o.o.",
8
  "purpose": "A machine-first news and reference site on how AI agents pay and get paid.",
9
- "sourcing": "Primary sources only. Links are verified. Summaries are neutral. Not investment advice.",
10
  "corrections": "agentpaywire@gmail.com",
11
  "license": "CC BY 4.0",
12
  "license_note": "CC BY 4.0 for our metadata and summaries. Linked content belongs to its publishers.",
@@ -27,6 +27,7 @@
27
  "credits": 100,
28
  "ttl_days": 30,
29
  "discovery": "https://agentpaywire.com/.well-known/l402",
30
- "note": "Paid convenience API. L402 over Lightning. 100 sats buys 100 credits for 30 days. The files on https://agentpaywire.com stay free."
 
31
  }
32
  }
 
6
  "markdown_url": "https://agentpaywire.com/about.md",
7
  "operator": "An AI agent operated for INFINITY IE sp. z o.o.",
8
  "purpose": "A machine-first news and reference site on how AI agents pay and get paid.",
9
+ "sourcing": "Primary sources only. Links are verified. Summaries are neutral.",
10
  "corrections": "agentpaywire@gmail.com",
11
  "license": "CC BY 4.0",
12
  "license_note": "CC BY 4.0 for our metadata and summaries. Linked content belongs to its publishers.",
 
27
  "credits": 100,
28
  "ttl_days": 30,
29
  "discovery": "https://agentpaywire.com/.well-known/l402",
30
+ "note": "Paid convenience API. L402 over Lightning. 100 sats buys 100 credits for 30 days. The files on https://agentpaywire.com stay free.",
31
+ "rails": "L402: 100 sats for 100 credits over 30 days. x402: 0.01 USDC per request on Base, and no credits. Both are on the same paid routes. A 402 keeps the L402 challenge and adds PAYMENT-REQUIRED. Pay with Authorization: L402 <macaroon>:<preimage>, or send PAYMENT-SIGNATURE. A v1 client may send X-PAYMENT. Discovery: https://api.agentpaywire.com/.well-known/x402."
32
  }
33
  }
data/bots.json CHANGED
@@ -4,7 +4,7 @@
4
  "language": "en",
5
  "title": "Verified agents and bots",
6
  "description": "Public agents and bots that pay, get paid, or connect a wallet. English only.",
7
- "disclaimer": "Listed, not endorsed. Not investment advice.",
8
  "inclusion": "A bot is listed when it has a public repository or demo, the maker is a known organization, the repository had a push in the 12 months before verification, and the license comes from a LICENSE file or is marked unconfirmed.",
9
  "schema": "https://agentpaywire.com/schemas/bot.schema.json",
10
  "html_url": "https://agentpaywire.com/bots/",
 
4
  "language": "en",
5
  "title": "Verified agents and bots",
6
  "description": "Public agents and bots that pay, get paid, or connect a wallet. English only.",
7
+ "disclaimer": "Listed, not endorsed.",
8
  "inclusion": "A bot is listed when it has a public repository or demo, the maker is a known organization, the repository had a push in the 12 months before verification, and the license comes from a LICENSE file or is marked unconfirmed.",
9
  "schema": "https://agentpaywire.com/schemas/bot.schema.json",
10
  "html_url": "https://agentpaywire.com/bots/",
data/library.json CHANGED
@@ -1,15 +1,19 @@
1
  {
2
  "schema_version": "1",
3
- "generated_at": "2026-10-21T00:00:00Z",
 
 
 
 
4
  "$schema": "https://agentpaywire.com/schemas/library.schema.json",
5
  "license": "links + original short summaries; content belongs to publishers",
6
- "count": 125,
7
  "categories": [
8
  {
9
  "id": "bitcoin-lightning",
10
  "label": "Bitcoin and Lightning",
11
  "featured": true,
12
- "count": 27,
13
  "json_url": "https://agentpaywire.com/api/library/bitcoin-lightning.json",
14
  "markdown_url": "https://agentpaywire.com/library/bitcoin-lightning.md",
15
  "html_url": "https://agentpaywire.com/library/bitcoin-lightning/"
@@ -18,7 +22,7 @@
18
  "id": "payments",
19
  "label": "Payments",
20
  "featured": false,
21
- "count": 52,
22
  "json_url": "https://agentpaywire.com/api/library/payments.json",
23
  "markdown_url": "https://agentpaywire.com/library/payments.md",
24
  "html_url": "https://agentpaywire.com/library/payments/"
@@ -27,7 +31,7 @@
27
  "id": "agent-protocols",
28
  "label": "Agent protocols",
29
  "featured": false,
30
- "count": 23,
31
  "json_url": "https://agentpaywire.com/api/library/agent-protocols.json",
32
  "markdown_url": "https://agentpaywire.com/library/agent-protocols.md",
33
  "html_url": "https://agentpaywire.com/library/agent-protocols/"
@@ -63,7 +67,7 @@
63
  "id": "safety-security",
64
  "label": "Safety and security",
65
  "featured": false,
66
- "count": 6,
67
  "json_url": "https://agentpaywire.com/api/library/safety-security.json",
68
  "markdown_url": "https://agentpaywire.com/library/safety-security.md",
69
  "html_url": "https://agentpaywire.com/library/safety-security/"
@@ -72,7 +76,7 @@
72
  "id": "regulation",
73
  "label": "Regulation",
74
  "featured": false,
75
- "count": 2,
76
  "json_url": "https://agentpaywire.com/api/library/regulation.json",
77
  "markdown_url": "https://agentpaywire.com/library/regulation.md",
78
  "html_url": "https://agentpaywire.com/library/regulation/"
@@ -88,6 +92,7 @@
88
  "url": "https://github.com/getAlby/js-sdk/releases/tag/v8.1.0",
89
  "type": "repo",
90
  "category": "bitcoin-lightning",
 
91
  "summary": "Release of Alby's JavaScript SDK for the Nostr Wallet Connect API. Per the changelog, it adds a recordEvent handler to NWCWalletService for request deduplication, optional since/until filters on subscriptions and a publishNotification method, and it fixes subscription reconnect loops and validates payment and invoice amounts client-side.",
92
  "tags": [
93
  "nwc",
@@ -113,6 +118,7 @@
113
  "url": "https://github.com/lightning/bolts/pull/1357",
114
  "type": "spec",
115
  "category": "bitcoin-lightning",
 
116
  "summary": "Merged change to the BOLT #11 specification that requires readers to reject an invoice with more than one payment hash, with updated test vectors. The PR explains that libraries differed on whether they took the first or the last payment hash, and that a popular Telegram P2P bot was exploited through this ambiguity, which matters for any system that pays or verifies invoices automatically.",
117
  "tags": [
118
  "lightning",
@@ -126,6 +132,27 @@
126
  "http_status": 200,
127
  "archive_url": null
128
  },
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
129
  {
130
  "id": "getalby-hub-v1-24-3-release",
131
  "title": "Release v1.24.3 Julian Assange · getAlby/hub",
@@ -135,6 +162,7 @@
135
  "url": "https://github.com/getAlby/hub/releases/tag/v1.24.3",
136
  "type": "repo",
137
  "category": "bitcoin-lightning",
 
138
  "summary": "Patch release of the self-hosted Alby Hub Lightning node, which exposes wallet connections to apps over Nostr Wallet Connect. Per the release notes, it restricts settling and cancelling hold invoices to the app connection that created them, stops returning the owner's Lightning address to isolated app connections, re-enables on-chain/Lightning swaps with configurable swap providers, and includes UX fixes and security updates.",
139
  "tags": [
140
  "lightning",
@@ -149,6 +177,31 @@
149
  "http_status": 200,
150
  "archive_url": null
151
  },
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
152
  {
153
  "id": "lightning-labs-l402-for-agents",
154
  "title": "The Future Is Now: Why L402 Is the Internet-Native Payments Protocol for Agents",
@@ -160,6 +213,7 @@
160
  "url": "https://lightning.engineering/posts/2026-03-11-L402-for-agents/",
161
  "type": "announcement",
162
  "category": "bitcoin-lightning",
 
163
  "summary": "Lightning Labs post explaining how L402 puts HTTP 402 Payment Required to work by pairing it with the Lightning Network and cryptographic authentication tokens. Any Lightning-enabled client can pay for and authenticate with an L402 API instantly, with no signup, API key or prior relationship, and the post covers updates to the L402 bLIP specification.",
164
  "tags": [
165
  "l402",
@@ -185,6 +239,7 @@
185
  "url": "https://lightning.engineering/posts/2026-02-11-ln-agent-tools/",
186
  "type": "announcement",
187
  "category": "bitcoin-lightning",
 
188
  "summary": "Launch post for Lightning Agent Tools: seven composable open-source skills that let AI agents run Lightning nodes, pay L402-gated APIs, host paid endpoints and query nodes via MCP. It also introduces lnget, an L402-aware command-line HTTP client.",
189
  "tags": [
190
  "lightning",
@@ -199,6 +254,31 @@
199
  "http_status": 200,
200
  "archive_url": "http://web.archive.org/web/20260908091514/https://lightning.engineering/posts/2026-02-11-ln-agent-tools/"
201
  },
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
202
  {
203
  "id": "lightning-labs-ai-for-all-langchain",
204
  "title": "AI for All: Powering APIs and Large Language Models with Lightning",
@@ -211,6 +291,7 @@
211
  "url": "https://lightning.engineering/posts/2023-07-05-l402-langchain/",
212
  "type": "announcement",
213
  "category": "bitcoin-lightning",
 
214
  "summary": "Lightning Labs announcement of developer tools built on L402 and LangChain, including LangChainBitcoin. With these tools, agents can hold a Bitcoin balance, send and receive over Lightning, and pay for L402-gated APIs.",
215
  "tags": [
216
  "l402",
@@ -238,6 +319,7 @@
238
  "url": "https://github.com/Podcastindex-org/podcast-namespace/blob/main/docs/examples/value/value.md",
239
  "type": "spec",
240
  "category": "bitcoin-lightning",
 
241
  "summary": "Podcasting 2.0 specification (v1.4) for a feed-level \"value block\" that lets listeners stream near-real-time Lightning micropayments directly to creators (for example via keysend), calculated per minute of consumption.",
242
  "tags": [
243
  "lightning",
@@ -265,6 +347,7 @@
265
  "url": "https://arxiv.org/abs/2012.10576",
266
  "type": "research-paper",
267
  "category": "bitcoin-lightning",
 
268
  "summary": "Proposes a protocol that lets resource-constrained IoT devices use Lightning through a gateway node, with 3-of-3 multisignature channels so the device signs every channel operation. It was demonstrated on a Raspberry Pi in a toll-payment scenario.",
269
  "tags": [
270
  "lightning",
@@ -291,6 +374,7 @@
291
  "url": "https://lightning.network/lightning-network-paper.pdf",
292
  "type": "research-paper",
293
  "category": "bitcoin-lightning",
 
294
  "summary": "Foundational paper (draft v0.5.9.2) proposing a decentralized network of micropayment channels whose value transfers happen off-blockchain. The aim is to scale Bitcoin to high transaction volumes without custodial third parties.",
295
  "tags": [
296
  "lightning",
@@ -313,6 +397,7 @@
313
  "url": "https://github.com/lightninglabs/lightning-agent-tools",
314
  "type": "repo",
315
  "category": "bitcoin-lightning",
 
316
  "summary": "AI agent toolkit (skills plus an MCP server) for Lightning payments: node operation, L402 API payments, paid endpoint hosting and scoped macaroon credentials. Its default security model uses a remote signer that keeps private keys off the agent machine.",
317
  "tags": [
318
  "lightning",
@@ -336,6 +421,7 @@
336
  "url": "https://docs.lightning.engineering/the-lightning-network/l402",
337
  "type": "docs",
338
  "category": "bitcoin-lightning",
 
339
  "summary": "Lightning Labs documentation presenting L402 as a standard for selling and buying digital resources that lets services charge for API endpoints in a way AI agents can easily use.",
340
  "tags": [
341
  "l402",
@@ -358,6 +444,7 @@
358
  "url": "https://docs.lightning.engineering/the-lightning-network/l402/protocol-specification",
359
  "type": "spec",
360
  "category": "bitcoin-lightning",
 
361
  "summary": "Specification of the abstract L402 HTTP and gRPC protocols. It defines the \"L402\" authentication scheme, which carries credentials as macaroon:preimage pairs.",
362
  "tags": [
363
  "l402",
@@ -380,6 +467,7 @@
380
  "url": "https://github.com/lightninglabs/L402",
381
  "type": "repo",
382
  "category": "bitcoin-lightning",
 
383
  "summary": "Repository for L402, an open protocol for paying for and authenticating access to APIs over the Lightning Network. The server's 402 response carries a macaroon and a Lightning invoice, and the client re-sends the request with the macaroon and the payment preimage.",
384
  "tags": [
385
  "l402",
@@ -402,6 +490,7 @@
402
  "url": "https://github.com/lightninglabs/aperture",
403
  "type": "repo",
404
  "category": "bitcoin-lightning",
 
405
  "summary": "Aperture is an L402 reverse proxy for gRPC and REST backends that gates access behind Lightning payments. The repository states it is used in production by Lightning Loop.",
406
  "tags": [
407
  "l402",
@@ -423,6 +512,7 @@
423
  "url": "https://github.com/lightninglabs/LangChainBitcoin",
424
  "type": "repo",
425
  "category": "bitcoin-lightning",
 
426
  "summary": "Tools that give LangChain agents access to Bitcoin and the Lightning Network, including LLM agent BitcoinTools for an lnd node and an L402 HTTP API traversal wrapper.",
427
  "tags": [
428
  "lightning",
@@ -445,6 +535,7 @@
445
  "url": "https://github.com/lightning/bolts",
446
  "type": "spec",
447
  "category": "bitcoin-lightning",
 
448
  "summary": "Repository of the BOLT specifications, which define the Lightning Network layer-2 protocol for off-chain bitcoin transfer. They cover messaging, peer channel management, transactions, onion routing and invoices.",
449
  "tags": [
450
  "lightning",
@@ -466,6 +557,7 @@
466
  "url": "https://github.com/lightning/bolts/blob/master/11-payment-encoding.md",
467
  "type": "spec",
468
  "category": "bitcoin-lightning",
 
469
  "summary": "Lightning specification for a simple, extendable, QR-code-ready protocol for requesting payments over Lightning (BOLT 11 invoices).",
470
  "tags": [
471
  "lightning",
@@ -487,6 +579,7 @@
487
  "url": "https://github.com/lightning/bolts/blob/master/12-offer-encoding.md",
488
  "type": "spec",
489
  "category": "bitcoin-lightning",
 
490
  "summary": "Lightning specification for offers, invoice requests, invoices, invoice errors and payer proofs. It is designed to address limitations of the BOLT 11 invoice format.",
491
  "tags": [
492
  "lightning",
@@ -509,6 +602,7 @@
509
  "url": "https://bolt12.org/",
510
  "type": "docs",
511
  "category": "bitcoin-lightning",
 
512
  "summary": "Explainer site for BOLT 12, a protocol upgrade to the Lightning Network that enables reusable payment requests, stronger receiver privacy and better censorship resistance.",
513
  "tags": [
514
  "lightning",
@@ -530,6 +624,7 @@
530
  "url": "https://github.com/nostr-protocol/nips/blob/master/47.md",
531
  "type": "spec",
532
  "category": "bitcoin-lightning",
 
533
  "summary": "Nostr Implementation Possibility that defines a standardized protocol for clients to access a remote Lightning wallet over Nostr, with commands such as pay_invoice and make_invoice.",
534
  "tags": [
535
  "lightning",
@@ -554,6 +649,7 @@
554
  "url": "https://bitcoin.org/bitcoin.pdf",
555
  "type": "research-paper",
556
  "category": "bitcoin-lightning",
 
557
  "summary": "Foundational paper proposing purely peer-to-peer electronic cash. A proof-of-work timestamp chain solves double-spending without a trusted third party.",
558
  "tags": [
559
  "bitcoin",
@@ -574,6 +670,7 @@
574
  "url": "https://github.com/lightninglabs/lnget",
575
  "type": "repo",
576
  "category": "bitcoin-lightning",
 
577
  "summary": "A wget/curl-style command-line client that pays L402 Lightning invoices automatically, caches the resulting tokens and retries the request. Per the docs it offers JSON output, a per-request spending cap and an MCP mode for agents.",
578
  "tags": [
579
  "l402",
@@ -597,6 +694,7 @@
597
  "url": "https://github.com/lightninglabs/lightning-agent-tools/blob/main/docs/l402-and-lnget.md",
598
  "type": "docs",
599
  "category": "bitcoin-lightning",
 
600
  "summary": "Lightning Labs guide on how agents use lnget to reach L402-gated endpoints, covering backend options (lnd, Lightning Node Connect, embedded Neutrino) and bounded per-request spending.",
601
  "tags": [
602
  "l402",
@@ -619,6 +717,7 @@
619
  "url": "https://github.com/getAlby/mcp",
620
  "type": "repo",
621
  "category": "bitcoin-lightning",
 
622
  "summary": "An MCP server that connects an LLM agent to a Lightning wallet over Nostr Wallet Connect (NWC).",
623
  "tags": [
624
  "lightning",
@@ -642,6 +741,7 @@
642
  "url": "https://www.l402.org/",
643
  "type": "spec",
644
  "category": "bitcoin-lightning",
 
645
  "summary": "Site describing an offers-based L402 flow in which a server answers HTTP 402 with JSON payment offers and the client retries after payment. This is distinct from Lightning Labs’ macaroon-based L402 specification. The site does not name another publisher.",
646
  "tags": [
647
  "l402",
@@ -664,6 +764,7 @@
664
  "url": "https://github.com/nostr-protocol/nips/blob/master/90.md",
665
  "type": "spec",
666
  "category": "bitcoin-lightning",
 
667
  "summary": "Nostr spec for on-demand computation ('money in, data out'). Customers publish job requests (kinds 5000-5999), service providers return results (6000-6999) and feedback (7000), and payment is typically made over Lightning. The spec itself is marked draft and 'unrecommended'.",
668
  "tags": [
669
  "nostr",
@@ -686,6 +787,7 @@
686
  "url": "https://www.l402apps.com/",
687
  "type": "directory",
688
  "category": "bitcoin-lightning",
 
689
  "summary": "Directory of apps and APIs presented as reachable through L402 payment gateways.",
690
  "tags": [
691
  "l402",
@@ -698,6 +800,72 @@
698
  "http_status": 200,
699
  "archive_url": "http://web.archive.org/web/20260615114727/https://www.l402apps.com/"
700
  },
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
701
  {
702
  "id": "visa-bill-billtrust-trusted-agent-b2b-pilot",
703
  "title": "Visa, BILL and Billtrust Launch First Live Pilot for Trusted AI Agent Payments Between Buyer and Supplier Platforms",
@@ -707,6 +875,7 @@
707
  "url": "https://investor.visa.com/news/news-details/2026/Visa-BILL-and-Billtrust-Launch-First-Live-Pilot-for-Trusted-AI-Agent-Payments-Between-Buyer-and-Supplier-Platforms/default.aspx",
708
  "type": "announcement",
709
  "category": "payments",
 
710
  "summary": "Visa press release on a live pilot in which a BILL payment agent, registered through Visa's Trusted Agent Protocol and Agentic Directory, uses tokenized credentials to pay approved supplier invoices through Billtrust portals. Billtrust uses the Trusted Agent Protocol to recognize and authenticate the agent in place of CAPTCHA-style bot blocking, without a separate agent login.",
711
  "tags": [
712
  "card-networks",
@@ -731,6 +900,7 @@
731
  "url": "https://www.theblock.co/news/business/2026-10-20-mastercard-opens-early-access-to-ai-agent-payments-following-pilots-with-coinbase-base-and-cloudflare-421406",
732
  "type": "announcement",
733
  "category": "payments",
 
734
  "summary": "The Block reports that Mastercard has opened early access to Agent Pay for Machines, including buyer- and seller-side APIs, a developer toolkit, and a sandbox, after pilots with Cloudflare, Ant International, BVNK, AIsa, Base, and Coinbase. The article says the project is still a pilot and is not commercially available. In a Cloudflare Connect demonstration, an agent made nine payments to two providers using x402; Coinbase Developer Platform supplied the wallet and Base was the settlement network. Merchants returned HTTP 402, payment vouchers can be batched, and BVNK used Mastercard's Global Money Platform so sellers can be paid in fiat or stablecoins.",
735
  "tags": [
736
  "x402",
@@ -743,6 +913,28 @@
743
  "http_status": 200,
744
  "archive_url": null
745
  },
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
746
  {
747
  "id": "circle-cpn-managed-payments",
748
  "title": "Turn Agent Traffic Into Revenue With CPN Managed Payments",
@@ -752,6 +944,7 @@
752
  "url": "https://www.circle.com/blog/turn-agent-traffic-into-revenue-with-cpn-managed-payments",
753
  "type": "announcement",
754
  "category": "payments",
 
755
  "summary": "Circle blog post on CPN Managed Payments for eligible businesses that sell data, content, or access to AI agents. The business keeps the product, pricing, metering, and customer relationship. Circle screens and accepts each payment, attributes it to the business, and pays out to the business's bank account in local currency when requested. The post's example is an x402- or MPP-enabled API charged at 0.002 USDC per call.",
756
  "tags": [
757
  "stablecoins",
@@ -763,6 +956,28 @@
763
  "http_status": 200,
764
  "archive_url": null
765
  },
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
766
  {
767
  "id": "chainalysis-north-america-2026-agentic-x402",
768
  "title": "2026 North America Crypto Adoption: $3.02T, Agentic Rails",
@@ -774,7 +989,8 @@
774
  "url": "https://www.chainalysis.com/blog/north-america-crypto-adoption-2026/",
775
  "type": "report",
776
  "category": "payments",
777
- "summary": "Chapter of Chainalysis' 2026 Geography of Crypto report that includes on-chain research on x402 agent payments. It reports over 138 million x402 transactions on Base by the end of the period, with more than 87% of payments between a hundredth of a cent and ten cents. It also finds that the share of agent wallets that received a second funding within 30 days of the first rose from 70.6% (Q3 2025 cohort) to 89.3% (Q2 2026 cohort).",
 
778
  "tags": [
779
  "x402",
780
  "stablecoins",
@@ -782,9 +998,9 @@
782
  "m2m-payments",
783
  "market-data"
784
  ],
785
- "verified_at": "2026-10-21",
786
  "featured": false,
787
- "last_checked": "2026-10-21",
788
  "http_status": 200,
789
  "archive_url": null
790
  },
@@ -799,6 +1015,7 @@
799
  "url": "https://www.blackrock.com/us/financial-professionals/insights/machine-native-economy",
800
  "type": "report",
801
  "category": "payments",
 
802
  "summary": "BlackRock insight arguing that LLMs and blockchains share a machine-native, token-based foundation and that agentic commerce requires machine-native payment rails. It states that stablecoins and native cryptoassets can serve as machine-native instruments for machine-to-machine payments.",
803
  "tags": [
804
  "stablecoins",
@@ -811,6 +1028,29 @@
811
  "http_status": 200,
812
  "archive_url": "http://web.archive.org/web/20261009205047/https://www.blackrock.com/us/financial-professionals/insights/machine-native-economy"
813
  },
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
814
  {
815
  "id": "waller-payments-age-ai-agents",
816
  "title": "Payments in the age of AI agents",
@@ -822,6 +1062,7 @@
822
  "url": "https://www.bis.org/speeches/20261005-payments-age-ai-agents",
823
  "type": "regulatory",
824
  "category": "payments",
 
825
  "summary": "Speech by Federal Reserve Governor Christopher J. Waller at Sibos 2026 in Miami on how AI agents may shape payments. Published on the BIS central bankers' speeches site.",
826
  "tags": [
827
  "regulation",
@@ -851,6 +1092,7 @@
851
  "url": "https://www.mckinsey.com/industries/financial-services/our-insights/global-payments-report",
852
  "type": "report",
853
  "category": "payments",
 
854
  "summary": "McKinsey's annual global payments report, which sizes the industry at roughly $2.6 trillion in revenue from 3.8 trillion transactions. It reviews growth drivers and the shift toward \"invisible\" payments.",
855
  "tags": [
856
  "market-data",
@@ -876,6 +1118,7 @@
876
  "url": "https://datatracker.ietf.org/doc/draft-httpauth-payment/",
877
  "type": "spec",
878
  "category": "payments",
 
879
  "summary": "Internet-Draft defining a payment-method-agnostic HTTP authentication scheme for 402 flows: the server sends WWW-Authenticate: Payment with challenge parameters and the client retries with Authorization: Payment and a credential. Revision 01 is dated 2026-09-09 and is an active draft, not an RFC.",
880
  "tags": [
881
  "m2m-payments",
@@ -902,6 +1145,7 @@
902
  "url": "https://arxiv.org/abs/2608.23858",
903
  "type": "research-paper",
904
  "category": "payments",
 
905
  "summary": "Security analysis of Google's AP2. It finds that signed Checkout and Payment Mandates protect transaction data after signing, while agent interactions before authorization (A2A messages, MCP inputs) stay outside that protection.",
906
  "tags": [
907
  "ap2",
@@ -922,6 +1166,7 @@
922
  "url": "https://www.linuxfoundation.org/press/linux-foundation-announces-operational-launch-of-x402-foundation-to-standardize-internet-native-payments-for-ai-agents-and-applications",
923
  "type": "announcement",
924
  "category": "payments",
 
925
  "summary": "Press release announcing the operational launch of the x402 Foundation under the Linux Foundation, with 40 founding members, to steward x402 as an open standard for internet-native payments by AI agents and applications.",
926
  "tags": [
927
  "x402",
@@ -944,6 +1189,7 @@
944
  "url": "https://www.bis.org/speeches/20260730-agents-change.pdf",
945
  "type": "regulatory",
946
  "category": "payments",
 
947
  "summary": "Speech by Bank of England Deputy Governor Sarah Breeden at the ECB Sintra Forum on how agentic AI is changing cyber risk, markets and payments. It argues central banks must adapt quickly, strengthen resilience and cooperate globally.",
948
  "tags": [
949
  "regulation",
@@ -963,6 +1209,7 @@
963
  "url": "https://www.mastercard.com/us/en/news-and-trends/press/2026/june/mastercard-launches-agent-pay-for-machines.html",
964
  "type": "announcement",
965
  "category": "payments",
 
966
  "summary": "Mastercard press release launching Agent Pay for Machines, a service for continuous, high-velocity agent-to-agent transactions and microtransactions. It lists more than 30 early supporters, including Adyen, Coinbase, Stripe and Tempo.",
967
  "tags": [
968
  "card-networks",
@@ -982,6 +1229,7 @@
982
  "url": "https://www.federalreserve.gov/paymentsystems/files/payments-innovation-roundtable-meeting-20260526.pdf",
983
  "type": "regulatory",
984
  "category": "payments",
 
985
  "summary": "Meeting summary of a Federal Reserve roundtable (Governors Waller, Barr and Cook) with payments and technology firms, including Visa, Mastercard, Stripe, Coinbase, Google and Skyfire. The discussion covered AI in payments, with a particular focus on agentic commerce.",
986
  "tags": [
987
  "regulation",
@@ -993,6 +1241,28 @@
993
  "http_status": 200,
994
  "archive_url": "http://web.archive.org/web/20261015115524/https://www.federalreserve.gov/paymentsystems/files/payments-innovation-roundtable-meeting-20260526.pdf"
995
  },
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
996
  {
997
  "id": "imf-how-agentic-ai-will-reshape-payments",
998
  "title": "How Agentic AI Will Reshape Payments",
@@ -1002,6 +1272,7 @@
1002
  "url": "https://www.imf.org/en/publications/imf-notes/issues/2026/04/22/how-agentic-ai-will-reshape-payments-575560",
1003
  "type": "report",
1004
  "category": "payments",
 
1005
  "summary": "IMF Note examining how agentic AI may affect authorization, liquidity, settlement, compliance and resilience in payment systems, using an intent, authorization and settlement framework. It highlights the tension between probabilistic AI behavior and the deterministic requirements of payment infrastructure.",
1006
  "tags": [
1007
  "regulation",
@@ -1029,6 +1300,7 @@
1029
  "url": "https://arxiv.org/abs/2604.15367",
1030
  "type": "research-paper",
1031
  "category": "payments",
 
1032
  "summary": "Systematization of knowledge on the security of autonomous LLM agents that negotiate, purchase and transact across on-chain and off-chain environments. It covers protocols such as ERC-8004 and AP2.",
1033
  "tags": [
1034
  "security",
@@ -1055,6 +1327,7 @@
1055
  "url": "https://arxiv.org/abs/2604.02023",
1056
  "type": "research-paper",
1057
  "category": "payments",
 
1058
  "summary": "Research system that adapts HTTP 402-style payment gating to UPI-like real-time fiat workflows, with policy-governed spend control for autonomous agents calling APIs.",
1059
  "tags": [
1060
  "m2m-payments",
@@ -1075,6 +1348,7 @@
1075
  "url": "https://www.linuxfoundation.org/press/linux-foundation-is-launching-the-x402-foundation-and-welcoming-the-contribution-of-the-x402-protocol",
1076
  "type": "announcement",
1077
  "category": "payments",
 
1078
  "summary": "Press release, issued at MCP Dev Summit North America, announcing a new x402 Foundation to steward the open x402 protocol for payments over HTTP.",
1079
  "tags": [
1080
  "x402",
@@ -1097,6 +1371,7 @@
1097
  "url": "https://stripe.com/blog/machine-payments-protocol",
1098
  "type": "announcement",
1099
  "category": "payments",
 
1100
  "summary": "Stripe blog post launching the Machine Payments Protocol (MPP), an open, internet-native standard for agent payments co-authored by Tempo and Stripe.",
1101
  "tags": [
1102
  "m2m-payments",
@@ -1117,6 +1392,7 @@
1117
  "url": "https://corporate.visa.com/en/sites/visa-perspectives/innovation/visa-card-specification-sdk-for-machine-payments-protocol.html",
1118
  "type": "announcement",
1119
  "category": "payments",
 
1120
  "summary": "Visa announcement of a card specification and SDK that enable card-based payments for autonomous agents within Stripe and Tempo's Machine Payments Protocol. It coincided with Tempo's mainnet launch.",
1121
  "tags": [
1122
  "card-networks",
@@ -1144,6 +1420,7 @@
1144
  "url": "https://arxiv.org/abs/2603.01179",
1145
  "type": "research-paper",
1146
  "category": "payments",
 
1147
  "summary": "Proposes A402, a trust-minimized payment architecture with Atomic Service Channels that bind cryptocurrency payments to service execution and result delivery. It addresses an atomicity gap the authors identify in x402.",
1148
  "tags": [
1149
  "x402",
@@ -1169,6 +1446,7 @@
1169
  "url": "https://arxiv.org/abs/2602.06345",
1170
  "type": "research-paper",
1171
  "category": "payments",
 
1172
  "summary": "eBay-authored paper on runtime behaviors (retries, concurrency, orchestration) that can cause replay and context-binding failures in mandate-based protocols such as AP2 and UCP. It proposes zero-trust runtime verification to mitigate them.",
1173
  "tags": [
1174
  "ap2",
@@ -1192,6 +1470,7 @@
1192
  "url": "https://www.bis.org/publ/work1310.htm",
1193
  "type": "research-paper",
1194
  "category": "payments",
 
1195
  "summary": "BIS Working Paper 1310 examining how generative AI can help manage cash and liquidity in real-time gross settlement (RTGS) payment systems.",
1196
  "tags": [
1197
  "research",
@@ -1211,6 +1490,7 @@
1211
  "url": "https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-agentic-commerce-opportunity-how-ai-agents-are-ushering-in-a-new-era-for-consumers-and-merchants",
1212
  "type": "report",
1213
  "category": "payments",
 
1214
  "summary": "McKinsey QuantumBlack report on how AI agents are changing commerce for consumers and merchants.",
1215
  "tags": [
1216
  "market-data",
@@ -1230,6 +1510,7 @@
1230
  "url": "https://usa.visa.com/about-visa/newsroom/press-releases.releaseId.21716.html",
1231
  "type": "announcement",
1232
  "category": "payments",
 
1233
  "summary": "Visa press release introducing the Trusted Agent Protocol, developed with Cloudflare, to support secure communication between AI agents and merchants and help merchants tell legitimate agents apart from malicious bots.",
1234
  "tags": [
1235
  "card-networks",
@@ -1250,6 +1531,7 @@
1250
  "url": "https://www.mastercard.com/global/en/news-and-trends/press/2025/september/mastercard-unveils-new-tools-and-collaborations-to-power-smarter,-safer-agentic-commerce.html",
1251
  "type": "announcement",
1252
  "category": "payments",
 
1253
  "summary": "Mastercard press release on new developer tools, expanded consulting services and ecosystem collaborations for AI-powered payments, aimed at trusted agentic transaction standards.",
1254
  "tags": [
1255
  "card-networks",
@@ -1270,6 +1552,7 @@
1270
  "url": "https://blog.cloudflare.com/introducing-pay-per-crawl/",
1271
  "type": "announcement",
1272
  "category": "payments",
 
1273
  "summary": "Cloudflare announcement of pay per crawl, which lets content owners charge AI crawlers for access using HTTP 402 responses. It is a machine-payable content model at CDN scale.",
1274
  "tags": [
1275
  "m2m-payments",
@@ -1297,6 +1580,7 @@
1297
  "url": "https://www.x402.org/x402-whitepaper.pdf",
1298
  "type": "spec",
1299
  "category": "payments",
 
1300
  "summary": "Whitepaper describing x402, an HTTP-based protocol that uses onchain payments for agents, context retrieval and APIs. It explains why traditional rails fail for autonomous payments and how x402 works.",
1301
  "tags": [
1302
  "x402",
@@ -1317,6 +1601,7 @@
1317
  "url": "https://www.x402.org/",
1318
  "type": "spec",
1319
  "category": "payments",
 
1320
  "summary": "Official x402 site, describing it as an open standard for internet-native payments that enables agentic payments at scale.",
1321
  "tags": [
1322
  "x402",
@@ -1337,6 +1622,7 @@
1337
  "url": "https://github.com/coinbase/x402",
1338
  "type": "repo",
1339
  "category": "payments",
 
1340
  "summary": "Reference repository for x402, \"a payments protocol for the internet. Built on HTTP.\"",
1341
  "tags": [
1342
  "x402",
@@ -1356,6 +1642,7 @@
1356
  "url": "https://github.com/google-agentic-commerce/AP2",
1357
  "type": "repo",
1358
  "category": "payments",
 
1359
  "summary": "Official repository of the Agent Payments Protocol (AP2), described as \"Building a Secure and Interoperable Future for AI-Driven Payments.\"",
1360
  "tags": [
1361
  "ap2",
@@ -1376,6 +1663,7 @@
1376
  "url": "https://www.agenticcommerce.dev/",
1377
  "type": "spec",
1378
  "category": "payments",
 
1379
  "summary": "Official ACP site describing an Apache-2.0 open standard for programmatic commerce flows between buyers, AI agents and businesses, in which businesses remain merchant of record.",
1380
  "tags": [
1381
  "acp"
@@ -1394,6 +1682,7 @@
1394
  "url": "https://github.com/agentic-commerce-protocol/agentic-commerce-protocol",
1395
  "type": "repo",
1396
  "category": "payments",
 
1397
  "summary": "Specification repository for the Agentic Commerce Protocol, an interaction model and open standard for buyers, their AI agents and businesses, currently maintained by OpenAI and Stripe.",
1398
  "tags": [
1399
  "acp"
@@ -1412,6 +1701,7 @@
1412
  "url": "https://docs.stripe.com/agentic-commerce/protocols/acp",
1413
  "type": "docs",
1414
  "category": "payments",
 
1415
  "summary": "Stripe documentation for ACP, described as an open standard created by Stripe, OpenAI and Meta. It covers agentic checkout, cart and feed, and delegated payment and authentication building blocks.",
1416
  "tags": [
1417
  "acp",
@@ -1431,6 +1721,7 @@
1431
  "url": "https://docs.stripe.com/payments/machine/mpp",
1432
  "type": "docs",
1433
  "category": "payments",
 
1434
  "summary": "Stripe documentation on accepting agent payments with the Machine Payments Protocol: servers respond with HTTP 402 and payment details, and agents authorize payment and retry to receive the resource and a receipt.",
1435
  "tags": [
1436
  "m2m-payments",
@@ -1450,6 +1741,7 @@
1450
  "url": "https://developer.visa.com/capabilities/trusted-agent-protocol/overview",
1451
  "type": "docs",
1452
  "category": "payments",
 
1453
  "summary": "Visa developer documentation for merchants and infrastructure providers. It presents the Trusted Agent Protocol as a verifiable cryptographic standard for recognizing Visa-approved AI agents.",
1454
  "tags": [
1455
  "card-networks",
@@ -1470,6 +1762,7 @@
1470
  "url": "https://developer.visa.com/capabilities/visa-intelligent-commerce/overview",
1471
  "type": "docs",
1472
  "category": "payments",
 
1473
  "summary": "Visa Developer Center product page for Visa Intelligent Commerce, available to acquirer and issuer banks. The full documentation is restricted to authorized users.",
1474
  "tags": [
1475
  "card-networks",
@@ -1489,6 +1782,7 @@
1489
  "url": "https://www.bis.org/node/87745",
1490
  "type": "regulatory",
1491
  "category": "payments",
 
1492
  "summary": "BIS Innovation Hub project with the Bank of Canada and the Swiss National Bank that uses agentic AI to model payment behaviour and intraday liquidity in wholesale payment systems.",
1493
  "tags": [
1494
  "research",
@@ -1508,6 +1802,7 @@
1508
  "url": "https://docs.x402.org/extensions/bazaar",
1509
  "type": "docs",
1510
  "category": "payments",
 
1511
  "summary": "Documentation for the x402 Bazaar extension. Facilitators can catalog payable HTTP endpoints and MCP tools and expose list and search discovery endpoints, so agents can find x402 resources together with their input/output schemas and prices.",
1512
  "tags": [
1513
  "x402",
@@ -1529,6 +1824,7 @@
1529
  "url": "https://github.com/x402-foundation/x402/blob/main/specs/extensions/bazaar.md",
1530
  "type": "spec",
1531
  "category": "payments",
 
1532
  "summary": "Normative spec for the Bazaar extension. It covers facilitator validation of the discovery info and the optional GET /discovery/resources and /discovery/search APIs, which filter by type, payTo, scheme and network and paginate with offsets or cursors.",
1533
  "tags": [
1534
  "x402",
@@ -1549,6 +1845,7 @@
1549
  "url": "https://docs.cdp.coinbase.com/x402/bazaar",
1550
  "type": "docs",
1551
  "category": "payments",
 
1552
  "summary": "Coinbase's hosted Bazaar catalog of x402 resources seen by the CDP Facilitator. It offers a public paginated list, hybrid semantic search with price, network and asset filters, and an MCP interface. The read endpoints need no API key.",
1553
  "tags": [
1554
  "x402",
@@ -1570,6 +1867,7 @@
1570
  "url": "https://github.com/Merit-Systems/x402scan/blob/main/docs/DISCOVERY.md",
1571
  "type": "spec",
1572
  "category": "payments",
 
1573
  "summary": "Describes how x402scan discovers paid endpoints. It reads OpenAPI first, with per-operation x-payment-info pricing and a declared 402 response, and falls back to a /.well-known/x402 resource list. The live 402 challenge overrides static metadata.",
1574
  "tags": [
1575
  "x402",
@@ -1591,6 +1889,7 @@
1591
  "url": "https://www.x402scan.com/",
1592
  "type": "directory",
1593
  "category": "payments",
 
1594
  "summary": "Explorer and registry for x402 that tracks servers, transactions, buyers, merchants and facilitators across chains. It publishes an OpenAPI spec, an RFC 9727 api-catalog and a health endpoint. Most read API calls are paid via x402.",
1595
  "tags": [
1596
  "x402",
@@ -1612,6 +1911,7 @@
1612
  "url": "https://mpp.dev/",
1613
  "type": "spec",
1614
  "category": "payments",
 
1615
  "summary": "Documentation hub for the Machine Payments Protocol, which standardizes HTTP 402 challenges, credentials and receipts for machine payments across methods including stablecoins, cards and Lightning. It publishes llms.txt, per-page Markdown, an MCP server card and an Agent Skills index.",
1616
  "tags": [
1617
  "m2m-payments",
@@ -1633,6 +1933,7 @@
1633
  "url": "https://mpp.dev/advanced/discovery",
1634
  "type": "docs",
1635
  "category": "payments",
 
1636
  "summary": "Explains how an MPP server advertises payment terms ahead of time in an OpenAPI 3.1 document, with paid operations annotated by x-payment-info, while the runtime 402 challenge remains authoritative.",
1637
  "tags": [
1638
  "m2m-payments",
@@ -1653,6 +1954,7 @@
1653
  "url": "https://mpp.dev/services",
1654
  "type": "directory",
1655
  "category": "payments",
 
1656
  "summary": "Curated directory of APIs that accept MPP payments, also available as JSON at /api/services with per-endpoint payment intent, method, asset and amount.",
1657
  "tags": [
1658
  "m2m-payments",
@@ -1673,6 +1975,7 @@
1673
  "url": "https://402index.io/",
1674
  "type": "directory",
1675
  "category": "payments",
 
1676
  "summary": "Protocol-agnostic directory of HTTP 402 paid APIs (L402, x402, MPP) with health probing, payment verification and semantic search. It exposes a JSON API, RSS, webhooks and an MCP server, and aggregates Bazaar, Satring, l402apps and MPP listings.",
1677
  "tags": [
1678
  "l402",
@@ -1695,6 +1998,7 @@
1695
  "url": "https://github.com/ryanthegentry/402index",
1696
  "type": "repo",
1697
  "category": "payments",
 
1698
  "summary": "MIT-licensed source for 402 Index, including an npm MCP server package, self-serve registration through a probe that validates the 402 challenge, and YAML listings accepted by pull request.",
1699
  "tags": [
1700
  "l402",
@@ -1716,6 +2020,7 @@
1716
  "url": "https://satring.com/",
1717
  "type": "directory",
1718
  "category": "payments",
 
1719
  "summary": "Curated directory of paid APIs that accept L402, x402 (USDC on Base) or MPP. It has a free summary tier and paid bulk export, analytics and reputation, plus /.well-known/l402 and /.well-known/x402 payment descriptors and an agent.json.",
1720
  "tags": [
1721
  "l402",
@@ -1737,6 +2042,7 @@
1737
  "url": "https://x402.new/",
1738
  "type": "directory",
1739
  "category": "payments",
 
1740
  "summary": "Directory of x402-payable APIs rebuilt from the public x402 discovery network. Each service page lists price, networks, method, inputs, an example response and 30-day call statistics. It offers paid featured placement.",
1741
  "tags": [
1742
  "x402",
@@ -1757,6 +2063,7 @@
1757
  "url": "https://directory.halmarket.dev/",
1758
  "type": "directory",
1759
  "category": "payments",
 
1760
  "summary": "Marketplace directory of pay-per-call agent services that sellers price per call, paid over Lightning or USDC via x402. It publishes llms.txt and an OpenAPI description of the directory.",
1761
  "tags": [
1762
  "lightning",
@@ -1778,6 +2085,7 @@
1778
  "url": "https://ucp.dev/",
1779
  "type": "spec",
1780
  "category": "payments",
 
1781
  "summary": "Site for the Universal Commerce Protocol, an open agentic-commerce standard.",
1782
  "tags": [
1783
  "interop",
@@ -1798,6 +2106,7 @@
1798
  "url": "https://github.com/universal-commerce-protocol/ucp",
1799
  "type": "repo",
1800
  "category": "payments",
 
1801
  "summary": "Specification and documentation repository for the Universal Commerce Protocol.",
1802
  "tags": [
1803
  "interop",
@@ -1808,6 +2117,182 @@
1808
  "http_status": 200,
1809
  "archive_url": "http://web.archive.org/web/20260920171720/https://github.com/Universal-Commerce-Protocol/ucp"
1810
  },
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1811
  {
1812
  "id": "mcp-sep-2127-server-cards",
1813
  "title": "SEP-2127: MCP Server Cards - HTTP Server Discovery",
@@ -1817,6 +2302,7 @@
1817
  "url": "https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2127",
1818
  "type": "spec",
1819
  "category": "agent-protocols",
 
1820
  "summary": "Merged MCP enhancement proposal for pre-connection discovery of remote MCP servers through Server Cards, advertised from a domain-level /.well-known/ai-catalog.json. It supersedes the earlier SEP-1649 approach. The server-card schema is still marked experimental.",
1821
  "tags": [
1822
  "mcp",
@@ -1837,6 +2323,7 @@
1837
  "url": "https://modelcontextprotocol.io/specification/2026-07-28",
1838
  "type": "spec",
1839
  "category": "agent-protocols",
 
1840
  "summary": "Latest dated version of the Model Context Protocol specification, covering architecture, base protocol, lifecycle, transports, authorization and client and server features. The version identifier is the date.",
1841
  "tags": [
1842
  "mcp",
@@ -1863,6 +2350,7 @@
1863
  "url": "https://datatracker.ietf.org/doc/draft-mozleywilliams-dnsop-dnsaid/",
1864
  "type": "spec",
1865
  "category": "agent-protocols",
 
1866
  "summary": "Internet-Draft for publishing AI agent endpoints and capability metadata in DNS using SVCB records and DNS-SD-style indexes, with DNSSEC/DANE for validation. Active individual draft, revision 02.",
1867
  "tags": [
1868
  "interop",
@@ -1883,6 +2371,7 @@
1883
  "url": "https://blog.cloudflare.com/agent-readiness",
1884
  "type": "announcement",
1885
  "category": "agent-protocols",
 
1886
  "summary": "Cloudflare post introducing an Agent Readiness score and the isitagentready.com scanner, which checks emerging standards such as llms.txt, Markdown negotiation, Content Signals, RFC 9727 API catalogs, MCP Server Cards, A2A Agent Cards, Agent Skills and the x402/MPP commerce protocols.",
1887
  "tags": [
1888
  "interop",
@@ -1903,6 +2392,7 @@
1903
  "url": "https://modelcontextprotocol.io/specification/2025-06-18",
1904
  "type": "spec",
1905
  "category": "agent-protocols",
 
1906
  "summary": "Earlier dated revision of the MCP specification, covering authorization, transports, roots, sampling, elicitation, prompts and resources.",
1907
  "tags": [
1908
  "mcp",
@@ -1925,6 +2415,7 @@
1925
  "url": "https://llmstxt.org/",
1926
  "type": "spec",
1927
  "category": "agent-protocols",
 
1928
  "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.",
1929
  "tags": [
1930
  "llms-txt",
@@ -1944,6 +2435,7 @@
1944
  "url": "https://spec.openapis.org/oas/v3.1.0.html",
1945
  "type": "spec",
1946
  "category": "agent-protocols",
 
1947
  "summary": "Standard, programming-language-agnostic interface description for HTTP APIs, widely used to describe tools and APIs for programmatic consumers.",
1948
  "tags": [
1949
  "openapi",
@@ -1963,6 +2455,7 @@
1963
  "url": "https://a2a-protocol.org/latest/specification/",
1964
  "type": "spec",
1965
  "category": "agent-protocols",
 
1966
  "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.",
1967
  "tags": [
1968
  "a2a",
@@ -1986,6 +2479,7 @@
1986
  "url": "https://datatracker.ietf.org/doc/html/rfc9421",
1987
  "type": "spec",
1988
  "category": "agent-protocols",
 
1989
  "summary": "IETF Proposed Standard defining how to create, encode and verify digital signatures over components of HTTP messages. It can serve as a building block for authenticating automated clients. Published February 2024 (no day given, so date_published is null).",
1990
  "tags": [
1991
  "identity",
@@ -2006,6 +2500,7 @@
2006
  "url": "https://registry.modelcontextprotocol.io/",
2007
  "type": "directory",
2008
  "category": "agent-protocols",
 
2009
  "summary": "Official registry of MCP servers with an unauthenticated read API (GET /v0.1/servers) supporting cursor pagination, name search and updated_since for incremental sync by downstream aggregators.",
2010
  "tags": [
2011
  "mcp",
@@ -2026,6 +2521,7 @@
2026
  "url": "https://github.com/modelcontextprotocol/registry",
2027
  "type": "repo",
2028
  "category": "agent-protocols",
 
2029
  "summary": "Source, OpenAPI reference and server.json schema for the community-driven MCP Registry, including the publishing flow and namespace verification.",
2030
  "tags": [
2031
  "mcp",
@@ -2046,6 +2542,7 @@
2046
  "url": "https://github.com/modelcontextprotocol/experimental-ext-server-card",
2047
  "type": "repo",
2048
  "category": "agent-protocols",
 
2049
  "summary": "Experimental extension that holds the TypeScript and JSON Schema source for MCP Server Cards. A card describes a remote server's identity and transport endpoints; tools are listed at runtime, not on the card.",
2050
  "tags": [
2051
  "mcp",
@@ -2065,6 +2562,7 @@
2065
  "url": "https://ai-catalog.io/",
2066
  "type": "spec",
2067
  "category": "agent-protocols",
 
2068
  "summary": "Cross-protocol draft standard for a typed, nestable JSON catalog that lists heterogeneous AI artifacts (MCP servers, A2A agents, datasets and more) for discovery. It is developed by members of several AI protocol communities.",
2069
  "tags": [
2070
  "interop",
@@ -2086,6 +2584,7 @@
2086
  "url": "https://a2a-protocol.org/latest/topics/agent-discovery/",
2087
  "type": "docs",
2088
  "category": "agent-protocols",
 
2089
  "summary": "A2A guidance on finding agents through a well-known Agent Card URL (/.well-known/agent-card.json), curated registries, or direct configuration. It notes that the spec does not prescribe a registry API.",
2090
  "tags": [
2091
  "a2a",
@@ -2105,6 +2604,7 @@
2105
  "url": "https://www.a2a-registry.org/",
2106
  "type": "directory",
2107
  "category": "agent-protocols",
 
2108
  "summary": "Free public registry of A2A agents that is itself discoverable as an A2A agent. It offers natural-language agent search and DNS- and GitHub-based verification, and its agent card includes an extension that declares a payment model.",
2109
  "tags": [
2110
  "a2a",
@@ -2125,6 +2625,7 @@
2125
  "url": "https://github.com/wild-card-ai/agents-json",
2126
  "type": "repo",
2127
  "category": "agent-protocols",
 
2128
  "summary": "agents.json, an OpenAPI-based contract published at /.well-known/agents.json that describes multi-step API 'flows' for agents, linking the outputs of one operation to the inputs of the next.",
2129
  "tags": [
2130
  "interop",
@@ -2145,6 +2646,7 @@
2145
  "url": "https://agentskills.io/",
2146
  "type": "spec",
2147
  "category": "agent-protocols",
 
2148
  "summary": "Open format for packaging agent capabilities as SKILL.md files with YAML frontmatter, plus a discovery index schema used by sites at /.well-known/agent-skills/index.json (for example docs.x402.org and mpp.dev).",
2149
  "tags": [
2150
  "interop",
@@ -2165,6 +2667,7 @@
2165
  "url": "https://agents.md/",
2166
  "type": "spec",
2167
  "category": "agent-protocols",
 
2168
  "summary": "Simple open format for a README-style instruction file aimed at coding agents. mpp.dev publishes one and links it from its API catalog.",
2169
  "tags": [
2170
  "interop",
@@ -2186,6 +2689,7 @@
2186
  "url": "https://www.rfc-editor.org/rfc/rfc9727",
2187
  "type": "spec",
2188
  "category": "agent-protocols",
 
2189
  "summary": "Standards-track RFC (June 2025) defining /.well-known/api-catalog and the api-catalog link relation, which return a linkset of a publisher's APIs with links to their descriptions, docs and status endpoints.",
2190
  "tags": [
2191
  "openapi",
@@ -2211,6 +2715,7 @@
2211
  "url": "https://www.rfc-editor.org/rfc/rfc9728",
2212
  "type": "spec",
2213
  "category": "agent-protocols",
 
2214
  "summary": "Standards-track RFC (April 2025) defining metadata that a protected resource publishes so clients can learn how to obtain tokens for it. Remote MCP authorization relies on it.",
2215
  "tags": [
2216
  "identity",
@@ -2232,6 +2737,7 @@
2232
  "url": "https://contentsignals.org/",
2233
  "type": "spec",
2234
  "category": "agent-protocols",
 
2235
  "summary": "robots.txt extension (Content-Signal: search=, ai-input=, ai-train=) that declares how crawled content may be used, settable per user-agent. mpp.dev, x402scan and x402.org use it.",
2236
  "tags": [
2237
  "web-agents",
@@ -2252,6 +2758,7 @@
2252
  "url": "https://github.com/webmachinelearning/webmcp",
2253
  "type": "repo",
2254
  "category": "agent-protocols",
 
2255
  "summary": "Community Group proposal that lets a web page register tools for in-browser agents (document.modelContext.registerTool with a JSON Schema input). It is a CG draft, not a W3C standard.",
2256
  "tags": [
2257
  "mcp",
@@ -2272,6 +2779,7 @@
2272
  "url": "https://glama.ai/mcp/servers",
2273
  "type": "directory",
2274
  "category": "agent-protocols",
 
2275
  "summary": "Large MCP server and remote connector directory, described as a superset of the official MCP Registry. Each server is scanned and scored, and the directory has a public REST API with OpenAPI and an RFC 9727 api-catalog.",
2276
  "tags": [
2277
  "mcp",
@@ -2283,6 +2791,28 @@
2283
  "http_status": 200,
2284
  "archive_url": "http://web.archive.org/web/20261010122735/https://glama.ai/mcp/servers"
2285
  },
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
2286
  {
2287
  "id": "iso-21423-2026-industrial-mobile-robots-interoperability",
2288
  "title": "ISO 21423:2026 Robotics — Industrial mobile robots — Communications and interoperability",
@@ -2292,6 +2822,7 @@
2292
  "url": "https://www.iso.org/standard/86749.html",
2293
  "type": "spec",
2294
  "category": "robotics-autonomy",
 
2295
  "summary": "International Standard (edition 1) that specifies communication requirements between industrial mobile robots, their fleet managers and other equipment and applications in a shared industrial environment, such as ERP tools, lifts, alarms and automated doors. Safety and navigation requirements are out of scope, as are consumer, medical, military and public-road uses.",
2296
  "tags": [
2297
  "robotics",
@@ -2314,6 +2845,7 @@
2314
  "url": "https://www.shopulstandards.com/ProductDetail.aspx?productId=UL4600",
2315
  "type": "spec",
2316
  "category": "robotics-autonomy",
 
2317
  "summary": "ANSI/UL 4600 (3rd edition) covers safety principles, risk mitigation, tools, techniques and lifecycle processes for building and evaluating a safety case for vehicles that operate autonomously without human supervision.",
2318
  "tags": [
2319
  "autonomy-safety",
@@ -2333,6 +2865,7 @@
2333
  "url": "https://www.iso.org/standard/74296.html",
2334
  "type": "spec",
2335
  "category": "robotics-autonomy",
 
2336
  "summary": "International Standard that establishes AI terminology and describes AI concepts for use in developing other standards and in communication among stakeholders.",
2337
  "tags": [
2338
  "ai-standards",
@@ -2352,6 +2885,7 @@
2352
  "url": "https://github.com/ros2/ros2",
2353
  "type": "repo",
2354
  "category": "robotics-autonomy",
 
2355
  "summary": "Main repository of ROS 2, the Robot Operating System, described as a meta operating system for robots.",
2356
  "tags": [
2357
  "ros2",
@@ -2371,6 +2905,7 @@
2371
  "url": "https://www.w3.org/TR/wot-architecture11/",
2372
  "type": "spec",
2373
  "category": "iot",
 
2374
  "summary": "W3C Recommendation defining the abstract architecture of the Web of Things for interoperability across IoT platforms and application domains.",
2375
  "tags": [
2376
  "wot",
@@ -2391,6 +2926,7 @@
2391
  "url": "https://docs.oasis-open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html",
2392
  "type": "spec",
2393
  "category": "iot",
 
2394
  "summary": "OASIS Standard for MQTT v5.0, a lightweight publish/subscribe messaging protocol for IoT and machine-to-machine communication.",
2395
  "tags": [
2396
  "mqtt",
@@ -2411,6 +2947,7 @@
2411
  "url": "https://csa-iot.org/all-solutions/matter/",
2412
  "type": "spec",
2413
  "category": "iot",
 
2414
  "summary": "Connectivity Standards Alliance page for Matter, an industry-unifying standard for reliable, secure, interoperable connectivity between smart home devices, with access to the specification and certification.",
2415
  "tags": [
2416
  "matter",
@@ -2431,6 +2968,7 @@
2431
  "url": "https://opcfoundation.org/about/opc-technologies/opc-ua/",
2432
  "type": "spec",
2433
  "category": "iot",
 
2434
  "summary": "OPC Foundation landing page for OPC Unified Architecture. It describes features such as server discovery, a hierarchical address space, permission-based read/write and subscriptions, and links companion specifications for industry domains.",
2435
  "tags": [
2436
  "opc-ua",
@@ -2456,6 +2994,7 @@
2456
  "url": "https://arxiv.org/abs/2610.27548",
2457
  "type": "research-paper",
2458
  "category": "datasets-benchmarks",
 
2459
  "summary": "The paper introduces AuthorizationBench, 286 executable tasks across ten domains, built from documented real-world cases, that test whether agents stay within the authorization a user granted. Across 6,864 trajectories from 24 model, reasoning-effort and harness configurations, agents acted outside their authorization in 19.2% of runs. Higher reasoning effort left the aggregate rate nearly unchanged.",
2460
  "tags": [
2461
  "benchmark",
@@ -2482,6 +3021,7 @@
2482
  "url": "https://arxiv.org/abs/2406.12045",
2483
  "type": "research-paper",
2484
  "category": "datasets-benchmarks",
 
2485
  "summary": "Benchmark of dynamic conversations between a language-model-simulated user and an agent equipped with domain-specific API tools and policy guidelines. Success is scored by comparing the final database state with an annotated goal state, and the paper introduces the pass^k reliability metric.",
2486
  "tags": [
2487
  "benchmark",
@@ -2509,6 +3049,7 @@
2509
  "url": "https://arxiv.org/abs/2311.12983",
2510
  "type": "research-paper",
2511
  "category": "datasets-benchmarks",
 
2512
  "summary": "Benchmark of real-world questions for general AI assistants that require reasoning, multimodality, web browsing and tool use.",
2513
  "tags": [
2514
  "benchmark",
@@ -2536,6 +3077,7 @@
2536
  "url": "https://arxiv.org/abs/2310.06770",
2537
  "type": "research-paper",
2538
  "category": "datasets-benchmarks",
 
2539
  "summary": "Evaluation framework of 2,294 software engineering problems drawn from real GitHub issues and pull requests across 12 popular Python repositories.",
2540
  "tags": [
2541
  "benchmark",
@@ -2568,6 +3110,7 @@
2568
  "url": "https://arxiv.org/abs/2307.13854",
2569
  "type": "research-paper",
2570
  "category": "datasets-benchmarks",
 
2571
  "summary": "Highly realistic and reproducible web environment for building and testing language-guided agents that perform tasks on the web. The authors list shows the first 12 of a longer list.",
2572
  "tags": [
2573
  "benchmark",
@@ -2588,6 +3131,7 @@
2588
  "url": "https://www.swebench.com/",
2589
  "type": "docs",
2590
  "category": "datasets-benchmarks",
 
2591
  "summary": "Official SWE-bench site with leaderboards for SWE-bench, Verified, Multilingual, Multimodal and Lite variants, plus related tools.",
2592
  "tags": [
2593
  "benchmark",
@@ -2607,6 +3151,7 @@
2607
  "url": "https://robotics-transformer-x.github.io/",
2608
  "type": "docs",
2609
  "category": "datasets-benchmarks",
 
2610
  "summary": "Project page of the Open X-Embodiment Collaboration presenting robotic learning datasets and RT-X models. It asks whether the consolidation around large pretrained models seen in NLP and computer vision can happen in robotics.",
2611
  "tags": [
2612
  "dataset",
@@ -2626,6 +3171,7 @@
2626
  "url": "https://blog.cloudflare.com/verified-bots-accountability/",
2627
  "type": "announcement",
2628
  "category": "safety-security",
 
2629
  "summary": "Cloudflare describes a system that keeps evaluating Verified bots after they have identified themselves (for example via Web Bot Auth request signatures). It measures whether a bot honors robots.txt and responds to direct feedback, and turns this into an explainable trust band. Cloudflare says it plans to publish these scores on Radar.",
2630
  "tags": [
2631
  "identity",
@@ -2652,6 +3198,7 @@
2652
  "url": "https://arxiv.org/abs/2610.21063",
2653
  "type": "research-paper",
2654
  "category": "safety-security",
 
2655
  "summary": "The paper defines twelve attacks on the human-approval path of agent actions (such as decoy recipients, amount cancellation and threshold splitting) and runs them against AP2, Microsoft's action-bound approval design and MCP elicitation. An audit of ten agent runtimes finds no third-party verifiable approval record. The authors propose ASU, a gateway that renders the approval card from a canonical effect descriptor and has a user passkey sign its digest, and they verify it formally with Tamarin.",
2656
  "tags": [
2657
  "security",
@@ -2678,6 +3225,7 @@
2678
  "url": "https://datatracker.ietf.org/doc/draft-ietf-webbotauth-httpsig-protocol/",
2679
  "type": "spec",
2680
  "category": "safety-security",
 
2681
  "summary": "IETF working-group draft (Web Bot Auth) under which bots and agents identify themselves by signing requests with RFC 9421 HTTP Message Signatures, with keys discoverable from a published key directory. It replaces the earlier individual architecture draft.",
2682
  "tags": [
2683
  "identity",
@@ -2690,6 +3238,35 @@
2690
  "http_status": 200,
2691
  "archive_url": "http://web.archive.org/web/20261004055551/https://datatracker.ietf.org/doc/draft-ietf-webbotauth-httpsig-protocol/"
2692
  },
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
2693
  {
2694
  "id": "owasp-top-10-agentic-applications-2026",
2695
  "title": "OWASP Top 10 for Agentic Applications for 2026",
@@ -2699,6 +3276,7 @@
2699
  "url": "https://genai.owasp.org/resource/owasp-top-10-for-agentic-applications-for-2026/",
2700
  "type": "report",
2701
  "category": "safety-security",
 
2702
  "summary": "Peer-reviewed framework, developed with more than 100 experts, identifying the most critical security risks facing autonomous and agentic AI systems.",
2703
  "tags": [
2704
  "owasp",
@@ -2721,6 +3299,7 @@
2721
  "url": "https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-ai-rmf-10",
2722
  "type": "spec",
2723
  "category": "safety-security",
 
2724
  "summary": "Voluntary, non-sector-specific NIST framework, developed as directed by the National Artificial Intelligence Initiative Act of 2020, to help organizations that design, develop, deploy or use AI systems manage AI risks and promote trustworthy, responsible AI.",
2725
  "tags": [
2726
  "ai-risk",
@@ -2741,6 +3320,7 @@
2741
  "url": "https://genai.owasp.org/llm-top-10/",
2742
  "type": "report",
2743
  "category": "safety-security",
 
2744
  "summary": "OWASP Gen AI Security Project list of top risks for LLM applications, 2025 edition (for example LLM01:2025 Prompt Injection), with the 2023-24 edition also linked.",
2745
  "tags": [
2746
  "owasp",
@@ -2752,6 +3332,27 @@
2752
  "http_status": 200,
2753
  "archive_url": "http://web.archive.org/web/20261016132319/https://genai.owasp.org/llm-top-10/"
2754
  },
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
2755
  {
2756
  "id": "fsb-sound-practices-responsible-ai-adoption-final",
2757
  "title": "Sound Practices for Responsible Adoption of Artificial Intelligence (AI): Final report",
@@ -2761,6 +3362,7 @@
2761
  "url": "https://www.fsb.org/2026/10/sound-practices-for-responsible-adoption-of-artificial-intelligence-ai-final-report/",
2762
  "type": "report",
2763
  "category": "regulation",
 
2764
  "summary": "FSB final report setting out 12 sound practices for financial institutions' responsible adoption of AI, grouped into organisation-wide governance and AI-lifecycle risk management. The report includes additional considerations for agentic AI and multi-agent systems, noting that highly autonomous agents may act outside intended boundaries, and states that the practices do not establish an international standard.",
2765
  "tags": [
2766
  "regulation",
@@ -2782,6 +3384,7 @@
2782
  "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai",
2783
  "type": "regulatory",
2784
  "category": "regulation",
 
2785
  "summary": "European Commission overview of the AI Act (Regulation (EU) 2024/1689). The page states the Act entered into force on 1 August 2024 and became applicable on 2 August 2026, with prohibitions applying from 2 February 2025, GPAI obligations from 2 August 2025, and stated high-risk obligations from 2 December 2027.",
2786
  "tags": [
2787
  "eu-ai-act",
 
1
  {
2
  "schema_version": "1",
3
+ "generated_at": "2026-10-23T00: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": 146,
11
  "categories": [
12
  {
13
  "id": "bitcoin-lightning",
14
  "label": "Bitcoin and Lightning",
15
  "featured": true,
16
+ "count": 31,
17
  "json_url": "https://agentpaywire.com/api/library/bitcoin-lightning.json",
18
  "markdown_url": "https://agentpaywire.com/library/bitcoin-lightning.md",
19
  "html_url": "https://agentpaywire.com/library/bitcoin-lightning/"
 
22
  "id": "payments",
23
  "label": "Payments",
24
  "featured": false,
25
+ "count": 64,
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": 26,
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/"
 
67
  "id": "safety-security",
68
  "label": "Safety and security",
69
  "featured": false,
70
+ "count": 7,
71
  "json_url": "https://agentpaywire.com/api/library/safety-security.json",
72
  "markdown_url": "https://agentpaywire.com/library/safety-security.md",
73
  "html_url": "https://agentpaywire.com/library/safety-security/"
 
76
  "id": "regulation",
77
  "label": "Regulation",
78
  "featured": false,
79
+ "count": 3,
80
  "json_url": "https://agentpaywire.com/api/library/regulation.json",
81
  "markdown_url": "https://agentpaywire.com/library/regulation.md",
82
  "html_url": "https://agentpaywire.com/library/regulation/"
 
92
  "url": "https://github.com/getAlby/js-sdk/releases/tag/v8.1.0",
93
  "type": "repo",
94
  "category": "bitcoin-lightning",
95
+ "status": "product_docs",
96
  "summary": "Release of Alby's JavaScript SDK for the Nostr Wallet Connect API. Per the changelog, it adds a recordEvent handler to NWCWalletService for request deduplication, optional since/until filters on subscriptions and a publishNotification method, and it fixes subscription reconnect loops and validates payment and invoice amounts client-side.",
97
  "tags": [
98
  "nwc",
 
118
  "url": "https://github.com/lightning/bolts/pull/1357",
119
  "type": "spec",
120
  "category": "bitcoin-lightning",
121
+ "status": "spec_released",
122
  "summary": "Merged change to the BOLT #11 specification that requires readers to reject an invoice with more than one payment hash, with updated test vectors. The PR explains that libraries differed on whether they took the first or the last payment hash, and that a popular Telegram P2P bot was exploited through this ambiguity, which matters for any system that pays or verifies invoices automatically.",
123
  "tags": [
124
  "lightning",
 
132
  "http_status": 200,
133
  "archive_url": null
134
  },
135
+ {
136
+ "id": "bitcoin-optech-newsletter-427",
137
+ "title": "Bitcoin Optech Newsletter #427",
138
+ "publisher": "Bitcoin Optech",
139
+ "authors": [],
140
+ "date_published": "2026-10-16",
141
+ "url": "https://bitcoinops.org/en/newsletters/2026/10/16/",
142
+ "type": "report",
143
+ "category": "bitcoin-lightning",
144
+ "status": "news",
145
+ "summary": "Newsletter for the week of 2026-10-16. It summarizes the disclosure of two denial-of-service vulnerabilities in Eclair v0.14.0 and earlier, both fixed in v0.14.1, and Adam Gibson's proposal for running multi-round two-party contracts inside a Lightning channel while settling disputes on-chain in a constant number of transactions.",
146
+ "tags": [
147
+ "lightning",
148
+ "security",
149
+ "standards"
150
+ ],
151
+ "verified_at": "2026-10-22",
152
+ "last_checked": "2026-10-22",
153
+ "http_status": 200,
154
+ "archive_url": null
155
+ },
156
  {
157
  "id": "getalby-hub-v1-24-3-release",
158
  "title": "Release v1.24.3 Julian Assange · getAlby/hub",
 
162
  "url": "https://github.com/getAlby/hub/releases/tag/v1.24.3",
163
  "type": "repo",
164
  "category": "bitcoin-lightning",
165
+ "status": "product_docs",
166
  "summary": "Patch release of the self-hosted Alby Hub Lightning node, which exposes wallet connections to apps over Nostr Wallet Connect. Per the release notes, it restricts settling and cancelling hold invoices to the app connection that created them, stops returning the owner's Lightning address to isolated app connections, re-enables on-chain/Lightning swaps with configurable swap providers, and includes UX fixes and security updates.",
167
  "tags": [
168
  "lightning",
 
177
  "http_status": 200,
178
  "archive_url": null
179
  },
180
+ {
181
+ "id": "lightning-enable-l402-is-ready",
182
+ "title": "L402 Is Ready. The Missing Layer Is Adoption.",
183
+ "publisher": "Lightning Enable",
184
+ "authors": [
185
+ "Michael Rahel"
186
+ ],
187
+ "date_published": "2026-10-15",
188
+ "url": "https://docs.lightningenable.com/blog/l402-is-ready-the-missing-layer-is-adoption",
189
+ "type": "announcement",
190
+ "category": "bitcoin-lightning",
191
+ "status": "news",
192
+ "summary": "Michael Rahel writes that L402 is ready and that adoption is the missing layer. The post describes an HTTP 402 response carrying a Lightning invoice and a macaroon, then a retry that presents the token and the payment preimage.",
193
+ "tags": [
194
+ "l402",
195
+ "lightning",
196
+ "macaroons",
197
+ "m2m-payments"
198
+ ],
199
+ "verified_at": "2026-10-22",
200
+ "featured": true,
201
+ "last_checked": "2026-10-22",
202
+ "http_status": 200,
203
+ "archive_url": null
204
+ },
205
  {
206
  "id": "lightning-labs-l402-for-agents",
207
  "title": "The Future Is Now: Why L402 Is the Internet-Native Payments Protocol for Agents",
 
213
  "url": "https://lightning.engineering/posts/2026-03-11-L402-for-agents/",
214
  "type": "announcement",
215
  "category": "bitcoin-lightning",
216
+ "status": "news",
217
  "summary": "Lightning Labs post explaining how L402 puts HTTP 402 Payment Required to work by pairing it with the Lightning Network and cryptographic authentication tokens. Any Lightning-enabled client can pay for and authenticate with an L402 API instantly, with no signup, API key or prior relationship, and the post covers updates to the L402 bLIP specification.",
218
  "tags": [
219
  "l402",
 
239
  "url": "https://lightning.engineering/posts/2026-02-11-ln-agent-tools/",
240
  "type": "announcement",
241
  "category": "bitcoin-lightning",
242
+ "status": "news",
243
  "summary": "Launch post for Lightning Agent Tools: seven composable open-source skills that let AI agents run Lightning nodes, pay L402-gated APIs, host paid endpoints and query nodes via MCP. It also introduces lnget, an L402-aware command-line HTTP client.",
244
  "tags": [
245
  "lightning",
 
254
  "http_status": 200,
255
  "archive_url": "http://web.archive.org/web/20260908091514/https://lightning.engineering/posts/2026-02-11-ln-agent-tools/"
256
  },
257
+ {
258
+ "id": "nip-47-bolt12-pull-1952",
259
+ "title": "Adding support for main bolt12 commands to NIP-47",
260
+ "publisher": "GitHub (nostr-protocol/nips)",
261
+ "authors": [
262
+ "21M4TW"
263
+ ],
264
+ "date_published": "2025-06-11",
265
+ "url": "https://github.com/nostr-protocol/nips/pull/1952",
266
+ "type": "spec",
267
+ "category": "bitcoin-lightning",
268
+ "status": "proposal",
269
+ "summary": "Open pull request, not merged as of 2026-10-22, that asks NIP-47 to let a Lightning client use Nostr Wallet Connect to create BOLT12 offers and to fetch and pay BOLT12 invoices. NWC BOLT12 offer creation and payment is not standardized yet, so check wallet support.",
270
+ "tags": [
271
+ "nostr",
272
+ "nwc",
273
+ "bolt12",
274
+ "lightning",
275
+ "standards"
276
+ ],
277
+ "verified_at": "2026-10-22",
278
+ "last_checked": "2026-10-22",
279
+ "http_status": 200,
280
+ "archive_url": null
281
+ },
282
  {
283
  "id": "lightning-labs-ai-for-all-langchain",
284
  "title": "AI for All: Powering APIs and Large Language Models with Lightning",
 
291
  "url": "https://lightning.engineering/posts/2023-07-05-l402-langchain/",
292
  "type": "announcement",
293
  "category": "bitcoin-lightning",
294
+ "status": "news",
295
  "summary": "Lightning Labs announcement of developer tools built on L402 and LangChain, including LangChainBitcoin. With these tools, agents can hold a Bitcoin balance, send and receive over Lightning, and pay for L402-gated APIs.",
296
  "tags": [
297
  "l402",
 
319
  "url": "https://github.com/Podcastindex-org/podcast-namespace/blob/main/docs/examples/value/value.md",
320
  "type": "spec",
321
  "category": "bitcoin-lightning",
322
+ "status": "spec_released",
323
  "summary": "Podcasting 2.0 specification (v1.4) for a feed-level \"value block\" that lets listeners stream near-real-time Lightning micropayments directly to creators (for example via keysend), calculated per minute of consumption.",
324
  "tags": [
325
  "lightning",
 
347
  "url": "https://arxiv.org/abs/2012.10576",
348
  "type": "research-paper",
349
  "category": "bitcoin-lightning",
350
+ "status": "research",
351
  "summary": "Proposes a protocol that lets resource-constrained IoT devices use Lightning through a gateway node, with 3-of-3 multisignature channels so the device signs every channel operation. It was demonstrated on a Raspberry Pi in a toll-payment scenario.",
352
  "tags": [
353
  "lightning",
 
374
  "url": "https://lightning.network/lightning-network-paper.pdf",
375
  "type": "research-paper",
376
  "category": "bitcoin-lightning",
377
+ "status": "research",
378
  "summary": "Foundational paper (draft v0.5.9.2) proposing a decentralized network of micropayment channels whose value transfers happen off-blockchain. The aim is to scale Bitcoin to high transaction volumes without custodial third parties.",
379
  "tags": [
380
  "lightning",
 
397
  "url": "https://github.com/lightninglabs/lightning-agent-tools",
398
  "type": "repo",
399
  "category": "bitcoin-lightning",
400
+ "status": "product_docs",
401
  "summary": "AI agent toolkit (skills plus an MCP server) for Lightning payments: node operation, L402 API payments, paid endpoint hosting and scoped macaroon credentials. Its default security model uses a remote signer that keeps private keys off the agent machine.",
402
  "tags": [
403
  "lightning",
 
421
  "url": "https://docs.lightning.engineering/the-lightning-network/l402",
422
  "type": "docs",
423
  "category": "bitcoin-lightning",
424
+ "status": "product_docs",
425
  "summary": "Lightning Labs documentation presenting L402 as a standard for selling and buying digital resources that lets services charge for API endpoints in a way AI agents can easily use.",
426
  "tags": [
427
  "l402",
 
444
  "url": "https://docs.lightning.engineering/the-lightning-network/l402/protocol-specification",
445
  "type": "spec",
446
  "category": "bitcoin-lightning",
447
+ "status": "spec_released",
448
  "summary": "Specification of the abstract L402 HTTP and gRPC protocols. It defines the \"L402\" authentication scheme, which carries credentials as macaroon:preimage pairs.",
449
  "tags": [
450
  "l402",
 
467
  "url": "https://github.com/lightninglabs/L402",
468
  "type": "repo",
469
  "category": "bitcoin-lightning",
470
+ "status": "product_docs",
471
  "summary": "Repository for L402, an open protocol for paying for and authenticating access to APIs over the Lightning Network. The server's 402 response carries a macaroon and a Lightning invoice, and the client re-sends the request with the macaroon and the payment preimage.",
472
  "tags": [
473
  "l402",
 
490
  "url": "https://github.com/lightninglabs/aperture",
491
  "type": "repo",
492
  "category": "bitcoin-lightning",
493
+ "status": "product_docs",
494
  "summary": "Aperture is an L402 reverse proxy for gRPC and REST backends that gates access behind Lightning payments. The repository states it is used in production by Lightning Loop.",
495
  "tags": [
496
  "l402",
 
512
  "url": "https://github.com/lightninglabs/LangChainBitcoin",
513
  "type": "repo",
514
  "category": "bitcoin-lightning",
515
+ "status": "product_docs",
516
  "summary": "Tools that give LangChain agents access to Bitcoin and the Lightning Network, including LLM agent BitcoinTools for an lnd node and an L402 HTTP API traversal wrapper.",
517
  "tags": [
518
  "lightning",
 
535
  "url": "https://github.com/lightning/bolts",
536
  "type": "spec",
537
  "category": "bitcoin-lightning",
538
+ "status": "spec_released",
539
  "summary": "Repository of the BOLT specifications, which define the Lightning Network layer-2 protocol for off-chain bitcoin transfer. They cover messaging, peer channel management, transactions, onion routing and invoices.",
540
  "tags": [
541
  "lightning",
 
557
  "url": "https://github.com/lightning/bolts/blob/master/11-payment-encoding.md",
558
  "type": "spec",
559
  "category": "bitcoin-lightning",
560
+ "status": "spec_released",
561
  "summary": "Lightning specification for a simple, extendable, QR-code-ready protocol for requesting payments over Lightning (BOLT 11 invoices).",
562
  "tags": [
563
  "lightning",
 
579
  "url": "https://github.com/lightning/bolts/blob/master/12-offer-encoding.md",
580
  "type": "spec",
581
  "category": "bitcoin-lightning",
582
+ "status": "spec_released",
583
  "summary": "Lightning specification for offers, invoice requests, invoices, invoice errors and payer proofs. It is designed to address limitations of the BOLT 11 invoice format.",
584
  "tags": [
585
  "lightning",
 
602
  "url": "https://bolt12.org/",
603
  "type": "docs",
604
  "category": "bitcoin-lightning",
605
+ "status": "product_docs",
606
  "summary": "Explainer site for BOLT 12, a protocol upgrade to the Lightning Network that enables reusable payment requests, stronger receiver privacy and better censorship resistance.",
607
  "tags": [
608
  "lightning",
 
624
  "url": "https://github.com/nostr-protocol/nips/blob/master/47.md",
625
  "type": "spec",
626
  "category": "bitcoin-lightning",
627
+ "status": "spec_released",
628
  "summary": "Nostr Implementation Possibility that defines a standardized protocol for clients to access a remote Lightning wallet over Nostr, with commands such as pay_invoice and make_invoice.",
629
  "tags": [
630
  "lightning",
 
649
  "url": "https://bitcoin.org/bitcoin.pdf",
650
  "type": "research-paper",
651
  "category": "bitcoin-lightning",
652
+ "status": "research",
653
  "summary": "Foundational paper proposing purely peer-to-peer electronic cash. A proof-of-work timestamp chain solves double-spending without a trusted third party.",
654
  "tags": [
655
  "bitcoin",
 
670
  "url": "https://github.com/lightninglabs/lnget",
671
  "type": "repo",
672
  "category": "bitcoin-lightning",
673
+ "status": "product_docs",
674
  "summary": "A wget/curl-style command-line client that pays L402 Lightning invoices automatically, caches the resulting tokens and retries the request. Per the docs it offers JSON output, a per-request spending cap and an MCP mode for agents.",
675
  "tags": [
676
  "l402",
 
694
  "url": "https://github.com/lightninglabs/lightning-agent-tools/blob/main/docs/l402-and-lnget.md",
695
  "type": "docs",
696
  "category": "bitcoin-lightning",
697
+ "status": "product_docs",
698
  "summary": "Lightning Labs guide on how agents use lnget to reach L402-gated endpoints, covering backend options (lnd, Lightning Node Connect, embedded Neutrino) and bounded per-request spending.",
699
  "tags": [
700
  "l402",
 
717
  "url": "https://github.com/getAlby/mcp",
718
  "type": "repo",
719
  "category": "bitcoin-lightning",
720
+ "status": "product_docs",
721
  "summary": "An MCP server that connects an LLM agent to a Lightning wallet over Nostr Wallet Connect (NWC).",
722
  "tags": [
723
  "lightning",
 
741
  "url": "https://www.l402.org/",
742
  "type": "spec",
743
  "category": "bitcoin-lightning",
744
+ "status": "product_docs",
745
  "summary": "Site describing an offers-based L402 flow in which a server answers HTTP 402 with JSON payment offers and the client retries after payment. This is distinct from Lightning Labs’ macaroon-based L402 specification. The site does not name another publisher.",
746
  "tags": [
747
  "l402",
 
764
  "url": "https://github.com/nostr-protocol/nips/blob/master/90.md",
765
  "type": "spec",
766
  "category": "bitcoin-lightning",
767
+ "status": "spec_released",
768
  "summary": "Nostr spec for on-demand computation ('money in, data out'). Customers publish job requests (kinds 5000-5999), service providers return results (6000-6999) and feedback (7000), and payment is typically made over Lightning. The spec itself is marked draft and 'unrecommended'.",
769
  "tags": [
770
  "nostr",
 
787
  "url": "https://www.l402apps.com/",
788
  "type": "directory",
789
  "category": "bitcoin-lightning",
790
+ "status": "product_docs",
791
  "summary": "Directory of apps and APIs presented as reachable through L402 payment gateways.",
792
  "tags": [
793
  "l402",
 
800
  "http_status": 200,
801
  "archive_url": "http://web.archive.org/web/20260615114727/https://www.l402apps.com/"
802
  },
803
+ {
804
+ "id": "voltage-cli",
805
+ "title": "Voltage CLI",
806
+ "publisher": "Voltage",
807
+ "authors": [],
808
+ "date_published": null,
809
+ "url": "https://github.com/voltagecloud/voltage-cli",
810
+ "type": "repo",
811
+ "category": "bitcoin-lightning",
812
+ "status": "product_docs",
813
+ "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.",
814
+ "tags": [
815
+ "lightning",
816
+ "bitcoin",
817
+ "tools",
818
+ "agent-wallets"
819
+ ],
820
+ "verified_at": "2026-10-23",
821
+ "featured": false,
822
+ "last_checked": "2026-10-23",
823
+ "http_status": 200,
824
+ "archive_url": null
825
+ },
826
+ {
827
+ "id": "stripe-treasury-for-agents",
828
+ "title": "Introducing Stripe Treasury for agents",
829
+ "publisher": "Stripe",
830
+ "authors": [],
831
+ "date_published": "2026-10-21",
832
+ "url": "https://stripe.com/newsroom/news/treasury-for-agents",
833
+ "type": "announcement",
834
+ "category": "payments",
835
+ "status": "news",
836
+ "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.",
837
+ "tags": [
838
+ "agent-wallets",
839
+ "mcp",
840
+ "tools"
841
+ ],
842
+ "verified_at": "2026-10-22",
843
+ "last_checked": "2026-10-22",
844
+ "http_status": 200,
845
+ "archive_url": null
846
+ },
847
+ {
848
+ "id": "singularity-layer-training-lab-x402",
849
+ "title": "Training Lab, now over x402",
850
+ "publisher": "Singularity Layer",
851
+ "authors": [],
852
+ "date_published": "2026-10-21",
853
+ "url": "https://www.x402layer.cc/blog/training-lab-x402",
854
+ "type": "announcement",
855
+ "category": "payments",
856
+ "status": "news",
857
+ "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.",
858
+ "tags": [
859
+ "x402",
860
+ "stablecoins",
861
+ "micropayments",
862
+ "tools"
863
+ ],
864
+ "verified_at": "2026-10-22",
865
+ "last_checked": "2026-10-22",
866
+ "http_status": 200,
867
+ "archive_url": null
868
+ },
869
  {
870
  "id": "visa-bill-billtrust-trusted-agent-b2b-pilot",
871
  "title": "Visa, BILL and Billtrust Launch First Live Pilot for Trusted AI Agent Payments Between Buyer and Supplier Platforms",
 
875
  "url": "https://investor.visa.com/news/news-details/2026/Visa-BILL-and-Billtrust-Launch-First-Live-Pilot-for-Trusted-AI-Agent-Payments-Between-Buyer-and-Supplier-Platforms/default.aspx",
876
  "type": "announcement",
877
  "category": "payments",
878
+ "status": "news",
879
  "summary": "Visa press release on a live pilot in which a BILL payment agent, registered through Visa's Trusted Agent Protocol and Agentic Directory, uses tokenized credentials to pay approved supplier invoices through Billtrust portals. Billtrust uses the Trusted Agent Protocol to recognize and authenticate the agent in place of CAPTCHA-style bot blocking, without a separate agent login.",
880
  "tags": [
881
  "card-networks",
 
900
  "url": "https://www.theblock.co/news/business/2026-10-20-mastercard-opens-early-access-to-ai-agent-payments-following-pilots-with-coinbase-base-and-cloudflare-421406",
901
  "type": "announcement",
902
  "category": "payments",
903
+ "status": "news",
904
  "summary": "The Block reports that Mastercard has opened early access to Agent Pay for Machines, including buyer- and seller-side APIs, a developer toolkit, and a sandbox, after pilots with Cloudflare, Ant International, BVNK, AIsa, Base, and Coinbase. The article says the project is still a pilot and is not commercially available. In a Cloudflare Connect demonstration, an agent made nine payments to two providers using x402; Coinbase Developer Platform supplied the wallet and Base was the settlement network. Merchants returned HTTP 402, payment vouchers can be batched, and BVNK used Mastercard's Global Money Platform so sellers can be paid in fiat or stablecoins.",
905
  "tags": [
906
  "x402",
 
913
  "http_status": 200,
914
  "archive_url": null
915
  },
916
+ {
917
+ "id": "mastercard-agent-pay-for-machines-in-action",
918
+ "title": "What happens when AI agents start paying each other? Watch Mastercard Agent Pay for Machines in action",
919
+ "publisher": "Mastercard",
920
+ "authors": [],
921
+ "date_published": "2026-10-20",
922
+ "url": "https://www.mastercard.com/global/en/news-and-trends/press/2026/october/Mastercard-Agent-Pay-for-Machines-in-action.html",
923
+ "type": "announcement",
924
+ "category": "payments",
925
+ "status": "news",
926
+ "summary": "Mastercard's press page describes Agent Pay for Machines as an x402-based flow in which a service returns HTTP 402 and an agent presents a digitally signed payment voucher within a spending limit that providers can combine and redeem later. Early Access covers buyer- and seller-side APIs; the Cloudflare Connect pilot names Coinbase Developer Platform for wallet funding, Base as the on-chain settlement network, and BVNK as the agent wallet.",
927
+ "tags": [
928
+ "x402",
929
+ "card-networks",
930
+ "m2m-payments",
931
+ "agent-wallets"
932
+ ],
933
+ "verified_at": "2026-10-22",
934
+ "last_checked": "2026-10-22",
935
+ "http_status": 200,
936
+ "archive_url": null
937
+ },
938
  {
939
  "id": "circle-cpn-managed-payments",
940
  "title": "Turn Agent Traffic Into Revenue With CPN Managed Payments",
 
944
  "url": "https://www.circle.com/blog/turn-agent-traffic-into-revenue-with-cpn-managed-payments",
945
  "type": "announcement",
946
  "category": "payments",
947
+ "status": "news",
948
  "summary": "Circle blog post on CPN Managed Payments for eligible businesses that sell data, content, or access to AI agents. The business keeps the product, pricing, metering, and customer relationship. Circle screens and accepts each payment, attributes it to the business, and pays out to the business's bank account in local currency when requested. The post's example is an x402- or MPP-enabled API charged at 0.002 USDC per call.",
949
  "tags": [
950
  "stablecoins",
 
956
  "http_status": 200,
957
  "archive_url": null
958
  },
959
+ {
960
+ "id": "proof-circle-agents-prove-who-they-act-for-and-pay-in-usdc",
961
+ "title": "Proof and Circle Show How AI Agents Can Prove Who They Act For and Pay in USDC",
962
+ "publisher": "Proof",
963
+ "authors": [],
964
+ "date_published": "2026-10-19",
965
+ "url": "https://www.proof.com/blog/proof-and-circle-show-how-ai-agents-can-prove-who-they-act-for-and-pay-in-usdc",
966
+ "type": "announcement",
967
+ "category": "payments",
968
+ "status": "news",
969
+ "summary": "Proof and Circle Internet Group announced a collaboration and a Money20/20 demonstration in which an agent presents a Proof credential via x401 and pays the merchant in USDC over x402 from a Circle Agent Wallet.",
970
+ "tags": [
971
+ "x402",
972
+ "identity",
973
+ "stablecoins",
974
+ "agent-wallets"
975
+ ],
976
+ "verified_at": "2026-10-22",
977
+ "last_checked": "2026-10-22",
978
+ "http_status": 200,
979
+ "archive_url": null
980
+ },
981
  {
982
  "id": "chainalysis-north-america-2026-agentic-x402",
983
  "title": "2026 North America Crypto Adoption: $3.02T, Agentic Rails",
 
989
  "url": "https://www.chainalysis.com/blog/north-america-crypto-adoption-2026/",
990
  "type": "report",
991
  "category": "payments",
992
+ "status": "research",
993
+ "summary": "Chapter of Chainalysis' 2026 Geography of Crypto report that includes on-chain research on x402 agent payments. It reports over 138 million x402 transactions on Base by the end of the period, with more than 87% of payments between a hundredth of a cent and ten cents. It also finds that the share of agent wallets that received a second funding within 30 days of the first rose from 70.6% (Q3 2025 cohort) to 89.3% (Q2 2026 cohort). American wallets account for 88.1% of geolocated AI model inference transactions, 41.8% of payments to agent frameworks and tool catalogs, and 23.2% of payments to data and search APIs. Chinese-funded AI agents took 0.1% of model inference.",
994
  "tags": [
995
  "x402",
996
  "stablecoins",
 
998
  "m2m-payments",
999
  "market-data"
1000
  ],
1001
+ "verified_at": "2026-10-23",
1002
  "featured": false,
1003
+ "last_checked": "2026-10-23",
1004
  "http_status": 200,
1005
  "archive_url": null
1006
  },
 
1015
  "url": "https://www.blackrock.com/us/financial-professionals/insights/machine-native-economy",
1016
  "type": "report",
1017
  "category": "payments",
1018
+ "status": "research",
1019
  "summary": "BlackRock insight arguing that LLMs and blockchains share a machine-native, token-based foundation and that agentic commerce requires machine-native payment rails. It states that stablecoins and native cryptoassets can serve as machine-native instruments for machine-to-machine payments.",
1020
  "tags": [
1021
  "stablecoins",
 
1028
  "http_status": 200,
1029
  "archive_url": "http://web.archive.org/web/20261009205047/https://www.blackrock.com/us/financial-professionals/insights/machine-native-economy"
1030
  },
1031
+ {
1032
+ "id": "cloudflare-monetization-gateway-x402",
1033
+ "title": "x402 protocol",
1034
+ "publisher": "Cloudflare",
1035
+ "authors": [],
1036
+ "date_published": "2026-09-30",
1037
+ "url": "https://developers.cloudflare.com/monetization-gateway/x402/",
1038
+ "type": "docs",
1039
+ "category": "payments",
1040
+ "status": "product_docs",
1041
+ "summary": "Cloudflare Monetization Gateway docs for x402 version 2. The page, last updated 2026-09-30, names two client-facing headers, PAYMENT-REQUIRED and PAYMENT-SIGNATURE, each carrying Base64-encoded JSON. Network identifiers are CAIP-2. The gateway uses the exact scheme for a fixed price and the upto scheme for a variable price. The same product publishes https://developers.cloudflare.com/monetization-gateway/llms.txt. Its overview says the gateway can charge for MCP tools. This page does not name PAYMENT-RESPONSE and does not document a separate Monetization Gateway MCP server.",
1042
+ "tags": [
1043
+ "x402",
1044
+ "http",
1045
+ "standards",
1046
+ "mcp",
1047
+ "llms-txt"
1048
+ ],
1049
+ "verified_at": "2026-10-22",
1050
+ "last_checked": "2026-10-22",
1051
+ "http_status": 200,
1052
+ "archive_url": null
1053
+ },
1054
  {
1055
  "id": "waller-payments-age-ai-agents",
1056
  "title": "Payments in the age of AI agents",
 
1062
  "url": "https://www.bis.org/speeches/20261005-payments-age-ai-agents",
1063
  "type": "regulatory",
1064
  "category": "payments",
1065
+ "status": "news",
1066
  "summary": "Speech by Federal Reserve Governor Christopher J. Waller at Sibos 2026 in Miami on how AI agents may shape payments. Published on the BIS central bankers' speeches site.",
1067
  "tags": [
1068
  "regulation",
 
1092
  "url": "https://www.mckinsey.com/industries/financial-services/our-insights/global-payments-report",
1093
  "type": "report",
1094
  "category": "payments",
1095
+ "status": "research",
1096
  "summary": "McKinsey's annual global payments report, which sizes the industry at roughly $2.6 trillion in revenue from 3.8 trillion transactions. It reviews growth drivers and the shift toward \"invisible\" payments.",
1097
  "tags": [
1098
  "market-data",
 
1118
  "url": "https://datatracker.ietf.org/doc/draft-httpauth-payment/",
1119
  "type": "spec",
1120
  "category": "payments",
1121
+ "status": "individual_draft",
1122
  "summary": "Internet-Draft defining a payment-method-agnostic HTTP authentication scheme for 402 flows: the server sends WWW-Authenticate: Payment with challenge parameters and the client retries with Authorization: Payment and a credential. Revision 01 is dated 2026-09-09 and is an active draft, not an RFC.",
1123
  "tags": [
1124
  "m2m-payments",
 
1145
  "url": "https://arxiv.org/abs/2608.23858",
1146
  "type": "research-paper",
1147
  "category": "payments",
1148
+ "status": "research",
1149
  "summary": "Security analysis of Google's AP2. It finds that signed Checkout and Payment Mandates protect transaction data after signing, while agent interactions before authorization (A2A messages, MCP inputs) stay outside that protection.",
1150
  "tags": [
1151
  "ap2",
 
1166
  "url": "https://www.linuxfoundation.org/press/linux-foundation-announces-operational-launch-of-x402-foundation-to-standardize-internet-native-payments-for-ai-agents-and-applications",
1167
  "type": "announcement",
1168
  "category": "payments",
1169
+ "status": "news",
1170
  "summary": "Press release announcing the operational launch of the x402 Foundation under the Linux Foundation, with 40 founding members, to steward x402 as an open standard for internet-native payments by AI agents and applications.",
1171
  "tags": [
1172
  "x402",
 
1189
  "url": "https://www.bis.org/speeches/20260730-agents-change.pdf",
1190
  "type": "regulatory",
1191
  "category": "payments",
1192
+ "status": "news",
1193
  "summary": "Speech by Bank of England Deputy Governor Sarah Breeden at the ECB Sintra Forum on how agentic AI is changing cyber risk, markets and payments. It argues central banks must adapt quickly, strengthen resilience and cooperate globally.",
1194
  "tags": [
1195
  "regulation",
 
1209
  "url": "https://www.mastercard.com/us/en/news-and-trends/press/2026/june/mastercard-launches-agent-pay-for-machines.html",
1210
  "type": "announcement",
1211
  "category": "payments",
1212
+ "status": "news",
1213
  "summary": "Mastercard press release launching Agent Pay for Machines, a service for continuous, high-velocity agent-to-agent transactions and microtransactions. It lists more than 30 early supporters, including Adyen, Coinbase, Stripe and Tempo.",
1214
  "tags": [
1215
  "card-networks",
 
1229
  "url": "https://www.federalreserve.gov/paymentsystems/files/payments-innovation-roundtable-meeting-20260526.pdf",
1230
  "type": "regulatory",
1231
  "category": "payments",
1232
+ "status": "news",
1233
  "summary": "Meeting summary of a Federal Reserve roundtable (Governors Waller, Barr and Cook) with payments and technology firms, including Visa, Mastercard, Stripe, Coinbase, Google and Skyfire. The discussion covered AI in payments, with a particular focus on agentic commerce.",
1234
  "tags": [
1235
  "regulation",
 
1241
  "http_status": 200,
1242
  "archive_url": "http://web.archive.org/web/20261015115524/https://www.federalreserve.gov/paymentsystems/files/payments-innovation-roundtable-meeting-20260526.pdf"
1243
  },
1244
+ {
1245
+ "id": "solana-pay-sh-google-cloud",
1246
+ "title": "Solana Foundation Launches Pay.sh in Collaboration with Google Cloud",
1247
+ "publisher": "Solana Foundation",
1248
+ "authors": [],
1249
+ "date_published": "2026-05-05",
1250
+ "url": "https://solana.com/news/solana-foundation-launches-pay-sh-in-collaboration-with-google-cloud",
1251
+ "type": "announcement",
1252
+ "category": "payments",
1253
+ "status": "news",
1254
+ "summary": "Solana Foundation announcement dated 2026-05-05 of Pay.sh, built with Google Cloud. The page describes a gateway where an agent pays per request in stablecoins on Solana via x402, with no account and no API key. It names Google Cloud APIs including Gemini and BigQuery, and says the catalog also includes more than 50 community APIs. The page also says Pay.sh is built on x402 and MPP.",
1255
+ "tags": [
1256
+ "x402",
1257
+ "stablecoins",
1258
+ "m2m-payments",
1259
+ "agents"
1260
+ ],
1261
+ "verified_at": "2026-10-22",
1262
+ "last_checked": "2026-10-22",
1263
+ "http_status": 200,
1264
+ "archive_url": null
1265
+ },
1266
  {
1267
  "id": "imf-how-agentic-ai-will-reshape-payments",
1268
  "title": "How Agentic AI Will Reshape Payments",
 
1272
  "url": "https://www.imf.org/en/publications/imf-notes/issues/2026/04/22/how-agentic-ai-will-reshape-payments-575560",
1273
  "type": "report",
1274
  "category": "payments",
1275
+ "status": "research",
1276
  "summary": "IMF Note examining how agentic AI may affect authorization, liquidity, settlement, compliance and resilience in payment systems, using an intent, authorization and settlement framework. It highlights the tension between probabilistic AI behavior and the deterministic requirements of payment infrastructure.",
1277
  "tags": [
1278
  "regulation",
 
1300
  "url": "https://arxiv.org/abs/2604.15367",
1301
  "type": "research-paper",
1302
  "category": "payments",
1303
+ "status": "research",
1304
  "summary": "Systematization of knowledge on the security of autonomous LLM agents that negotiate, purchase and transact across on-chain and off-chain environments. It covers protocols such as ERC-8004 and AP2.",
1305
  "tags": [
1306
  "security",
 
1327
  "url": "https://arxiv.org/abs/2604.02023",
1328
  "type": "research-paper",
1329
  "category": "payments",
1330
+ "status": "research",
1331
  "summary": "Research system that adapts HTTP 402-style payment gating to UPI-like real-time fiat workflows, with policy-governed spend control for autonomous agents calling APIs.",
1332
  "tags": [
1333
  "m2m-payments",
 
1348
  "url": "https://www.linuxfoundation.org/press/linux-foundation-is-launching-the-x402-foundation-and-welcoming-the-contribution-of-the-x402-protocol",
1349
  "type": "announcement",
1350
  "category": "payments",
1351
+ "status": "news",
1352
  "summary": "Press release, issued at MCP Dev Summit North America, announcing a new x402 Foundation to steward the open x402 protocol for payments over HTTP.",
1353
  "tags": [
1354
  "x402",
 
1371
  "url": "https://stripe.com/blog/machine-payments-protocol",
1372
  "type": "announcement",
1373
  "category": "payments",
1374
+ "status": "news",
1375
  "summary": "Stripe blog post launching the Machine Payments Protocol (MPP), an open, internet-native standard for agent payments co-authored by Tempo and Stripe.",
1376
  "tags": [
1377
  "m2m-payments",
 
1392
  "url": "https://corporate.visa.com/en/sites/visa-perspectives/innovation/visa-card-specification-sdk-for-machine-payments-protocol.html",
1393
  "type": "announcement",
1394
  "category": "payments",
1395
+ "status": "news",
1396
  "summary": "Visa announcement of a card specification and SDK that enable card-based payments for autonomous agents within Stripe and Tempo's Machine Payments Protocol. It coincided with Tempo's mainnet launch.",
1397
  "tags": [
1398
  "card-networks",
 
1420
  "url": "https://arxiv.org/abs/2603.01179",
1421
  "type": "research-paper",
1422
  "category": "payments",
1423
+ "status": "research",
1424
  "summary": "Proposes A402, a trust-minimized payment architecture with Atomic Service Channels that bind cryptocurrency payments to service execution and result delivery. It addresses an atomicity gap the authors identify in x402.",
1425
  "tags": [
1426
  "x402",
 
1446
  "url": "https://arxiv.org/abs/2602.06345",
1447
  "type": "research-paper",
1448
  "category": "payments",
1449
+ "status": "research",
1450
  "summary": "eBay-authored paper on runtime behaviors (retries, concurrency, orchestration) that can cause replay and context-binding failures in mandate-based protocols such as AP2 and UCP. It proposes zero-trust runtime verification to mitigate them.",
1451
  "tags": [
1452
  "ap2",
 
1470
  "url": "https://www.bis.org/publ/work1310.htm",
1471
  "type": "research-paper",
1472
  "category": "payments",
1473
+ "status": "research",
1474
  "summary": "BIS Working Paper 1310 examining how generative AI can help manage cash and liquidity in real-time gross settlement (RTGS) payment systems.",
1475
  "tags": [
1476
  "research",
 
1490
  "url": "https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-agentic-commerce-opportunity-how-ai-agents-are-ushering-in-a-new-era-for-consumers-and-merchants",
1491
  "type": "report",
1492
  "category": "payments",
1493
+ "status": "research",
1494
  "summary": "McKinsey QuantumBlack report on how AI agents are changing commerce for consumers and merchants.",
1495
  "tags": [
1496
  "market-data",
 
1510
  "url": "https://usa.visa.com/about-visa/newsroom/press-releases.releaseId.21716.html",
1511
  "type": "announcement",
1512
  "category": "payments",
1513
+ "status": "news",
1514
  "summary": "Visa press release introducing the Trusted Agent Protocol, developed with Cloudflare, to support secure communication between AI agents and merchants and help merchants tell legitimate agents apart from malicious bots.",
1515
  "tags": [
1516
  "card-networks",
 
1531
  "url": "https://www.mastercard.com/global/en/news-and-trends/press/2025/september/mastercard-unveils-new-tools-and-collaborations-to-power-smarter,-safer-agentic-commerce.html",
1532
  "type": "announcement",
1533
  "category": "payments",
1534
+ "status": "news",
1535
  "summary": "Mastercard press release on new developer tools, expanded consulting services and ecosystem collaborations for AI-powered payments, aimed at trusted agentic transaction standards.",
1536
  "tags": [
1537
  "card-networks",
 
1552
  "url": "https://blog.cloudflare.com/introducing-pay-per-crawl/",
1553
  "type": "announcement",
1554
  "category": "payments",
1555
+ "status": "news",
1556
  "summary": "Cloudflare announcement of pay per crawl, which lets content owners charge AI crawlers for access using HTTP 402 responses. It is a machine-payable content model at CDN scale.",
1557
  "tags": [
1558
  "m2m-payments",
 
1580
  "url": "https://www.x402.org/x402-whitepaper.pdf",
1581
  "type": "spec",
1582
  "category": "payments",
1583
+ "status": "research",
1584
  "summary": "Whitepaper describing x402, an HTTP-based protocol that uses onchain payments for agents, context retrieval and APIs. It explains why traditional rails fail for autonomous payments and how x402 works.",
1585
  "tags": [
1586
  "x402",
 
1601
  "url": "https://www.x402.org/",
1602
  "type": "spec",
1603
  "category": "payments",
1604
+ "status": "product_docs",
1605
  "summary": "Official x402 site, describing it as an open standard for internet-native payments that enables agentic payments at scale.",
1606
  "tags": [
1607
  "x402",
 
1622
  "url": "https://github.com/coinbase/x402",
1623
  "type": "repo",
1624
  "category": "payments",
1625
+ "status": "spec_released",
1626
  "summary": "Reference repository for x402, \"a payments protocol for the internet. Built on HTTP.\"",
1627
  "tags": [
1628
  "x402",
 
1642
  "url": "https://github.com/google-agentic-commerce/AP2",
1643
  "type": "repo",
1644
  "category": "payments",
1645
+ "status": "spec_released",
1646
  "summary": "Official repository of the Agent Payments Protocol (AP2), described as \"Building a Secure and Interoperable Future for AI-Driven Payments.\"",
1647
  "tags": [
1648
  "ap2",
 
1663
  "url": "https://www.agenticcommerce.dev/",
1664
  "type": "spec",
1665
  "category": "payments",
1666
+ "status": "product_docs",
1667
  "summary": "Official ACP site describing an Apache-2.0 open standard for programmatic commerce flows between buyers, AI agents and businesses, in which businesses remain merchant of record.",
1668
  "tags": [
1669
  "acp"
 
1682
  "url": "https://github.com/agentic-commerce-protocol/agentic-commerce-protocol",
1683
  "type": "repo",
1684
  "category": "payments",
1685
+ "status": "spec_released",
1686
  "summary": "Specification repository for the Agentic Commerce Protocol, an interaction model and open standard for buyers, their AI agents and businesses, currently maintained by OpenAI and Stripe.",
1687
  "tags": [
1688
  "acp"
 
1701
  "url": "https://docs.stripe.com/agentic-commerce/protocols/acp",
1702
  "type": "docs",
1703
  "category": "payments",
1704
+ "status": "product_docs",
1705
  "summary": "Stripe documentation for ACP, described as an open standard created by Stripe, OpenAI and Meta. It covers agentic checkout, cart and feed, and delegated payment and authentication building blocks.",
1706
  "tags": [
1707
  "acp",
 
1721
  "url": "https://docs.stripe.com/payments/machine/mpp",
1722
  "type": "docs",
1723
  "category": "payments",
1724
+ "status": "product_docs",
1725
  "summary": "Stripe documentation on accepting agent payments with the Machine Payments Protocol: servers respond with HTTP 402 and payment details, and agents authorize payment and retry to receive the resource and a receipt.",
1726
  "tags": [
1727
  "m2m-payments",
 
1741
  "url": "https://developer.visa.com/capabilities/trusted-agent-protocol/overview",
1742
  "type": "docs",
1743
  "category": "payments",
1744
+ "status": "product_docs",
1745
  "summary": "Visa developer documentation for merchants and infrastructure providers. It presents the Trusted Agent Protocol as a verifiable cryptographic standard for recognizing Visa-approved AI agents.",
1746
  "tags": [
1747
  "card-networks",
 
1762
  "url": "https://developer.visa.com/capabilities/visa-intelligent-commerce/overview",
1763
  "type": "docs",
1764
  "category": "payments",
1765
+ "status": "product_docs",
1766
  "summary": "Visa Developer Center product page for Visa Intelligent Commerce, available to acquirer and issuer banks. The full documentation is restricted to authorized users.",
1767
  "tags": [
1768
  "card-networks",
 
1782
  "url": "https://www.bis.org/node/87745",
1783
  "type": "regulatory",
1784
  "category": "payments",
1785
+ "status": "research",
1786
  "summary": "BIS Innovation Hub project with the Bank of Canada and the Swiss National Bank that uses agentic AI to model payment behaviour and intraday liquidity in wholesale payment systems.",
1787
  "tags": [
1788
  "research",
 
1802
  "url": "https://docs.x402.org/extensions/bazaar",
1803
  "type": "docs",
1804
  "category": "payments",
1805
+ "status": "product_docs",
1806
  "summary": "Documentation for the x402 Bazaar extension. Facilitators can catalog payable HTTP endpoints and MCP tools and expose list and search discovery endpoints, so agents can find x402 resources together with their input/output schemas and prices.",
1807
  "tags": [
1808
  "x402",
 
1824
  "url": "https://github.com/x402-foundation/x402/blob/main/specs/extensions/bazaar.md",
1825
  "type": "spec",
1826
  "category": "payments",
1827
+ "status": "spec_released",
1828
  "summary": "Normative spec for the Bazaar extension. It covers facilitator validation of the discovery info and the optional GET /discovery/resources and /discovery/search APIs, which filter by type, payTo, scheme and network and paginate with offsets or cursors.",
1829
  "tags": [
1830
  "x402",
 
1845
  "url": "https://docs.cdp.coinbase.com/x402/bazaar",
1846
  "type": "docs",
1847
  "category": "payments",
1848
+ "status": "product_docs",
1849
  "summary": "Coinbase's hosted Bazaar catalog of x402 resources seen by the CDP Facilitator. It offers a public paginated list, hybrid semantic search with price, network and asset filters, and an MCP interface. The read endpoints need no API key.",
1850
  "tags": [
1851
  "x402",
 
1867
  "url": "https://github.com/Merit-Systems/x402scan/blob/main/docs/DISCOVERY.md",
1868
  "type": "spec",
1869
  "category": "payments",
1870
+ "status": "spec_released",
1871
  "summary": "Describes how x402scan discovers paid endpoints. It reads OpenAPI first, with per-operation x-payment-info pricing and a declared 402 response, and falls back to a /.well-known/x402 resource list. The live 402 challenge overrides static metadata.",
1872
  "tags": [
1873
  "x402",
 
1889
  "url": "https://www.x402scan.com/",
1890
  "type": "directory",
1891
  "category": "payments",
1892
+ "status": "product_docs",
1893
  "summary": "Explorer and registry for x402 that tracks servers, transactions, buyers, merchants and facilitators across chains. It publishes an OpenAPI spec, an RFC 9727 api-catalog and a health endpoint. Most read API calls are paid via x402.",
1894
  "tags": [
1895
  "x402",
 
1911
  "url": "https://mpp.dev/",
1912
  "type": "spec",
1913
  "category": "payments",
1914
+ "status": "product_docs",
1915
  "summary": "Documentation hub for the Machine Payments Protocol, which standardizes HTTP 402 challenges, credentials and receipts for machine payments across methods including stablecoins, cards and Lightning. It publishes llms.txt, per-page Markdown, an MCP server card and an Agent Skills index.",
1916
  "tags": [
1917
  "m2m-payments",
 
1933
  "url": "https://mpp.dev/advanced/discovery",
1934
  "type": "docs",
1935
  "category": "payments",
1936
+ "status": "product_docs",
1937
  "summary": "Explains how an MPP server advertises payment terms ahead of time in an OpenAPI 3.1 document, with paid operations annotated by x-payment-info, while the runtime 402 challenge remains authoritative.",
1938
  "tags": [
1939
  "m2m-payments",
 
1954
  "url": "https://mpp.dev/services",
1955
  "type": "directory",
1956
  "category": "payments",
1957
+ "status": "product_docs",
1958
  "summary": "Curated directory of APIs that accept MPP payments, also available as JSON at /api/services with per-endpoint payment intent, method, asset and amount.",
1959
  "tags": [
1960
  "m2m-payments",
 
1975
  "url": "https://402index.io/",
1976
  "type": "directory",
1977
  "category": "payments",
1978
+ "status": "product_docs",
1979
  "summary": "Protocol-agnostic directory of HTTP 402 paid APIs (L402, x402, MPP) with health probing, payment verification and semantic search. It exposes a JSON API, RSS, webhooks and an MCP server, and aggregates Bazaar, Satring, l402apps and MPP listings.",
1980
  "tags": [
1981
  "l402",
 
1998
  "url": "https://github.com/ryanthegentry/402index",
1999
  "type": "repo",
2000
  "category": "payments",
2001
+ "status": "product_docs",
2002
  "summary": "MIT-licensed source for 402 Index, including an npm MCP server package, self-serve registration through a probe that validates the 402 challenge, and YAML listings accepted by pull request.",
2003
  "tags": [
2004
  "l402",
 
2020
  "url": "https://satring.com/",
2021
  "type": "directory",
2022
  "category": "payments",
2023
+ "status": "product_docs",
2024
  "summary": "Curated directory of paid APIs that accept L402, x402 (USDC on Base) or MPP. It has a free summary tier and paid bulk export, analytics and reputation, plus /.well-known/l402 and /.well-known/x402 payment descriptors and an agent.json.",
2025
  "tags": [
2026
  "l402",
 
2042
  "url": "https://x402.new/",
2043
  "type": "directory",
2044
  "category": "payments",
2045
+ "status": "product_docs",
2046
  "summary": "Directory of x402-payable APIs rebuilt from the public x402 discovery network. Each service page lists price, networks, method, inputs, an example response and 30-day call statistics. It offers paid featured placement.",
2047
  "tags": [
2048
  "x402",
 
2063
  "url": "https://directory.halmarket.dev/",
2064
  "type": "directory",
2065
  "category": "payments",
2066
+ "status": "product_docs",
2067
  "summary": "Marketplace directory of pay-per-call agent services that sellers price per call, paid over Lightning or USDC via x402. It publishes llms.txt and an OpenAPI description of the directory.",
2068
  "tags": [
2069
  "lightning",
 
2085
  "url": "https://ucp.dev/",
2086
  "type": "spec",
2087
  "category": "payments",
2088
+ "status": "product_docs",
2089
  "summary": "Site for the Universal Commerce Protocol, an open agentic-commerce standard.",
2090
  "tags": [
2091
  "interop",
 
2106
  "url": "https://github.com/universal-commerce-protocol/ucp",
2107
  "type": "repo",
2108
  "category": "payments",
2109
+ "status": "spec_released",
2110
  "summary": "Specification and documentation repository for the Universal Commerce Protocol.",
2111
  "tags": [
2112
  "interop",
 
2117
  "http_status": 200,
2118
  "archive_url": "http://web.archive.org/web/20260920171720/https://github.com/Universal-Commerce-Protocol/ucp"
2119
  },
2120
+ {
2121
+ "id": "circle-agent-stack",
2122
+ "title": "Agent stack",
2123
+ "publisher": "Circle",
2124
+ "authors": [],
2125
+ "date_published": null,
2126
+ "url": "https://developers.circle.com/agent-stack",
2127
+ "type": "docs",
2128
+ "category": "payments",
2129
+ "status": "product_docs",
2130
+ "summary": "Circle's Agent stack documentation says an AI agent can hold and transact USDC and other tokens, discover and pay for x402 services, and operate within compliance guardrails. The page lists Circle CLI, Agent Wallets with custom spending policies, Agent Nanopayments, an Agent Marketplace, and a hosted x402 facilitator.",
2131
+ "tags": [
2132
+ "x402",
2133
+ "stablecoins",
2134
+ "agent-wallets",
2135
+ "tools"
2136
+ ],
2137
+ "verified_at": "2026-10-22",
2138
+ "last_checked": "2026-10-22",
2139
+ "http_status": 200,
2140
+ "archive_url": null
2141
+ },
2142
+ {
2143
+ "id": "buy-services-your-agents-can-buy",
2144
+ "title": "Services your agents can buy",
2145
+ "publisher": "buy",
2146
+ "authors": [],
2147
+ "date_published": null,
2148
+ "url": "https://usebuy.ai",
2149
+ "type": "directory",
2150
+ "category": "payments",
2151
+ "status": "product_docs",
2152
+ "summary": "The buy site lists services an agent can pay for per request with one wallet on Celo, and says the catalogue held 782 tools when prices were read on 2026-10-13. The how-it-works section says the caller sets a spending cap per call.",
2153
+ "tags": [
2154
+ "directory",
2155
+ "stablecoins",
2156
+ "tools",
2157
+ "agents"
2158
+ ],
2159
+ "verified_at": "2026-10-22",
2160
+ "last_checked": "2026-10-22",
2161
+ "http_status": 200,
2162
+ "archive_url": null
2163
+ },
2164
+ {
2165
+ "id": "celo-x402-facilitator",
2166
+ "title": "x402 Facilitator — Celo",
2167
+ "publisher": "Celo Core Co.",
2168
+ "authors": [],
2169
+ "date_published": null,
2170
+ "url": "https://x402.celo.org",
2171
+ "type": "docs",
2172
+ "category": "payments",
2173
+ "status": "product_docs",
2174
+ "summary": "x402.celo.org describes a hosted x402 facilitator for Celo, built by Celo Core Co., with a settle endpoint at api.x402.celo.org. It names USDC, USD₮, USA₮, wARS, wBRL, wMXN, wCOP, wPEN, and wCLP as gasless through Permit2, and says a first-time cNGN payer approves Permit2 once and pays that gas.",
2175
+ "tags": [
2176
+ "x402",
2177
+ "stablecoins",
2178
+ "tools"
2179
+ ],
2180
+ "verified_at": "2026-10-22",
2181
+ "last_checked": "2026-10-22",
2182
+ "http_status": 200,
2183
+ "archive_url": null
2184
+ },
2185
+ {
2186
+ "id": "stripe-docs-mcp",
2187
+ "title": "Model Context Protocol (MCP)",
2188
+ "publisher": "Stripe Docs",
2189
+ "authors": [],
2190
+ "date_published": null,
2191
+ "url": "https://docs.stripe.com/mcp",
2192
+ "type": "docs",
2193
+ "category": "payments",
2194
+ "status": "product_docs",
2195
+ "summary": "Stripe documentation for its Model Context Protocol server, labeled public preview. The server URL is https://mcp.stripe.com. Clients authenticate with OAuth or with an agent API key passed as a bearer token in the Authorization header. A GET of https://mcp.stripe.com with no API key returned HTTP 401 on 2026-10-23. Treasury tools on the server are labeled public preview. Related library entry: stripe-treasury-for-agents.",
2196
+ "tags": [
2197
+ "mcp",
2198
+ "agent-wallets",
2199
+ "tools"
2200
+ ],
2201
+ "verified_at": "2026-10-23",
2202
+ "featured": false,
2203
+ "last_checked": "2026-10-23",
2204
+ "http_status": 200,
2205
+ "archive_url": null
2206
+ },
2207
+ {
2208
+ "id": "visa-trusted-agent-protocol-reference",
2209
+ "title": "Trusted Agent Protocol sample implementation",
2210
+ "publisher": "Visa",
2211
+ "authors": [],
2212
+ "date_published": null,
2213
+ "url": "https://github.com/visa/trusted-agent-protocol",
2214
+ "type": "repo",
2215
+ "category": "payments",
2216
+ "status": "product_docs",
2217
+ "summary": "Visa's GitHub repository for a Trusted Agent Protocol sample implementation. The repository includes the modules agent-registry, tap-agent, and merchant-backend. The README says an agent signature includes a timestamp, a session identifier, a key identifier, and an algorithm identifier, and that the signature is bound to the merchant domain and the operation. License: not open source. LICENSE.md requires the Visa Developer Center Terms of Use (https://developer.visa.com/terms), including the Visa Trusted Agent Protocol Product Terms. Related library entries: visa-developer-trusted-agent-protocol and visa-bill-billtrust-trusted-agent-b2b-pilot.",
2218
+ "tags": [
2219
+ "card-networks",
2220
+ "identity",
2221
+ "security"
2222
+ ],
2223
+ "verified_at": "2026-10-23",
2224
+ "featured": false,
2225
+ "last_checked": "2026-10-23",
2226
+ "http_status": 200,
2227
+ "archive_url": null
2228
+ },
2229
+ {
2230
+ "id": "stripe-docs-mpp-sessions",
2231
+ "title": "Accept streaming payments",
2232
+ "publisher": "Stripe Docs",
2233
+ "authors": [],
2234
+ "date_published": null,
2235
+ "url": "https://docs.stripe.com/payments/machine/mpp/sessions",
2236
+ "type": "docs",
2237
+ "category": "payments",
2238
+ "status": "product_docs",
2239
+ "summary": "Stripe documentation for MPP sessions. An agent deposits USDC into a session on Tempo. The server charges for each unit of work in increments as small as 0.000001 USDC and settles funds to the Stripe balance in increments of 0.01 USD or more. Any sub-cent remainder, such as when a client closes a session, is forfeited. Related library entries: stripe-docs-mpp, stripe-introducing-machine-payments-protocol, and stripe-docs-mcp.",
2240
+ "tags": [
2241
+ "m2m-payments",
2242
+ "stablecoins"
2243
+ ],
2244
+ "verified_at": "2026-10-23",
2245
+ "featured": false,
2246
+ "last_checked": "2026-10-23",
2247
+ "http_status": 200,
2248
+ "archive_url": null
2249
+ },
2250
+ {
2251
+ "id": "mcp-tasks-and-events-working-group",
2252
+ "title": "Tasks and Events Charter",
2253
+ "publisher": "Model Context Protocol",
2254
+ "authors": [],
2255
+ "date_published": "2026-10-16",
2256
+ "url": "https://modelcontextprotocol.io/community/working-groups/tasks-events",
2257
+ "type": "docs",
2258
+ "category": "agent-protocols",
2259
+ "status": "product_docs",
2260
+ "summary": "The Tasks and Events Working Group charter says the group continues Tasks, described as MCP's foundation for durable asynchronous execution, and will specify server-initiated notifications. Its changelog records a rename on 2026-10-16, and the resources section links SEP-2663: Tasks Extension.",
2261
+ "tags": [
2262
+ "mcp",
2263
+ "standards",
2264
+ "agents"
2265
+ ],
2266
+ "verified_at": "2026-10-22",
2267
+ "last_checked": "2026-10-22",
2268
+ "http_status": 200,
2269
+ "archive_url": null
2270
+ },
2271
+ {
2272
+ "id": "ietf-draft-prakash-aip-02",
2273
+ "title": "Agent Identity Protocol (draft-prakash-aip-02)",
2274
+ "publisher": "IETF",
2275
+ "authors": [
2276
+ "S. Prakash"
2277
+ ],
2278
+ "date_published": "2026-10-10",
2279
+ "url": "https://datatracker.ietf.org/doc/html/draft-prakash-aip-02",
2280
+ "type": "spec",
2281
+ "category": "agent-protocols",
2282
+ "status": "individual_draft",
2283
+ "summary": "Individual Internet-Draft, not a standard. Published 2026-10-10, intended status Standards Track, expires 2027-04-13. It specifies a delegation chain so a relying party can check who granted authority and that no hop widened it. The encodings are a chain of JWTs or a Biscuit token. MCP carries the token in the X-AIP-Token header, A2A carries it in metadata.aip_token, and generic HTTP uses an Authorization header with the AIP scheme.",
2284
+ "tags": [
2285
+ "mcp",
2286
+ "a2a",
2287
+ "http",
2288
+ "identity",
2289
+ "standards"
2290
+ ],
2291
+ "verified_at": "2026-10-22",
2292
+ "last_checked": "2026-10-22",
2293
+ "http_status": 200,
2294
+ "archive_url": null
2295
+ },
2296
  {
2297
  "id": "mcp-sep-2127-server-cards",
2298
  "title": "SEP-2127: MCP Server Cards - HTTP Server Discovery",
 
2302
  "url": "https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2127",
2303
  "type": "spec",
2304
  "category": "agent-protocols",
2305
+ "status": "spec_released",
2306
  "summary": "Merged MCP enhancement proposal for pre-connection discovery of remote MCP servers through Server Cards, advertised from a domain-level /.well-known/ai-catalog.json. It supersedes the earlier SEP-1649 approach. The server-card schema is still marked experimental.",
2307
  "tags": [
2308
  "mcp",
 
2323
  "url": "https://modelcontextprotocol.io/specification/2026-07-28",
2324
  "type": "spec",
2325
  "category": "agent-protocols",
2326
+ "status": "spec_released",
2327
  "summary": "Latest dated version of the Model Context Protocol specification, covering architecture, base protocol, lifecycle, transports, authorization and client and server features. The version identifier is the date.",
2328
  "tags": [
2329
  "mcp",
 
2350
  "url": "https://datatracker.ietf.org/doc/draft-mozleywilliams-dnsop-dnsaid/",
2351
  "type": "spec",
2352
  "category": "agent-protocols",
2353
+ "status": "individual_draft",
2354
  "summary": "Internet-Draft for publishing AI agent endpoints and capability metadata in DNS using SVCB records and DNS-SD-style indexes, with DNSSEC/DANE for validation. Active individual draft, revision 02.",
2355
  "tags": [
2356
  "interop",
 
2371
  "url": "https://blog.cloudflare.com/agent-readiness",
2372
  "type": "announcement",
2373
  "category": "agent-protocols",
2374
+ "status": "news",
2375
  "summary": "Cloudflare post introducing an Agent Readiness score and the isitagentready.com scanner, which checks emerging standards such as llms.txt, Markdown negotiation, Content Signals, RFC 9727 API catalogs, MCP Server Cards, A2A Agent Cards, Agent Skills and the x402/MPP commerce protocols.",
2376
  "tags": [
2377
  "interop",
 
2392
  "url": "https://modelcontextprotocol.io/specification/2025-06-18",
2393
  "type": "spec",
2394
  "category": "agent-protocols",
2395
+ "status": "spec_released",
2396
  "summary": "Earlier dated revision of the MCP specification, covering authorization, transports, roots, sampling, elicitation, prompts and resources.",
2397
  "tags": [
2398
  "mcp",
 
2415
  "url": "https://llmstxt.org/",
2416
  "type": "spec",
2417
  "category": "agent-protocols",
2418
+ "status": "proposal",
2419
  "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.",
2420
  "tags": [
2421
  "llms-txt",
 
2435
  "url": "https://spec.openapis.org/oas/v3.1.0.html",
2436
  "type": "spec",
2437
  "category": "agent-protocols",
2438
+ "status": "spec_released",
2439
  "summary": "Standard, programming-language-agnostic interface description for HTTP APIs, widely used to describe tools and APIs for programmatic consumers.",
2440
  "tags": [
2441
  "openapi",
 
2455
  "url": "https://a2a-protocol.org/latest/specification/",
2456
  "type": "spec",
2457
  "category": "agent-protocols",
2458
+ "status": "spec_released",
2459
  "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.",
2460
  "tags": [
2461
  "a2a",
 
2479
  "url": "https://datatracker.ietf.org/doc/html/rfc9421",
2480
  "type": "spec",
2481
  "category": "agent-protocols",
2482
+ "status": "standard",
2483
  "summary": "IETF Proposed Standard defining how to create, encode and verify digital signatures over components of HTTP messages. It can serve as a building block for authenticating automated clients. Published February 2024 (no day given, so date_published is null).",
2484
  "tags": [
2485
  "identity",
 
2500
  "url": "https://registry.modelcontextprotocol.io/",
2501
  "type": "directory",
2502
  "category": "agent-protocols",
2503
+ "status": "product_docs",
2504
  "summary": "Official registry of MCP servers with an unauthenticated read API (GET /v0.1/servers) supporting cursor pagination, name search and updated_since for incremental sync by downstream aggregators.",
2505
  "tags": [
2506
  "mcp",
 
2521
  "url": "https://github.com/modelcontextprotocol/registry",
2522
  "type": "repo",
2523
  "category": "agent-protocols",
2524
+ "status": "product_docs",
2525
  "summary": "Source, OpenAPI reference and server.json schema for the community-driven MCP Registry, including the publishing flow and namespace verification.",
2526
  "tags": [
2527
  "mcp",
 
2542
  "url": "https://github.com/modelcontextprotocol/experimental-ext-server-card",
2543
  "type": "repo",
2544
  "category": "agent-protocols",
2545
+ "status": "product_docs",
2546
  "summary": "Experimental extension that holds the TypeScript and JSON Schema source for MCP Server Cards. A card describes a remote server's identity and transport endpoints; tools are listed at runtime, not on the card.",
2547
  "tags": [
2548
  "mcp",
 
2562
  "url": "https://ai-catalog.io/",
2563
  "type": "spec",
2564
  "category": "agent-protocols",
2565
+ "status": "proposal",
2566
  "summary": "Cross-protocol draft standard for a typed, nestable JSON catalog that lists heterogeneous AI artifacts (MCP servers, A2A agents, datasets and more) for discovery. It is developed by members of several AI protocol communities.",
2567
  "tags": [
2568
  "interop",
 
2584
  "url": "https://a2a-protocol.org/latest/topics/agent-discovery/",
2585
  "type": "docs",
2586
  "category": "agent-protocols",
2587
+ "status": "product_docs",
2588
  "summary": "A2A guidance on finding agents through a well-known Agent Card URL (/.well-known/agent-card.json), curated registries, or direct configuration. It notes that the spec does not prescribe a registry API.",
2589
  "tags": [
2590
  "a2a",
 
2604
  "url": "https://www.a2a-registry.org/",
2605
  "type": "directory",
2606
  "category": "agent-protocols",
2607
+ "status": "product_docs",
2608
  "summary": "Free public registry of A2A agents that is itself discoverable as an A2A agent. It offers natural-language agent search and DNS- and GitHub-based verification, and its agent card includes an extension that declares a payment model.",
2609
  "tags": [
2610
  "a2a",
 
2625
  "url": "https://github.com/wild-card-ai/agents-json",
2626
  "type": "repo",
2627
  "category": "agent-protocols",
2628
+ "status": "product_docs",
2629
  "summary": "agents.json, an OpenAPI-based contract published at /.well-known/agents.json that describes multi-step API 'flows' for agents, linking the outputs of one operation to the inputs of the next.",
2630
  "tags": [
2631
  "interop",
 
2646
  "url": "https://agentskills.io/",
2647
  "type": "spec",
2648
  "category": "agent-protocols",
2649
+ "status": "spec_released",
2650
  "summary": "Open format for packaging agent capabilities as SKILL.md files with YAML frontmatter, plus a discovery index schema used by sites at /.well-known/agent-skills/index.json (for example docs.x402.org and mpp.dev).",
2651
  "tags": [
2652
  "interop",
 
2667
  "url": "https://agents.md/",
2668
  "type": "spec",
2669
  "category": "agent-protocols",
2670
+ "status": "spec_released",
2671
  "summary": "Simple open format for a README-style instruction file aimed at coding agents. mpp.dev publishes one and links it from its API catalog.",
2672
  "tags": [
2673
  "interop",
 
2689
  "url": "https://www.rfc-editor.org/rfc/rfc9727",
2690
  "type": "spec",
2691
  "category": "agent-protocols",
2692
+ "status": "standard",
2693
  "summary": "Standards-track RFC (June 2025) defining /.well-known/api-catalog and the api-catalog link relation, which return a linkset of a publisher's APIs with links to their descriptions, docs and status endpoints.",
2694
  "tags": [
2695
  "openapi",
 
2715
  "url": "https://www.rfc-editor.org/rfc/rfc9728",
2716
  "type": "spec",
2717
  "category": "agent-protocols",
2718
+ "status": "standard",
2719
  "summary": "Standards-track RFC (April 2025) defining metadata that a protected resource publishes so clients can learn how to obtain tokens for it. Remote MCP authorization relies on it.",
2720
  "tags": [
2721
  "identity",
 
2737
  "url": "https://contentsignals.org/",
2738
  "type": "spec",
2739
  "category": "agent-protocols",
2740
+ "status": "spec_released",
2741
  "summary": "robots.txt extension (Content-Signal: search=, ai-input=, ai-train=) that declares how crawled content may be used, settable per user-agent. mpp.dev, x402scan and x402.org use it.",
2742
  "tags": [
2743
  "web-agents",
 
2758
  "url": "https://github.com/webmachinelearning/webmcp",
2759
  "type": "repo",
2760
  "category": "agent-protocols",
2761
+ "status": "product_docs",
2762
  "summary": "Community Group proposal that lets a web page register tools for in-browser agents (document.modelContext.registerTool with a JSON Schema input). It is a CG draft, not a W3C standard.",
2763
  "tags": [
2764
  "mcp",
 
2779
  "url": "https://glama.ai/mcp/servers",
2780
  "type": "directory",
2781
  "category": "agent-protocols",
2782
+ "status": "product_docs",
2783
  "summary": "Large MCP server and remote connector directory, described as a superset of the official MCP Registry. Each server is scanned and scored, and the directory has a public REST API with OpenAPI and an RFC 9727 api-catalog.",
2784
  "tags": [
2785
  "mcp",
 
2791
  "http_status": 200,
2792
  "archive_url": "http://web.archive.org/web/20261010122735/https://glama.ai/mcp/servers"
2793
  },
2794
+ {
2795
+ "id": "proof-x401",
2796
+ "title": "x401 — Identity protocol for agentic commerce",
2797
+ "publisher": "Proof",
2798
+ "authors": [],
2799
+ "date_published": null,
2800
+ "url": "https://proof.com/x401",
2801
+ "type": "spec",
2802
+ "category": "agent-protocols",
2803
+ "status": "proposal",
2804
+ "summary": "Proof's x401 page describes an identity protocol for agentic commerce, labeled v0.1.0 and in active development. A service returns HTTP 401 with a base64url JSON PROOF-REQUIRED header that names an OpenID4VP presentation of a jwt_vc_json credential; the page also names PROOF-PRESENTATION and PROOF-RESPONSE.",
2805
+ "tags": [
2806
+ "identity",
2807
+ "standards",
2808
+ "http",
2809
+ "agents"
2810
+ ],
2811
+ "verified_at": "2026-10-22",
2812
+ "last_checked": "2026-10-22",
2813
+ "http_status": 200,
2814
+ "archive_url": null
2815
+ },
2816
  {
2817
  "id": "iso-21423-2026-industrial-mobile-robots-interoperability",
2818
  "title": "ISO 21423:2026 Robotics — Industrial mobile robots — Communications and interoperability",
 
2822
  "url": "https://www.iso.org/standard/86749.html",
2823
  "type": "spec",
2824
  "category": "robotics-autonomy",
2825
+ "status": "standard",
2826
  "summary": "International Standard (edition 1) that specifies communication requirements between industrial mobile robots, their fleet managers and other equipment and applications in a shared industrial environment, such as ERP tools, lifts, alarms and automated doors. Safety and navigation requirements are out of scope, as are consumer, medical, military and public-road uses.",
2827
  "tags": [
2828
  "robotics",
 
2845
  "url": "https://www.shopulstandards.com/ProductDetail.aspx?productId=UL4600",
2846
  "type": "spec",
2847
  "category": "robotics-autonomy",
2848
+ "status": "standard",
2849
  "summary": "ANSI/UL 4600 (3rd edition) covers safety principles, risk mitigation, tools, techniques and lifecycle processes for building and evaluating a safety case for vehicles that operate autonomously without human supervision.",
2850
  "tags": [
2851
  "autonomy-safety",
 
2865
  "url": "https://www.iso.org/standard/74296.html",
2866
  "type": "spec",
2867
  "category": "robotics-autonomy",
2868
+ "status": "standard",
2869
  "summary": "International Standard that establishes AI terminology and describes AI concepts for use in developing other standards and in communication among stakeholders.",
2870
  "tags": [
2871
  "ai-standards",
 
2885
  "url": "https://github.com/ros2/ros2",
2886
  "type": "repo",
2887
  "category": "robotics-autonomy",
2888
+ "status": "product_docs",
2889
  "summary": "Main repository of ROS 2, the Robot Operating System, described as a meta operating system for robots.",
2890
  "tags": [
2891
  "ros2",
 
2905
  "url": "https://www.w3.org/TR/wot-architecture11/",
2906
  "type": "spec",
2907
  "category": "iot",
2908
+ "status": "standard",
2909
  "summary": "W3C Recommendation defining the abstract architecture of the Web of Things for interoperability across IoT platforms and application domains.",
2910
  "tags": [
2911
  "wot",
 
2926
  "url": "https://docs.oasis-open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html",
2927
  "type": "spec",
2928
  "category": "iot",
2929
+ "status": "standard",
2930
  "summary": "OASIS Standard for MQTT v5.0, a lightweight publish/subscribe messaging protocol for IoT and machine-to-machine communication.",
2931
  "tags": [
2932
  "mqtt",
 
2947
  "url": "https://csa-iot.org/all-solutions/matter/",
2948
  "type": "spec",
2949
  "category": "iot",
2950
+ "status": "standard",
2951
  "summary": "Connectivity Standards Alliance page for Matter, an industry-unifying standard for reliable, secure, interoperable connectivity between smart home devices, with access to the specification and certification.",
2952
  "tags": [
2953
  "matter",
 
2968
  "url": "https://opcfoundation.org/about/opc-technologies/opc-ua/",
2969
  "type": "spec",
2970
  "category": "iot",
2971
+ "status": "standard",
2972
  "summary": "OPC Foundation landing page for OPC Unified Architecture. It describes features such as server discovery, a hierarchical address space, permission-based read/write and subscriptions, and links companion specifications for industry domains.",
2973
  "tags": [
2974
  "opc-ua",
 
2994
  "url": "https://arxiv.org/abs/2610.27548",
2995
  "type": "research-paper",
2996
  "category": "datasets-benchmarks",
2997
+ "status": "research",
2998
  "summary": "The paper introduces AuthorizationBench, 286 executable tasks across ten domains, built from documented real-world cases, that test whether agents stay within the authorization a user granted. Across 6,864 trajectories from 24 model, reasoning-effort and harness configurations, agents acted outside their authorization in 19.2% of runs. Higher reasoning effort left the aggregate rate nearly unchanged.",
2999
  "tags": [
3000
  "benchmark",
 
3021
  "url": "https://arxiv.org/abs/2406.12045",
3022
  "type": "research-paper",
3023
  "category": "datasets-benchmarks",
3024
+ "status": "research",
3025
  "summary": "Benchmark of dynamic conversations between a language-model-simulated user and an agent equipped with domain-specific API tools and policy guidelines. Success is scored by comparing the final database state with an annotated goal state, and the paper introduces the pass^k reliability metric.",
3026
  "tags": [
3027
  "benchmark",
 
3049
  "url": "https://arxiv.org/abs/2311.12983",
3050
  "type": "research-paper",
3051
  "category": "datasets-benchmarks",
3052
+ "status": "research",
3053
  "summary": "Benchmark of real-world questions for general AI assistants that require reasoning, multimodality, web browsing and tool use.",
3054
  "tags": [
3055
  "benchmark",
 
3077
  "url": "https://arxiv.org/abs/2310.06770",
3078
  "type": "research-paper",
3079
  "category": "datasets-benchmarks",
3080
+ "status": "research",
3081
  "summary": "Evaluation framework of 2,294 software engineering problems drawn from real GitHub issues and pull requests across 12 popular Python repositories.",
3082
  "tags": [
3083
  "benchmark",
 
3110
  "url": "https://arxiv.org/abs/2307.13854",
3111
  "type": "research-paper",
3112
  "category": "datasets-benchmarks",
3113
+ "status": "research",
3114
  "summary": "Highly realistic and reproducible web environment for building and testing language-guided agents that perform tasks on the web. The authors list shows the first 12 of a longer list.",
3115
  "tags": [
3116
  "benchmark",
 
3131
  "url": "https://www.swebench.com/",
3132
  "type": "docs",
3133
  "category": "datasets-benchmarks",
3134
+ "status": "product_docs",
3135
  "summary": "Official SWE-bench site with leaderboards for SWE-bench, Verified, Multilingual, Multimodal and Lite variants, plus related tools.",
3136
  "tags": [
3137
  "benchmark",
 
3151
  "url": "https://robotics-transformer-x.github.io/",
3152
  "type": "docs",
3153
  "category": "datasets-benchmarks",
3154
+ "status": "product_docs",
3155
  "summary": "Project page of the Open X-Embodiment Collaboration presenting robotic learning datasets and RT-X models. It asks whether the consolidation around large pretrained models seen in NLP and computer vision can happen in robotics.",
3156
  "tags": [
3157
  "dataset",
 
3171
  "url": "https://blog.cloudflare.com/verified-bots-accountability/",
3172
  "type": "announcement",
3173
  "category": "safety-security",
3174
+ "status": "news",
3175
  "summary": "Cloudflare describes a system that keeps evaluating Verified bots after they have identified themselves (for example via Web Bot Auth request signatures). It measures whether a bot honors robots.txt and responds to direct feedback, and turns this into an explainable trust band. Cloudflare says it plans to publish these scores on Radar.",
3176
  "tags": [
3177
  "identity",
 
3198
  "url": "https://arxiv.org/abs/2610.21063",
3199
  "type": "research-paper",
3200
  "category": "safety-security",
3201
+ "status": "research",
3202
  "summary": "The paper defines twelve attacks on the human-approval path of agent actions (such as decoy recipients, amount cancellation and threshold splitting) and runs them against AP2, Microsoft's action-bound approval design and MCP elicitation. An audit of ten agent runtimes finds no third-party verifiable approval record. The authors propose ASU, a gateway that renders the approval card from a canonical effect descriptor and has a user passkey sign its digest, and they verify it formally with Tamarin.",
3203
  "tags": [
3204
  "security",
 
3225
  "url": "https://datatracker.ietf.org/doc/draft-ietf-webbotauth-httpsig-protocol/",
3226
  "type": "spec",
3227
  "category": "safety-security",
3228
+ "status": "working_group_draft",
3229
  "summary": "IETF working-group draft (Web Bot Auth) under which bots and agents identify themselves by signing requests with RFC 9421 HTTP Message Signatures, with keys discoverable from a published key directory. It replaces the earlier individual architecture draft.",
3230
  "tags": [
3231
  "identity",
 
3238
  "http_status": 200,
3239
  "archive_url": "http://web.archive.org/web/20261004055551/https://datatracker.ietf.org/doc/draft-ietf-webbotauth-httpsig-protocol/"
3240
  },
3241
+ {
3242
+ "id": "arxiv-formal-analysis-agent-payment-protocols",
3243
+ "title": "A Formal Analysis of Agent Payment Protocols",
3244
+ "publisher": "arXiv",
3245
+ "authors": [
3246
+ "Ke Jiang",
3247
+ "Mohan Yu",
3248
+ "Yuan Chang",
3249
+ "Mohit Kumar Jangid",
3250
+ "Jianyu Niu",
3251
+ "Cong Wang",
3252
+ "Yinqian Zhang"
3253
+ ],
3254
+ "date_published": "2026-08-30",
3255
+ "url": "https://arxiv.org/abs/2609.00060",
3256
+ "type": "research-paper",
3257
+ "category": "safety-security",
3258
+ "status": "research",
3259
+ "summary": "Paper published on arXiv on 2026-08-30 as 2609.00060v1. It formalizes x402, MPP, ACP, and AP2 in Tamarin. The abstract reports 18 shared security principles and 40 previously undocumented formal-consistency findings, across 86 verification cases.",
3260
+ "tags": [
3261
+ "x402",
3262
+ "security",
3263
+ "research"
3264
+ ],
3265
+ "verified_at": "2026-10-22",
3266
+ "last_checked": "2026-10-22",
3267
+ "http_status": 200,
3268
+ "archive_url": null
3269
+ },
3270
  {
3271
  "id": "owasp-top-10-agentic-applications-2026",
3272
  "title": "OWASP Top 10 for Agentic Applications for 2026",
 
3276
  "url": "https://genai.owasp.org/resource/owasp-top-10-for-agentic-applications-for-2026/",
3277
  "type": "report",
3278
  "category": "safety-security",
3279
+ "status": "spec_released",
3280
  "summary": "Peer-reviewed framework, developed with more than 100 experts, identifying the most critical security risks facing autonomous and agentic AI systems.",
3281
  "tags": [
3282
  "owasp",
 
3299
  "url": "https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-ai-rmf-10",
3300
  "type": "spec",
3301
  "category": "safety-security",
3302
+ "status": "spec_released",
3303
  "summary": "Voluntary, non-sector-specific NIST framework, developed as directed by the National Artificial Intelligence Initiative Act of 2020, to help organizations that design, develop, deploy or use AI systems manage AI risks and promote trustworthy, responsible AI.",
3304
  "tags": [
3305
  "ai-risk",
 
3320
  "url": "https://genai.owasp.org/llm-top-10/",
3321
  "type": "report",
3322
  "category": "safety-security",
3323
+ "status": "spec_released",
3324
  "summary": "OWASP Gen AI Security Project list of top risks for LLM applications, 2025 edition (for example LLM01:2025 Prompt Injection), with the 2023-24 edition also linked.",
3325
  "tags": [
3326
  "owasp",
 
3332
  "http_status": 200,
3333
  "archive_url": "http://web.archive.org/web/20261016132319/https://genai.owasp.org/llm-top-10/"
3334
  },
3335
+ {
3336
+ "id": "occ-bulletin-2026-50-genius-act",
3337
+ "title": "GENIUS Act Regulations: Final Rule",
3338
+ "publisher": "Office of the Comptroller of the Currency",
3339
+ "authors": [],
3340
+ "date_published": "2026-10-21",
3341
+ "url": "https://www.occ.gov/news-issuances/bulletins/2026/bulletin-2026-50.html",
3342
+ "type": "regulatory",
3343
+ "category": "regulation",
3344
+ "status": "standard",
3345
+ "summary": "OCC Bulletin 2026-50, dated October 21, 2026, issuing a final rule to implement the GENIUS Act for payment stablecoin issuance and related activities. The majority of the rules are in a new 12 CFR 15. The final rule is effective January 18, 2027. Rules related to the Bank Secrecy Act, anti-money laundering, and Office of Foreign Assets Control sanctions will be addressed in a separate rulemaking with the Department of the Treasury. Press release: https://occ.gov/news-issuances/news-releases/2026/nr-occ-2026-92.html.",
3346
+ "tags": [
3347
+ "regulation",
3348
+ "stablecoins"
3349
+ ],
3350
+ "verified_at": "2026-10-23",
3351
+ "featured": false,
3352
+ "last_checked": "2026-10-23",
3353
+ "http_status": 200,
3354
+ "archive_url": null
3355
+ },
3356
  {
3357
  "id": "fsb-sound-practices-responsible-ai-adoption-final",
3358
  "title": "Sound Practices for Responsible Adoption of Artificial Intelligence (AI): Final report",
 
3362
  "url": "https://www.fsb.org/2026/10/sound-practices-for-responsible-adoption-of-artificial-intelligence-ai-final-report/",
3363
  "type": "report",
3364
  "category": "regulation",
3365
+ "status": "research",
3366
  "summary": "FSB final report setting out 12 sound practices for financial institutions' responsible adoption of AI, grouped into organisation-wide governance and AI-lifecycle risk management. The report includes additional considerations for agentic AI and multi-agent systems, noting that highly autonomous agents may act outside intended boundaries, and states that the practices do not establish an international standard.",
3367
  "tags": [
3368
  "regulation",
 
3384
  "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai",
3385
  "type": "regulatory",
3386
  "category": "regulation",
3387
+ "status": "standard",
3388
  "summary": "European Commission overview of the AI Act (Regulation (EU) 2024/1689). The page states the Act entered into force on 1 August 2024 and became applicable on 2 August 2026, with prohibitions applying from 2 February 2025, GPAI obligations from 2 August 2025, and stated high-risk obligations from 2 December 2027.",
3389
  "tags": [
3390
  "eu-ai-act",
data/library.schema.json CHANGED
@@ -8,6 +8,7 @@
8
  "required": [
9
  "schema_version",
10
  "generated_at",
 
11
  "license",
12
  "count",
13
  "categories",
@@ -24,6 +25,22 @@
24
  "type": "string",
25
  "pattern": "^\\d{4}-\\d{2}-\\d{2}T00:00:00Z$"
26
  },
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
27
  "license": {
28
  "const": "links + original short summaries; content belongs to publishers"
29
  },
@@ -111,7 +128,8 @@
111
  "summary",
112
  "tags",
113
  "verified_at",
114
- "category"
 
115
  ],
116
  "properties": {
117
  "id": {
@@ -160,6 +178,19 @@
160
  "spec"
161
  ]
162
  },
 
 
 
 
 
 
 
 
 
 
 
 
 
163
  "summary": {
164
  "type": "string",
165
  "minLength": 1
 
8
  "required": [
9
  "schema_version",
10
  "generated_at",
11
+ "disclaimer",
12
  "license",
13
  "count",
14
  "categories",
 
25
  "type": "string",
26
  "pattern": "^\\d{4}-\\d{2}-\\d{2}T00:00:00Z$"
27
  },
28
+ "disclaimer": {
29
+ "type": "object",
30
+ "additionalProperties": false,
31
+ "required": [
32
+ "text",
33
+ "url"
34
+ ],
35
+ "properties": {
36
+ "text": {
37
+ "const": "Not investment advice."
38
+ },
39
+ "url": {
40
+ "const": "https://agentpaywire.com/disclaimer.json"
41
+ }
42
+ }
43
+ },
44
  "license": {
45
  "const": "links + original short summaries; content belongs to publishers"
46
  },
 
128
  "summary",
129
  "tags",
130
  "verified_at",
131
+ "category",
132
+ "status"
133
  ],
134
  "properties": {
135
  "id": {
 
178
  "spec"
179
  ]
180
  },
181
+ "status": {
182
+ "enum": [
183
+ "proposal",
184
+ "individual_draft",
185
+ "working_group_draft",
186
+ "standard",
187
+ "spec_released",
188
+ "product_docs",
189
+ "news",
190
+ "research",
191
+ "unknown"
192
+ ]
193
+ },
194
  "summary": {
195
  "type": "string",
196
  "minLength": 1
data/protocol-facts.json CHANGED
@@ -1,6 +1,10 @@
1
  {
2
  "schema_version": "1",
3
  "generated_at": "2026-10-20T00:00:00Z",
 
 
 
 
4
  "description": "Checked protocol facts. Bitcoin and Lightning protocols are first. Each fact has a source URL and a verified_at date. Null means the cited pages do not state that field.",
5
  "markdown_url": "https://agentpaywire.com/api/protocol-facts.md",
6
  "count": 9,
@@ -81,7 +85,7 @@
81
  "verified_at": "2026-10-20"
82
  },
83
  "example": {
84
- "value": "GET https://api.agentpaywire.com/v1/search?q=bitcoin with no Authorization header returns HTTP 402 and a BOLT11 invoice for 100 sats. Pay the invoice, then retry with Authorization: L402 <macaroon>:<preimage>. sha256 of that preimage matches the payment hash. One payment grants 100 requests for 30 days. Discovery: https://agentpaywire.com/.well-known/l402. The files on https://agentpaywire.com stay free.",
85
  "source": "https://agentpaywire.com/.well-known/l402",
86
  "verified_at": "2026-10-20"
87
  }
 
1
  {
2
  "schema_version": "1",
3
  "generated_at": "2026-10-20T00:00:00Z",
4
+ "disclaimer": {
5
+ "text": "Not investment advice.",
6
+ "url": "https://agentpaywire.com/disclaimer.json"
7
+ },
8
  "description": "Checked protocol facts. Bitcoin and Lightning protocols are first. Each fact has a source URL and a verified_at date. Null means the cited pages do not state that field.",
9
  "markdown_url": "https://agentpaywire.com/api/protocol-facts.md",
10
  "count": 9,
 
85
  "verified_at": "2026-10-20"
86
  },
87
  "example": {
88
+ "value": "GET https://api.agentpaywire.com/v1/search?q=bitcoin with no Authorization header returns HTTP 402 and a BOLT11 invoice for 100 sats. Pay the invoice, then retry with Authorization: L402 <macaroon>:<preimage>. sha256 of that preimage matches the payment hash. One payment grants 100 requests for 30 days. The same credit price covers GET https://api.agentpaywire.com/v1/updates, GET https://api.agentpaywire.com/v1/digest, and GET https://api.agentpaywire.com/v1/changes. Discovery: https://agentpaywire.com/.well-known/l402. The files on https://agentpaywire.com stay free.",
89
  "source": "https://agentpaywire.com/.well-known/l402",
90
  "verified_at": "2026-10-20"
91
  }
data/sources.csv CHANGED
The diff for this file is too large to render. See raw diff
 
data/sources.jsonl CHANGED
The diff for this file is too large to render. See raw diff
 
data/tags.json CHANGED
@@ -1,11 +1,11 @@
1
  {
2
  "schema_version": "1",
3
- "generated_at": "2026-10-20T00:00:00Z",
4
  "count": 51,
5
  "tags": [
6
  {
7
  "tag": "a2a",
8
- "count": 4,
9
  "json_url": "https://agentpaywire.com/api/library/tag/a2a.json"
10
  },
11
  {
@@ -15,17 +15,17 @@
15
  },
16
  {
17
  "tag": "agent-wallets",
18
- "count": 10,
19
  "json_url": "https://agentpaywire.com/api/library/tag/agent-wallets.json"
20
  },
21
  {
22
  "tag": "agents",
23
- "count": 4,
24
  "json_url": "https://agentpaywire.com/api/library/tag/agents.json"
25
  },
26
  {
27
  "tag": "ai-risk",
28
- "count": 1,
29
  "json_url": "https://agentpaywire.com/api/library/tag/ai-risk.json"
30
  },
31
  {
@@ -35,7 +35,7 @@
35
  },
36
  {
37
  "tag": "ap2",
38
- "count": 4,
39
  "json_url": "https://agentpaywire.com/api/library/tag/ap2.json"
40
  },
41
  {
@@ -45,22 +45,22 @@
45
  },
46
  {
47
  "tag": "benchmark",
48
- "count": 5,
49
  "json_url": "https://agentpaywire.com/api/library/tag/benchmark.json"
50
  },
51
  {
52
  "tag": "bitcoin",
53
- "count": 11,
54
  "json_url": "https://agentpaywire.com/api/library/tag/bitcoin.json"
55
  },
56
  {
57
  "tag": "bolt12",
58
- "count": 2,
59
  "json_url": "https://agentpaywire.com/api/library/tag/bolt12.json"
60
  },
61
  {
62
  "tag": "card-networks",
63
- "count": 7,
64
  "json_url": "https://agentpaywire.com/api/library/tag/card-networks.json"
65
  },
66
  {
@@ -70,7 +70,7 @@
70
  },
71
  {
72
  "tag": "directory",
73
- "count": 16,
74
  "json_url": "https://agentpaywire.com/api/library/tag/directory.json"
75
  },
76
  {
@@ -80,22 +80,22 @@
80
  },
81
  {
82
  "tag": "http",
83
- "count": 4,
84
  "json_url": "https://agentpaywire.com/api/library/tag/http.json"
85
  },
86
  {
87
  "tag": "identity",
88
- "count": 12,
89
  "json_url": "https://agentpaywire.com/api/library/tag/identity.json"
90
  },
91
  {
92
  "tag": "industrial-iot",
93
- "count": 1,
94
  "json_url": "https://agentpaywire.com/api/library/tag/industrial-iot.json"
95
  },
96
  {
97
  "tag": "interop",
98
- "count": 27,
99
  "json_url": "https://agentpaywire.com/api/library/tag/interop.json"
100
  },
101
  {
@@ -105,7 +105,7 @@
105
  },
106
  {
107
  "tag": "l402",
108
- "count": 16,
109
  "json_url": "https://agentpaywire.com/api/library/tag/l402.json"
110
  },
111
  {
@@ -115,12 +115,12 @@
115
  },
116
  {
117
  "tag": "lightning",
118
- "count": 27,
119
  "json_url": "https://agentpaywire.com/api/library/tag/lightning.json"
120
  },
121
  {
122
  "tag": "llms-txt",
123
- "count": 1,
124
  "json_url": "https://agentpaywire.com/api/library/tag/llms-txt.json"
125
  },
126
  {
@@ -130,17 +130,17 @@
130
  },
131
  {
132
  "tag": "m2m-payments",
133
- "count": 27,
134
  "json_url": "https://agentpaywire.com/api/library/tag/m2m-payments.json"
135
  },
136
  {
137
  "tag": "macaroons",
138
- "count": 2,
139
  "json_url": "https://agentpaywire.com/api/library/tag/macaroons.json"
140
  },
141
  {
142
  "tag": "market-data",
143
- "count": 4,
144
  "json_url": "https://agentpaywire.com/api/library/tag/market-data.json"
145
  },
146
  {
@@ -150,12 +150,12 @@
150
  },
151
  {
152
  "tag": "mcp",
153
- "count": 17,
154
  "json_url": "https://agentpaywire.com/api/library/tag/mcp.json"
155
  },
156
  {
157
  "tag": "micropayments",
158
- "count": 8,
159
  "json_url": "https://agentpaywire.com/api/library/tag/micropayments.json"
160
  },
161
  {
@@ -165,12 +165,12 @@
165
  },
166
  {
167
  "tag": "nostr",
168
- "count": 3,
169
  "json_url": "https://agentpaywire.com/api/library/tag/nostr.json"
170
  },
171
  {
172
  "tag": "nwc",
173
- "count": 2,
174
  "json_url": "https://agentpaywire.com/api/library/tag/nwc.json"
175
  },
176
  {
@@ -195,17 +195,17 @@
195
  },
196
  {
197
  "tag": "regulation",
198
- "count": 8,
199
  "json_url": "https://agentpaywire.com/api/library/tag/regulation.json"
200
  },
201
  {
202
  "tag": "research",
203
- "count": 17,
204
  "json_url": "https://agentpaywire.com/api/library/tag/research.json"
205
  },
206
  {
207
  "tag": "robotics",
208
- "count": 2,
209
  "json_url": "https://agentpaywire.com/api/library/tag/robotics.json"
210
  },
211
  {
@@ -215,17 +215,17 @@
215
  },
216
  {
217
  "tag": "security",
218
- "count": 19,
219
  "json_url": "https://agentpaywire.com/api/library/tag/security.json"
220
  },
221
  {
222
  "tag": "stablecoins",
223
- "count": 13,
224
  "json_url": "https://agentpaywire.com/api/library/tag/stablecoins.json"
225
  },
226
  {
227
  "tag": "standards",
228
- "count": 16,
229
  "json_url": "https://agentpaywire.com/api/library/tag/standards.json"
230
  },
231
  {
@@ -235,17 +235,17 @@
235
  },
236
  {
237
  "tag": "tokenization",
238
- "count": 4,
239
  "json_url": "https://agentpaywire.com/api/library/tag/tokenization.json"
240
  },
241
  {
242
  "tag": "tools",
243
- "count": 8,
244
  "json_url": "https://agentpaywire.com/api/library/tag/tools.json"
245
  },
246
  {
247
  "tag": "web-agents",
248
- "count": 6,
249
  "json_url": "https://agentpaywire.com/api/library/tag/web-agents.json"
250
  },
251
  {
@@ -255,7 +255,7 @@
255
  },
256
  {
257
  "tag": "x402",
258
- "count": 16,
259
  "json_url": "https://agentpaywire.com/api/library/tag/x402.json"
260
  }
261
  ]
 
1
  {
2
  "schema_version": "1",
3
+ "generated_at": "2026-10-23T00:00:00Z",
4
  "count": 51,
5
  "tags": [
6
  {
7
  "tag": "a2a",
8
+ "count": 5,
9
  "json_url": "https://agentpaywire.com/api/library/tag/a2a.json"
10
  },
11
  {
 
15
  },
16
  {
17
  "tag": "agent-wallets",
18
+ "count": 18,
19
  "json_url": "https://agentpaywire.com/api/library/tag/agent-wallets.json"
20
  },
21
  {
22
  "tag": "agents",
23
+ "count": 9,
24
  "json_url": "https://agentpaywire.com/api/library/tag/agents.json"
25
  },
26
  {
27
  "tag": "ai-risk",
28
+ "count": 2,
29
  "json_url": "https://agentpaywire.com/api/library/tag/ai-risk.json"
30
  },
31
  {
 
35
  },
36
  {
37
  "tag": "ap2",
38
+ "count": 5,
39
  "json_url": "https://agentpaywire.com/api/library/tag/ap2.json"
40
  },
41
  {
 
45
  },
46
  {
47
  "tag": "benchmark",
48
+ "count": 6,
49
  "json_url": "https://agentpaywire.com/api/library/tag/benchmark.json"
50
  },
51
  {
52
  "tag": "bitcoin",
53
+ "count": 12,
54
  "json_url": "https://agentpaywire.com/api/library/tag/bitcoin.json"
55
  },
56
  {
57
  "tag": "bolt12",
58
+ "count": 3,
59
  "json_url": "https://agentpaywire.com/api/library/tag/bolt12.json"
60
  },
61
  {
62
  "tag": "card-networks",
63
+ "count": 11,
64
  "json_url": "https://agentpaywire.com/api/library/tag/card-networks.json"
65
  },
66
  {
 
70
  },
71
  {
72
  "tag": "directory",
73
+ "count": 17,
74
  "json_url": "https://agentpaywire.com/api/library/tag/directory.json"
75
  },
76
  {
 
80
  },
81
  {
82
  "tag": "http",
83
+ "count": 8,
84
  "json_url": "https://agentpaywire.com/api/library/tag/http.json"
85
  },
86
  {
87
  "tag": "identity",
88
+ "count": 19,
89
  "json_url": "https://agentpaywire.com/api/library/tag/identity.json"
90
  },
91
  {
92
  "tag": "industrial-iot",
93
+ "count": 2,
94
  "json_url": "https://agentpaywire.com/api/library/tag/industrial-iot.json"
95
  },
96
  {
97
  "tag": "interop",
98
+ "count": 28,
99
  "json_url": "https://agentpaywire.com/api/library/tag/interop.json"
100
  },
101
  {
 
105
  },
106
  {
107
  "tag": "l402",
108
+ "count": 17,
109
  "json_url": "https://agentpaywire.com/api/library/tag/l402.json"
110
  },
111
  {
 
115
  },
116
  {
117
  "tag": "lightning",
118
+ "count": 34,
119
  "json_url": "https://agentpaywire.com/api/library/tag/lightning.json"
120
  },
121
  {
122
  "tag": "llms-txt",
123
+ "count": 2,
124
  "json_url": "https://agentpaywire.com/api/library/tag/llms-txt.json"
125
  },
126
  {
 
130
  },
131
  {
132
  "tag": "m2m-payments",
133
+ "count": 36,
134
  "json_url": "https://agentpaywire.com/api/library/tag/m2m-payments.json"
135
  },
136
  {
137
  "tag": "macaroons",
138
+ "count": 3,
139
  "json_url": "https://agentpaywire.com/api/library/tag/macaroons.json"
140
  },
141
  {
142
  "tag": "market-data",
143
+ "count": 5,
144
  "json_url": "https://agentpaywire.com/api/library/tag/market-data.json"
145
  },
146
  {
 
150
  },
151
  {
152
  "tag": "mcp",
153
+ "count": 23,
154
  "json_url": "https://agentpaywire.com/api/library/tag/mcp.json"
155
  },
156
  {
157
  "tag": "micropayments",
158
+ "count": 10,
159
  "json_url": "https://agentpaywire.com/api/library/tag/micropayments.json"
160
  },
161
  {
 
165
  },
166
  {
167
  "tag": "nostr",
168
+ "count": 5,
169
  "json_url": "https://agentpaywire.com/api/library/tag/nostr.json"
170
  },
171
  {
172
  "tag": "nwc",
173
+ "count": 5,
174
  "json_url": "https://agentpaywire.com/api/library/tag/nwc.json"
175
  },
176
  {
 
195
  },
196
  {
197
  "tag": "regulation",
198
+ "count": 10,
199
  "json_url": "https://agentpaywire.com/api/library/tag/regulation.json"
200
  },
201
  {
202
  "tag": "research",
203
+ "count": 20,
204
  "json_url": "https://agentpaywire.com/api/library/tag/research.json"
205
  },
206
  {
207
  "tag": "robotics",
208
+ "count": 3,
209
  "json_url": "https://agentpaywire.com/api/library/tag/robotics.json"
210
  },
211
  {
 
215
  },
216
  {
217
  "tag": "security",
218
+ "count": 27,
219
  "json_url": "https://agentpaywire.com/api/library/tag/security.json"
220
  },
221
  {
222
  "tag": "stablecoins",
223
+ "count": 24,
224
  "json_url": "https://agentpaywire.com/api/library/tag/stablecoins.json"
225
  },
226
  {
227
  "tag": "standards",
228
+ "count": 24,
229
  "json_url": "https://agentpaywire.com/api/library/tag/standards.json"
230
  },
231
  {
 
235
  },
236
  {
237
  "tag": "tokenization",
238
+ "count": 5,
239
  "json_url": "https://agentpaywire.com/api/library/tag/tokenization.json"
240
  },
241
  {
242
  "tag": "tools",
243
+ "count": 17,
244
  "json_url": "https://agentpaywire.com/api/library/tag/tools.json"
245
  },
246
  {
247
  "tag": "web-agents",
248
+ "count": 7,
249
  "json_url": "https://agentpaywire.com/api/library/tag/web-agents.json"
250
  },
251
  {
 
255
  },
256
  {
257
  "tag": "x402",
258
+ "count": 27,
259
  "json_url": "https://agentpaywire.com/api/library/tag/x402.json"
260
  }
261
  ]