agentpaywire commited on
Commit
5d9138b
·
verified ·
1 Parent(s): 8f124ec

Sync library snapshot 2026-11-05 (173 entries; Aperture v0.6.0, Core Lightning v26.06.10, OCC Bulletin 2026-54, Agent Money Benchmark v1)

Browse files
README.md CHANGED
@@ -26,7 +26,7 @@ configs:
26
 
27
  # Agent Paywire Knowledge Library
28
 
29
- A curated library of **170 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 taken 2026-11-04 (last updated 2026-11-04). `verified_at` dates: 2026-10-20 (112 rows), 2026-10-21 (10 rows), 2026-10-22 (15 rows), 2026-10-23 (6 rows), 2026-10-24 (5 rows), 2026-10-25 (2 rows), 2026-10-26 (2 rows), 2026-10-27 (1 row), 2026-10-28 (1 row), 2026-10-31 (7 rows), 2026-11-03 (7 rows), 2026-11-04 (2 rows); the library files (`library.json`, `tags.json`) report `generated_at` 2026-11-04T00: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) | 39 |
47
  | payments | 70 |
48
  | agent-protocols | 33 |
49
  | robotics-autonomy | 4 |
50
  | iot | 4 |
51
- | datasets-benchmarks | 8 |
52
  | safety-security | 9 |
53
- | regulation | 3 |
54
 
55
  ## Fields (`data/sources.jsonl`)
56
 
57
- One JSON object per line, 170 rows, single `train` split. Dates are `YYYY-MM-DD` strings in the file; the `datasets` JSON loader infers `date_published`, `verified_at` and `last_checked` as timestamps. JSON Schema: https://agentpaywire.com/schemas/library.schema.json (copy in `data/library.schema.json`).
58
 
59
  | field | type | description |
60
  | --- | --- | --- |
@@ -62,7 +62,7 @@ One JSON object per line, 170 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 (78 of 170 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. |
@@ -70,7 +70,7 @@ One JSON object per line, 170 rows, single `train` split. Dates are `YYYY-MM-DD`
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 (37 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,9 +79,9 @@ One JSON object per line, 170 rows, single `train` split. Dates are `YYYY-MM-DD`
79
 
80
  | file | contents |
81
  | --- | --- |
82
- | `data/sources.jsonl` | Main table (default config). 170 rows. |
83
- | `data/sources.csv` | Same 170 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 170 entries. From https://agentpaywire.com/api/library.json. |
85
  | `data/library.schema.json` | JSON Schema for the library documents. |
86
  | `data/tags.json` | Tag index, 70 tags with counts. From https://agentpaywire.com/api/library/tags.json. |
87
  | `data/protocol-facts.json` | Checked facts for 11 protocols (L402, BOLT 12, BIP 21, NWC, x402, MPP, AP2, ACP, UCP, MCP, A2A). From https://agentpaywire.com/api/protocol-facts.json. |
 
26
 
27
  # Agent Paywire Knowledge Library
28
 
29
+ A curated library of **173 verified sources** about how AI agents pay and get paid: machine-to-machine payment protocols (L402, x402 and others), Bitcoin and Lightning, stablecoins, agent protocols (e.g. MCP), and the surrounding security, IoT, robotics and regulation context. Each row is one source: a link to the original publication plus metadata and a short, neutral summary written for this library.
30
 
31
  This is the Hugging Face copy of the `agentpaywire-library` dataset published by [Agent Paywire](https://agentpaywire.com), a machine-readable reference site for AI agents on agent payments.
32
 
 
36
 
37
  - Built from the live site: https://agentpaywire.com/library (dataset card on the site: https://agentpaywire.com/datasets/agentpaywire-library/).
38
  - `data/sources.jsonl` is byte-identical to https://agentpaywire.com/dataset/library.jsonl (and https://agentpaywire.com/library.jsonl) at the time of this snapshot.
39
+ - Snapshot taken 2026-11-05 (last updated 2026-11-05). `verified_at` dates: 2026-10-20 (111 rows), 2026-10-21 (10 rows), 2026-10-22 (15 rows), 2026-10-23 (6 rows), 2026-10-24 (5 rows), 2026-10-25 (2 rows), 2026-10-26 (2 rows), 2026-10-27 (1 row), 2026-10-28 (1 row), 2026-10-31 (7 rows), 2026-11-03 (7 rows), 2026-11-04 (2 rows), 2026-11-05 (4 rows); the library files (`library.json`, `tags.json`) report `generated_at` 2026-11-05T00: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) | 40 |
47
  | payments | 70 |
48
  | agent-protocols | 33 |
49
  | robotics-autonomy | 4 |
50
  | iot | 4 |
51
+ | datasets-benchmarks | 9 |
52
  | safety-security | 9 |
53
+ | regulation | 4 |
54
 
55
  ## Fields (`data/sources.jsonl`)
56
 
57
+ One JSON object per line, 173 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 (78 of 173 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. |
 
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 (38 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). 173 rows. |
83
+ | `data/sources.csv` | Same 173 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 173 entries. From https://agentpaywire.com/api/library.json. |
85
  | `data/library.schema.json` | JSON Schema for the library documents. |
86
  | `data/tags.json` | Tag index, 70 tags with counts. From https://agentpaywire.com/api/library/tags.json. |
87
  | `data/protocol-facts.json` | Checked facts for 11 protocols (L402, BOLT 12, BIP 21, NWC, x402, MPP, AP2, ACP, UCP, MCP, A2A). From https://agentpaywire.com/api/protocol-facts.json. |
data/library.json CHANGED
@@ -1,19 +1,19 @@
1
  {
2
  "schema_version": "1",
3
- "generated_at": "2026-11-04T00: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": 170,
11
  "categories": [
12
  {
13
  "id": "bitcoin-lightning",
14
  "label": "Bitcoin and Lightning",
15
  "featured": true,
16
- "count": 39,
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/"
@@ -58,7 +58,7 @@
58
  "id": "datasets-benchmarks",
59
  "label": "Datasets and benchmarks",
60
  "featured": false,
61
- "count": 8,
62
  "json_url": "https://agentpaywire.com/api/library/datasets-benchmarks.json",
63
  "markdown_url": "https://agentpaywire.com/library/datasets-benchmarks.md",
64
  "html_url": "https://agentpaywire.com/library/datasets-benchmarks/"
@@ -76,13 +76,58 @@
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/"
83
  }
84
  ],
85
  "entries": [
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
86
  {
87
  "id": "wavelength-v0-2-1-release",
88
  "title": "Wavelength v0.2.1",
@@ -677,28 +722,6 @@
677
  "http_status": 200,
678
  "archive_url": "http://web.archive.org/web/20260610015121/https://github.com/lightninglabs/L402"
679
  },
680
- {
681
- "id": "lightninglabs-aperture-github",
682
- "title": "lightninglabs/aperture",
683
- "publisher": "GitHub (Lightning Labs)",
684
- "authors": [],
685
- "date_published": null,
686
- "url": "https://github.com/lightninglabs/aperture",
687
- "type": "repo",
688
- "category": "bitcoin-lightning",
689
- "status": "product_docs",
690
- "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.",
691
- "tags": [
692
- "l402",
693
- "lightning",
694
- "m2m-payments"
695
- ],
696
- "verified_at": "2026-10-20",
697
- "featured": true,
698
- "last_checked": "2026-10-20",
699
- "http_status": 200,
700
- "archive_url": "http://web.archive.org/web/20250812194102/https://github.com/lightninglabs/aperture"
701
- },
702
  {
703
  "id": "lightninglabs-langchainbitcoin-github",
704
  "title": "lightninglabs/LangChainBitcoin",
@@ -3672,6 +3695,28 @@
3672
  "http_status": 200,
3673
  "archive_url": "http://web.archive.org/web/20260905225407/https://robotics-transformer-x.github.io/"
3674
  },
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
3675
  {
3676
  "id": "arxiv-2610-35835-i-hitl",
3677
  "title": "I-HITL: Inalienable Human-in-the-Loop",
@@ -3896,6 +3941,28 @@
3896
  "http_status": 200,
3897
  "archive_url": "http://web.archive.org/web/20261016132319/https://genai.owasp.org/llm-top-10/"
3898
  },
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
3899
  {
3900
  "id": "occ-bulletin-2026-50-genius-act",
3901
  "title": "GENIUS Act Regulations: Final Rule",
 
1
  {
2
  "schema_version": "1",
3
+ "generated_at": "2026-11-05T00: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": 173,
11
  "categories": [
12
  {
13
  "id": "bitcoin-lightning",
14
  "label": "Bitcoin and Lightning",
15
  "featured": true,
16
+ "count": 40,
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/"
 
58
  "id": "datasets-benchmarks",
59
  "label": "Datasets and benchmarks",
60
  "featured": false,
61
+ "count": 9,
62
  "json_url": "https://agentpaywire.com/api/library/datasets-benchmarks.json",
63
  "markdown_url": "https://agentpaywire.com/library/datasets-benchmarks.md",
64
  "html_url": "https://agentpaywire.com/library/datasets-benchmarks/"
 
76
  "id": "regulation",
77
  "label": "Regulation",
78
  "featured": false,
79
+ "count": 4,
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/"
83
  }
84
  ],
85
  "entries": [
86
+ {
87
+ "id": "aperture-v0-6-0-release",
88
+ "title": "Aperture v0.6.0",
89
+ "publisher": "Lightning Labs",
90
+ "authors": [],
91
+ "date_published": "2026-11-05",
92
+ "url": "https://github.com/lightninglabs/aperture/releases/tag/v0.6.0",
93
+ "type": "repo",
94
+ "category": "bitcoin-lightning",
95
+ "status": "product_docs",
96
+ "summary": "Release published 2026-11-05, not a prerelease. Metered pricing is opt-in per service (metered: true). A price server is called at GetPrice, ChallengeMinted, AuthorizeRequest, and ReportUsage. The release includes meterd, a reference price server, and the pricesrpc interface. docs/metering.md at tag v0.6.0 names the same four calls. The release says invoices can be minted from a Wavelength wallet instead of lnd, so a seller needs no node of their own. docs/wavelength.md at that tag describes invoices from a Wavelength wallet and also says the Wavelength backend is not in an Aperture release yet. A service with auth: l402+mpp answers an unpaid request with one 402 that carries both an L402 and a Payment challenge. Hardening includes a Payment-Receipt only for a credential that authenticated the request, TLS 1.2 or newer, and path canonicalization before authorization. The Upgrading section lists changes that can break an existing deployment. enablempp is refused at startup with the etcd backend; sqlite or postgres is required. A static price of 0 means the default price of 1 sat, not free. This replaces the lightninglabs-aperture-github row. Metering: https://github.com/lightninglabs/aperture/blob/v0.6.0/docs/metering.md. Wavelength: https://github.com/lightninglabs/aperture/blob/v0.6.0/docs/wavelength.md.",
97
+ "tags": [
98
+ "l402",
99
+ "lightning",
100
+ "m2m-payments",
101
+ "release"
102
+ ],
103
+ "verified_at": "2026-11-05",
104
+ "featured": true,
105
+ "last_checked": "2026-11-05",
106
+ "http_status": 200,
107
+ "archive_url": null
108
+ },
109
+ {
110
+ "id": "core-lightning-v26-06-10",
111
+ "title": "Core Lightning v26.06.10",
112
+ "publisher": "Elements Project",
113
+ "authors": [],
114
+ "date_published": "2026-11-04",
115
+ "url": "https://github.com/ElementsProject/lightning/releases/tag/v26.06.10",
116
+ "type": "repo",
117
+ "category": "bitcoin-lightning",
118
+ "status": "product_docs",
119
+ "summary": "Security point release published 2026-11-04T13:34:33Z, not a prerelease. The notes say it includes fixes for vulnerabilities and that the maintainers strongly recommend upgrading. The highlighted security fixes cover dual funding and splicing, including signature checks on the peer's tx_signatures, onchaind HTLC resolution, gossip resource limits, connectd, runes and commando, plugin hooks and hsmd. A peer dust_limit_satoshis above 5000 sat is refused. The notes recommend binding commando runes to a node id with an id restriction, and rotating unaccounted runes by blacklisting them and issuing new ones. The notes name no CVE. The changelog heading linked from the release is dated 2026-11-05. The release notes do not name Blockstream.",
120
+ "tags": [
121
+ "lightning",
122
+ "release",
123
+ "security"
124
+ ],
125
+ "verified_at": "2026-11-05",
126
+ "featured": true,
127
+ "last_checked": "2026-11-05",
128
+ "http_status": 200,
129
+ "archive_url": null
130
+ },
131
  {
132
  "id": "wavelength-v0-2-1-release",
133
  "title": "Wavelength v0.2.1",
 
722
  "http_status": 200,
723
  "archive_url": "http://web.archive.org/web/20260610015121/https://github.com/lightninglabs/L402"
724
  },
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
725
  {
726
  "id": "lightninglabs-langchainbitcoin-github",
727
  "title": "lightninglabs/LangChainBitcoin",
 
3695
  "http_status": 200,
3696
  "archive_url": "http://web.archive.org/web/20260905225407/https://robotics-transformer-x.github.io/"
3697
  },
3698
+ {
3699
+ "id": "agent-money-benchmark-v1",
3700
+ "title": "Agent Money Benchmark v1",
3701
+ "publisher": "BlockRun",
3702
+ "authors": [],
3703
+ "date_published": null,
3704
+ "url": "https://agentmoneybench.com/",
3705
+ "type": "docs",
3706
+ "category": "datasets-benchmarks",
3707
+ "status": "product_docs",
3708
+ "summary": "Version 1 vendor benchmark from BlockRun. The site says 10 frontier models were given wallets, settlement is Solana mainnet, and purchases are real USDC on-chain. Tracks are Financial Research and Adversarial Marketplace. It says 7 of 10 models paid a cheating seller at least once. Trap columns are Charged again after payment, Price above listed, Expired quote, Wrong data delivered, Paid, not delivered, Lookalike payee, Receipt mismatch, and Hidden instructions. The site says the gateway is BlockRun's and does not name x402. It says the full task set, rubrics, and run records are private. BlockRun-authored materials are CC BY-NC 4.0 for noncommercial use with attribution, and commercial use needs written permission. The site dates the run 27-29 Oct 2026 and does not state a publication date. Repository: https://github.com/BlockRunAI/agent-money-bench. Dataset: https://huggingface.co/datasets/BlockRunAI/agent-money-bench, whose card license is cc-by-nc-4.0.",
3709
+ "tags": [
3710
+ "benchmark",
3711
+ "dataset",
3712
+ "stablecoins"
3713
+ ],
3714
+ "verified_at": "2026-11-05",
3715
+ "featured": false,
3716
+ "last_checked": "2026-11-05",
3717
+ "http_status": 200,
3718
+ "archive_url": null
3719
+ },
3720
  {
3721
  "id": "arxiv-2610-35835-i-hitl",
3722
  "title": "I-HITL: Inalienable Human-in-the-Loop",
 
3941
  "http_status": 200,
3942
  "archive_url": "http://web.archive.org/web/20261016132319/https://genai.owasp.org/llm-top-10/"
3943
  },
3944
+ {
3945
+ "id": "occ-bulletin-2026-54",
3946
+ "title": "OCC Bulletin 2026-54: Super Intelligence: Supervisory Framework",
3947
+ "publisher": "Office of the Comptroller of the Currency",
3948
+ "authors": [
3949
+ "James M. Gallagher"
3950
+ ],
3951
+ "date_published": "2026-11-04",
3952
+ "url": "https://www.occ.gov/news-issuances/bulletins/2026/bulletin-2026-54.html",
3953
+ "type": "regulatory",
3954
+ "category": "regulation",
3955
+ "status": "product_docs",
3956
+ "summary": "OCC Bulletin 2026-54, dated November 4, 2026, signed by James M. Gallagher, Senior Deputy Comptroller and Chief National Bank Examiner. It issues a supervisory framework for OCC examiners evaluating national banks' use of super intelligence in normal-course business activities. The bulletin says it does not establish supervisory expectations for banks and is not intended to establish new regulatory expectations or prescriptive requirements. It says examiners should not treat super intelligence as a separate and distinct risk category, and banks are not required to define a separate SI risk appetite. It says a bank's risk classification of SI use cases may be based on potential consequences, transfer of agency, and the degree of human oversight rather than the technical sophistication of the SI used. The bulletin links a PDF that was not read.",
3957
+ "tags": [
3958
+ "regulation"
3959
+ ],
3960
+ "verified_at": "2026-11-05",
3961
+ "featured": false,
3962
+ "last_checked": "2026-11-05",
3963
+ "http_status": 200,
3964
+ "archive_url": null
3965
+ },
3966
  {
3967
  "id": "occ-bulletin-2026-50-genius-act",
3968
  "title": "GENIUS Act Regulations: Final Rule",
data/protocol-facts.json CHANGED
@@ -1,6 +1,6 @@
1
  {
2
  "schema_version": "1",
3
- "generated_at": "2026-11-04T00:00:00Z",
4
  "disclaimer": {
5
  "text": "Not investment advice.",
6
  "url": "https://agentpaywire.com/disclaimer.json"
@@ -88,6 +88,11 @@
88
  "source": "https://docs.lightning.engineering/the-lightning-network/l402/protocol-specification",
89
  "verified_at": "2026-10-20"
90
  },
 
 
 
 
 
91
  "example": {
92
  "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.",
93
  "source": "https://agentpaywire.com/.well-known/l402",
@@ -505,6 +510,11 @@
505
  "value": "The challenges page uses 0x20c0000000000000000000006a37DA5C996874BE as an OUSD-on-Tempo example and says the sample identifiers are illustrative. This file does not treat that address as a canonical contract. CAIP-2 is not stated there.",
506
  "source": "https://mpp.dev/protocol/challenges",
507
  "verified_at": "2026-10-20"
 
 
 
 
 
508
  }
509
  },
510
  {
 
1
  {
2
  "schema_version": "1",
3
+ "generated_at": "2026-11-05T00:00:00Z",
4
  "disclaimer": {
5
  "text": "Not investment advice.",
6
  "url": "https://agentpaywire.com/disclaimer.json"
 
88
  "source": "https://docs.lightning.engineering/the-lightning-network/l402/protocol-specification",
89
  "verified_at": "2026-10-20"
90
  },
91
+ "implementation": {
92
+ "value": "Aperture v0.6.0, published 2026-11-05 and not a prerelease, says a service with auth: l402+mpp answers an unpaid request with one 402 that carries both an L402 and a Payment challenge, and accepts either. MPP charges and sessions stay opt-in (enablempp, enablesessions). enablempp is refused at startup with the etcd backend; sqlite or postgres is required. A static price of 0 means the default price of 1 sat, not free.",
93
+ "source": "https://github.com/lightninglabs/aperture/releases/tag/v0.6.0",
94
+ "verified_at": "2026-11-05"
95
+ },
96
  "example": {
97
  "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.",
98
  "source": "https://agentpaywire.com/.well-known/l402",
 
510
  "value": "The challenges page uses 0x20c0000000000000000000006a37DA5C996874BE as an OUSD-on-Tempo example and says the sample identifiers are illustrative. This file does not treat that address as a canonical contract. CAIP-2 is not stated there.",
511
  "source": "https://mpp.dev/protocol/challenges",
512
  "verified_at": "2026-10-20"
513
+ },
514
+ "implementation": {
515
+ "value": "Aperture v0.6.0, published 2026-11-05 and not a prerelease, says a service with auth: l402+mpp answers an unpaid request with one 402 that carries both an L402 and a Payment challenge, and accepts either. MPP charges and sessions stay opt-in (enablempp, enablesessions). enablempp is refused at startup with the etcd backend; sqlite or postgres is required. A static price of 0 means the default price of 1 sat, not free.",
516
+ "source": "https://github.com/lightninglabs/aperture/releases/tag/v0.6.0",
517
+ "verified_at": "2026-11-05"
518
  }
519
  },
520
  {
data/sources.csv CHANGED
@@ -1,4 +1,6 @@
1
  id,title,publisher,authors,date_published,url,type,category,status,summary,tags,verified_at,featured,last_checked,http_status,archive_url
 
 
2
  wavelength-v0-2-1-release,Wavelength v0.2.1,Lightning Labs (GitHub),,2026-10-31,https://github.com/lightninglabs/wavelength/releases/tag/v0.2.1,repo,bitcoin-lightning,spec_released,"Release published 2026-10-31, not a prerelease. The notes say changes are since v0.2.0. Clients validate Ark transaction inputs before accepting out-of-round transfers. Linux builds disable MPTCP listeners by default, and the notes say this does not replace installing a patched kernel. Received VTXO expiry timing is derived from locally confirmed chain evidence. Pay swaps reject excessive refund timelocks before funding, refund intent survives interruptions, and payments that would leave unusably small change fail promptly. Exit recovery preserves the spending policy and funding proofs. Binaries are built with Go 1.27.3. The release body says maintainers must sign manifest-v0.2.1.txt before publishing. Full changelog: https://github.com/lightninglabs/wavelength/compare/v0.2.0...v0.2.1.",lightning; ark; wallet; release,2026-11-03,true,2026-11-03,200,
3
  lnd-v0-21-6-beta,lnd v0.21.6-beta and v0.20.7-beta,Lightning Labs (GitHub),,2026-10-30,https://github.com/lightningnetwork/lnd/releases/tag/v0.21.6-beta,repo,bitcoin-lightning,product_docs,"Security releases published 2026-10-30. v0.21.6-beta at 23:21 UTC is the newest non-prerelease on the 0.21 line. v0.20.7-beta at 22:37 UTC is the matching 0.20 tag. Both release bodies name CVE-2026-98432 and say there are no database migrations. The v0.21.6 notes say the demonstrated exploit needs an MPTCP listener, which Go 1.24+ enables by default, that Windows and macOS are not affected, and that lnd no longer opens MPTCP listeners. They tell Linux operators to upgrade, set net.mptcp.enabled=0, and install a patched kernel, and to start an unupgraded binary with GODEBUG=multipathtcp=0. The notes do not name kernel version numbers. This replaces the library row for v0.21.5-beta. Notes: https://github.com/lightningnetwork/lnd/blob/v0.21.6-beta/docs/release-notes/release-notes-0.21.6.md. The 0.20 tag: https://github.com/lightningnetwork/lnd/releases/tag/v0.20.7-beta.",lnd; lightning; release; security,2026-11-03,true,2026-11-03,200,
4
  bitcoin-optech-newsletter-429,Bitcoin Optech Newsletter #429,Bitcoin Optech,,2026-10-30,https://bitcoinops.org/en/newsletters/2026/10/30/,report,bitcoin-lightning,news,"Newsletter dated 2026-10-30. It discloses a denial-of-service in Core Lightning 25.02 through 26.04: a channel announcement that names the same node as both endpoints passed validation, was stored, and then crashed gossipd on a no-duplicates assertion. The stored message crashed the node again on every restart until the operator removed it by hand, which upgrading alone did not do. The fix is CLN 26.04.1, which rejects an announcement whose node_id_1 is not strictly less than node_id_2. BOLTs #1333 added the same receiver check to BOLT7, which had only required senders to order the IDs.",bitcoin; lightning; security; optech,2026-10-31,true,2026-10-31,200,
@@ -23,7 +25,6 @@ lightning-agent-tools-github,lightninglabs/lightning-agent-tools,GitHub (Lightni
23
  lightning-labs-l402-builders-guide,L402: Lightning HTTP 402 Protocol,Lightning Labs (Builder's Guide),,,https://docs.lightning.engineering/the-lightning-network/l402,docs,bitcoin-lightning,product_docs,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.,l402; lightning; m2m-payments; micropayments,2026-10-20,true,2026-10-20,200,http://web.archive.org/web/20261009034701/https://docs.lightning.engineering/the-lightning-network/l402
24
  lightning-labs-l402-protocol-specification,L402 Protocol Specification,Lightning Labs (Builder's Guide),,,https://docs.lightning.engineering/the-lightning-network/l402/protocol-specification,spec,bitcoin-lightning,spec_released,"Specification of the abstract L402 HTTP and gRPC protocols. It defines the ""L402"" authentication scheme, which carries credentials as macaroon:preimage pairs.",l402; lightning; macaroons; identity,2026-10-20,true,2026-10-20,200,http://web.archive.org/web/20260702152123/https://docs.lightning.engineering/the-lightning-network/l402/protocol-specification
25
  lightninglabs-l402-github,lightninglabs/L402,GitHub (Lightning Labs),,,https://github.com/lightninglabs/L402,repo,bitcoin-lightning,product_docs,"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.",l402; lightning; macaroons; m2m-payments,2026-10-20,true,2026-10-20,200,http://web.archive.org/web/20260610015121/https://github.com/lightninglabs/L402
26
- lightninglabs-aperture-github,lightninglabs/aperture,GitHub (Lightning Labs),,,https://github.com/lightninglabs/aperture,repo,bitcoin-lightning,product_docs,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.,l402; lightning; m2m-payments,2026-10-20,true,2026-10-20,200,http://web.archive.org/web/20250812194102/https://github.com/lightninglabs/aperture
27
  lightninglabs-langchainbitcoin-github,lightninglabs/LangChainBitcoin,GitHub (Lightning Labs),,,https://github.com/lightninglabs/LangChainBitcoin,repo,bitcoin-lightning,product_docs,"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.",lightning; l402; bitcoin; agent-wallets,2026-10-20,true,2026-10-20,200,http://web.archive.org/web/20250714041334/https://github.com/lightninglabs/LangChainBitcoin
28
  lightning-bolts-github,lightning/bolts: BOLT: Basis of Lightning Technology (Lightning Network Specifications),GitHub (lightning),,,https://github.com/lightning/bolts,spec,bitcoin-lightning,spec_released,"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.",lightning; bitcoin; m2m-payments,2026-10-20,true,2026-10-20,200,http://web.archive.org/web/20260704121535/https://github.com/lightning/bolts
29
  bolt-11-invoice-protocol,BOLT #11: Invoice Protocol for Lightning Payments,GitHub (lightning/bolts),,,https://github.com/lightning/bolts/blob/master/11-payment-encoding.md,spec,bitcoin-lightning,spec_released,"Lightning specification for a simple, extendable, QR-code-ready protocol for requesting payments over Lightning (BOLT 11 invoices).",lightning; bitcoin; micropayments,2026-10-20,true,2026-10-20,200,http://web.archive.org/web/20261016083441/https://github.com/lightning/bolts/blob/master/11-payment-encoding.md
@@ -157,6 +158,7 @@ swe-bench-paper,SWE-bench: Can Language Models Resolve Real-World GitHub Issues?
157
  webarena,WebArena: A Realistic Web Environment for Building Autonomous Agents,arXiv,Shuyan Zhou; Frank F. Xu; Hao Zhu; Xuhui Zhou; Robert Lo; Abishek Sridhar; Xianyi Cheng; Tianyue Ou; Yonatan Bisk; Daniel Fried; Uri Alon; Graham Neubig,2023-07-25,https://arxiv.org/abs/2307.13854,research-paper,datasets-benchmarks,research,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.,benchmark; web-agents; research,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261002191854/https://arxiv.org/abs/2307.13854
158
  swe-bench-leaderboards,SWE-bench Leaderboards,SWE-bench,,,https://www.swebench.com/,docs,datasets-benchmarks,product_docs,"Official SWE-bench site with leaderboards for SWE-bench, Verified, Multilingual, Multimodal and Lite variants, plus related tools.",benchmark; leaderboard,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261019081426/https://www.swebench.com/
159
  open-x-embodiment,Open X-Embodiment: Robotic Learning Datasets and RT-X Models,Open X-Embodiment Collaboration,,,https://robotics-transformer-x.github.io/,docs,datasets-benchmarks,product_docs,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.,dataset; robotics,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20260905225407/https://robotics-transformer-x.github.io/
 
160
  arxiv-2610-35835-i-hitl,I-HITL: Inalienable Human-in-the-Loop,arXiv,Samuel Breckenridge; Dani Vilardell; Wenhao Wang; Fan Zhang; Ari Juels,2026-10-26,https://arxiv.org/abs/2610.35835,research-paper,safety-security,research,"arXiv 2610.35835, submitted 2026-10-26 and revised 2026-10-30 (v3). The abstract says an experiment on a popular agentic wallet platform required an emailed one-time passcode to raise a spending cap. With access to that email and a task blocked by the cap, ten frontier models often harvested the passcode and raised the cap. It says an I-HITL protocol requires a trusted computing device, and presents Countersign, a prototype that uses off-the-shelf consumer mobile devices. The abstract does not name the wallet vendor. GitHub repository https://github.com/I-HITL/countersign describes itself as a mobile phone-based implementation and is MIT licensed. The CoinDesk URL in the candidate file returned HTTP 429 on 2026-11-03 and was not read.",security; research; agent-wallets,2026-11-03,,2026-11-03,200,
161
  v12-x402-25-vulnerabilities,25 Vulnerabilities in the x402 Protocol: Inside Three Critical Findings,V12,,2026-10-22,https://v12.sh/blog/x402,report,safety-security,research,"V12 reports 25 vulnerabilities in the x402 codebase and details three critical ones: a Solana token approval accepted as payment by the TypeScript facilitator, SIWx login messages signed for a different site, and a default client with no spending limit. All three were reported on 2026-08-12 and fixed by 2026-08-20. According to The Hacker News (2026-10-23), the fixes are in @x402/fetch, @x402/axios, @x402/extensions and @x402/svm 2.23.0 or later, patched clients cap each payment at $1 and accept only recognized stablecoins by default (spendControls: false disables this), and no formal security advisory was published. Related: https://thehackernews.com/2026/10/critical-x402-sdk-flaw-could-let.html.",x402; security; vulnerabilities; spend-controls; siwx; solana; sdk,2026-10-24,,2026-10-24,200,
162
  cloudflare-verified-bots-continuous-accountability,Continuous accountability for Verified bots,Cloudflare,,2026-10-16,https://blog.cloudflare.com/verified-bots-accountability/,announcement,safety-security,news,"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.",identity; web-agents; security; http,2026-10-21,,2026-10-21,200,
@@ -166,6 +168,7 @@ arxiv-formal-analysis-agent-payment-protocols,A Formal Analysis of Agent Payment
166
  owasp-top-10-agentic-applications-2026,OWASP Top 10 for Agentic Applications for 2026,OWASP Gen AI Security Project,,2025-12-10,https://genai.owasp.org/resource/owasp-top-10-for-agentic-applications-for-2026/,report,safety-security,spec_released,"Peer-reviewed framework, developed with more than 100 experts, identifying the most critical security risks facing autonomous and agentic AI systems.",owasp; security; agents,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261016132319/https://genai.owasp.org/resource/owasp-top-10-for-agentic-applications-for-2026/
167
  nist-ai-rmf-1-0,Artificial Intelligence Risk Management Framework (AI RMF 1.0),NIST,Elham Tabassi,2023-01-26,https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-ai-rmf-10,spec,safety-security,spec_released,"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.",ai-risk; standards; security,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261005065247/https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-ai-rmf-10
168
  owasp-top-10-llm-2025,OWASP Top 10 for LLM Applications (2025),OWASP Gen AI Security Project,,,https://genai.owasp.org/llm-top-10/,report,safety-security,spec_released,"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.",owasp; security; prompt-injection,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261016132319/https://genai.owasp.org/llm-top-10/
 
169
  occ-bulletin-2026-50-genius-act,GENIUS Act Regulations: Final Rule,Office of the Comptroller of the Currency,,2026-10-21,https://www.occ.gov/news-issuances/bulletins/2026/bulletin-2026-50.html,regulatory,regulation,standard,"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.",regulation; stablecoins,2026-10-23,,2026-10-23,200,
170
  fsb-sound-practices-responsible-ai-adoption-final,Sound Practices for Responsible Adoption of Artificial Intelligence (AI): Final report,Financial Stability Board,,2026-10-15,https://www.fsb.org/2026/10/sound-practices-for-responsible-adoption-of-artificial-intelligence-ai-final-report/,report,regulation,research,"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.",regulation; ai-risk; agents,2026-10-21,,2026-10-21,200,
171
  eu-ai-act-commission-page,AI Act,European Commission (Shaping Europe's digital future),,,https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai,regulatory,regulation,standard,"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.",eu-ai-act; regulation,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261016150532/https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai
 
1
  id,title,publisher,authors,date_published,url,type,category,status,summary,tags,verified_at,featured,last_checked,http_status,archive_url
2
+ aperture-v0-6-0-release,Aperture v0.6.0,Lightning Labs,,2026-11-05,https://github.com/lightninglabs/aperture/releases/tag/v0.6.0,repo,bitcoin-lightning,product_docs,"Release published 2026-11-05, not a prerelease. Metered pricing is opt-in per service (metered: true). A price server is called at GetPrice, ChallengeMinted, AuthorizeRequest, and ReportUsage. The release includes meterd, a reference price server, and the pricesrpc interface. docs/metering.md at tag v0.6.0 names the same four calls. The release says invoices can be minted from a Wavelength wallet instead of lnd, so a seller needs no node of their own. docs/wavelength.md at that tag describes invoices from a Wavelength wallet and also says the Wavelength backend is not in an Aperture release yet. A service with auth: l402+mpp answers an unpaid request with one 402 that carries both an L402 and a Payment challenge. Hardening includes a Payment-Receipt only for a credential that authenticated the request, TLS 1.2 or newer, and path canonicalization before authorization. The Upgrading section lists changes that can break an existing deployment. enablempp is refused at startup with the etcd backend; sqlite or postgres is required. A static price of 0 means the default price of 1 sat, not free. This replaces the lightninglabs-aperture-github row. Metering: https://github.com/lightninglabs/aperture/blob/v0.6.0/docs/metering.md. Wavelength: https://github.com/lightninglabs/aperture/blob/v0.6.0/docs/wavelength.md.",l402; lightning; m2m-payments; release,2026-11-05,true,2026-11-05,200,
3
+ core-lightning-v26-06-10,Core Lightning v26.06.10,Elements Project,,2026-11-04,https://github.com/ElementsProject/lightning/releases/tag/v26.06.10,repo,bitcoin-lightning,product_docs,"Security point release published 2026-11-04T13:34:33Z, not a prerelease. The notes say it includes fixes for vulnerabilities and that the maintainers strongly recommend upgrading. The highlighted security fixes cover dual funding and splicing, including signature checks on the peer's tx_signatures, onchaind HTLC resolution, gossip resource limits, connectd, runes and commando, plugin hooks and hsmd. A peer dust_limit_satoshis above 5000 sat is refused. The notes recommend binding commando runes to a node id with an id restriction, and rotating unaccounted runes by blacklisting them and issuing new ones. The notes name no CVE. The changelog heading linked from the release is dated 2026-11-05. The release notes do not name Blockstream.",lightning; release; security,2026-11-05,true,2026-11-05,200,
4
  wavelength-v0-2-1-release,Wavelength v0.2.1,Lightning Labs (GitHub),,2026-10-31,https://github.com/lightninglabs/wavelength/releases/tag/v0.2.1,repo,bitcoin-lightning,spec_released,"Release published 2026-10-31, not a prerelease. The notes say changes are since v0.2.0. Clients validate Ark transaction inputs before accepting out-of-round transfers. Linux builds disable MPTCP listeners by default, and the notes say this does not replace installing a patched kernel. Received VTXO expiry timing is derived from locally confirmed chain evidence. Pay swaps reject excessive refund timelocks before funding, refund intent survives interruptions, and payments that would leave unusably small change fail promptly. Exit recovery preserves the spending policy and funding proofs. Binaries are built with Go 1.27.3. The release body says maintainers must sign manifest-v0.2.1.txt before publishing. Full changelog: https://github.com/lightninglabs/wavelength/compare/v0.2.0...v0.2.1.",lightning; ark; wallet; release,2026-11-03,true,2026-11-03,200,
5
  lnd-v0-21-6-beta,lnd v0.21.6-beta and v0.20.7-beta,Lightning Labs (GitHub),,2026-10-30,https://github.com/lightningnetwork/lnd/releases/tag/v0.21.6-beta,repo,bitcoin-lightning,product_docs,"Security releases published 2026-10-30. v0.21.6-beta at 23:21 UTC is the newest non-prerelease on the 0.21 line. v0.20.7-beta at 22:37 UTC is the matching 0.20 tag. Both release bodies name CVE-2026-98432 and say there are no database migrations. The v0.21.6 notes say the demonstrated exploit needs an MPTCP listener, which Go 1.24+ enables by default, that Windows and macOS are not affected, and that lnd no longer opens MPTCP listeners. They tell Linux operators to upgrade, set net.mptcp.enabled=0, and install a patched kernel, and to start an unupgraded binary with GODEBUG=multipathtcp=0. The notes do not name kernel version numbers. This replaces the library row for v0.21.5-beta. Notes: https://github.com/lightningnetwork/lnd/blob/v0.21.6-beta/docs/release-notes/release-notes-0.21.6.md. The 0.20 tag: https://github.com/lightningnetwork/lnd/releases/tag/v0.20.7-beta.",lnd; lightning; release; security,2026-11-03,true,2026-11-03,200,
6
  bitcoin-optech-newsletter-429,Bitcoin Optech Newsletter #429,Bitcoin Optech,,2026-10-30,https://bitcoinops.org/en/newsletters/2026/10/30/,report,bitcoin-lightning,news,"Newsletter dated 2026-10-30. It discloses a denial-of-service in Core Lightning 25.02 through 26.04: a channel announcement that names the same node as both endpoints passed validation, was stored, and then crashed gossipd on a no-duplicates assertion. The stored message crashed the node again on every restart until the operator removed it by hand, which upgrading alone did not do. The fix is CLN 26.04.1, which rejects an announcement whose node_id_1 is not strictly less than node_id_2. BOLTs #1333 added the same receiver check to BOLT7, which had only required senders to order the IDs.",bitcoin; lightning; security; optech,2026-10-31,true,2026-10-31,200,
 
25
  lightning-labs-l402-builders-guide,L402: Lightning HTTP 402 Protocol,Lightning Labs (Builder's Guide),,,https://docs.lightning.engineering/the-lightning-network/l402,docs,bitcoin-lightning,product_docs,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.,l402; lightning; m2m-payments; micropayments,2026-10-20,true,2026-10-20,200,http://web.archive.org/web/20261009034701/https://docs.lightning.engineering/the-lightning-network/l402
26
  lightning-labs-l402-protocol-specification,L402 Protocol Specification,Lightning Labs (Builder's Guide),,,https://docs.lightning.engineering/the-lightning-network/l402/protocol-specification,spec,bitcoin-lightning,spec_released,"Specification of the abstract L402 HTTP and gRPC protocols. It defines the ""L402"" authentication scheme, which carries credentials as macaroon:preimage pairs.",l402; lightning; macaroons; identity,2026-10-20,true,2026-10-20,200,http://web.archive.org/web/20260702152123/https://docs.lightning.engineering/the-lightning-network/l402/protocol-specification
27
  lightninglabs-l402-github,lightninglabs/L402,GitHub (Lightning Labs),,,https://github.com/lightninglabs/L402,repo,bitcoin-lightning,product_docs,"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.",l402; lightning; macaroons; m2m-payments,2026-10-20,true,2026-10-20,200,http://web.archive.org/web/20260610015121/https://github.com/lightninglabs/L402
 
28
  lightninglabs-langchainbitcoin-github,lightninglabs/LangChainBitcoin,GitHub (Lightning Labs),,,https://github.com/lightninglabs/LangChainBitcoin,repo,bitcoin-lightning,product_docs,"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.",lightning; l402; bitcoin; agent-wallets,2026-10-20,true,2026-10-20,200,http://web.archive.org/web/20250714041334/https://github.com/lightninglabs/LangChainBitcoin
29
  lightning-bolts-github,lightning/bolts: BOLT: Basis of Lightning Technology (Lightning Network Specifications),GitHub (lightning),,,https://github.com/lightning/bolts,spec,bitcoin-lightning,spec_released,"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.",lightning; bitcoin; m2m-payments,2026-10-20,true,2026-10-20,200,http://web.archive.org/web/20260704121535/https://github.com/lightning/bolts
30
  bolt-11-invoice-protocol,BOLT #11: Invoice Protocol for Lightning Payments,GitHub (lightning/bolts),,,https://github.com/lightning/bolts/blob/master/11-payment-encoding.md,spec,bitcoin-lightning,spec_released,"Lightning specification for a simple, extendable, QR-code-ready protocol for requesting payments over Lightning (BOLT 11 invoices).",lightning; bitcoin; micropayments,2026-10-20,true,2026-10-20,200,http://web.archive.org/web/20261016083441/https://github.com/lightning/bolts/blob/master/11-payment-encoding.md
 
158
  webarena,WebArena: A Realistic Web Environment for Building Autonomous Agents,arXiv,Shuyan Zhou; Frank F. Xu; Hao Zhu; Xuhui Zhou; Robert Lo; Abishek Sridhar; Xianyi Cheng; Tianyue Ou; Yonatan Bisk; Daniel Fried; Uri Alon; Graham Neubig,2023-07-25,https://arxiv.org/abs/2307.13854,research-paper,datasets-benchmarks,research,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.,benchmark; web-agents; research,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261002191854/https://arxiv.org/abs/2307.13854
159
  swe-bench-leaderboards,SWE-bench Leaderboards,SWE-bench,,,https://www.swebench.com/,docs,datasets-benchmarks,product_docs,"Official SWE-bench site with leaderboards for SWE-bench, Verified, Multilingual, Multimodal and Lite variants, plus related tools.",benchmark; leaderboard,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261019081426/https://www.swebench.com/
160
  open-x-embodiment,Open X-Embodiment: Robotic Learning Datasets and RT-X Models,Open X-Embodiment Collaboration,,,https://robotics-transformer-x.github.io/,docs,datasets-benchmarks,product_docs,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.,dataset; robotics,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20260905225407/https://robotics-transformer-x.github.io/
161
+ agent-money-benchmark-v1,Agent Money Benchmark v1,BlockRun,,,https://agentmoneybench.com/,docs,datasets-benchmarks,product_docs,"Version 1 vendor benchmark from BlockRun. The site says 10 frontier models were given wallets, settlement is Solana mainnet, and purchases are real USDC on-chain. Tracks are Financial Research and Adversarial Marketplace. It says 7 of 10 models paid a cheating seller at least once. Trap columns are Charged again after payment, Price above listed, Expired quote, Wrong data delivered, Paid, not delivered, Lookalike payee, Receipt mismatch, and Hidden instructions. The site says the gateway is BlockRun's and does not name x402. It says the full task set, rubrics, and run records are private. BlockRun-authored materials are CC BY-NC 4.0 for noncommercial use with attribution, and commercial use needs written permission. The site dates the run 27-29 Oct 2026 and does not state a publication date. Repository: https://github.com/BlockRunAI/agent-money-bench. Dataset: https://huggingface.co/datasets/BlockRunAI/agent-money-bench, whose card license is cc-by-nc-4.0.",benchmark; dataset; stablecoins,2026-11-05,,2026-11-05,200,
162
  arxiv-2610-35835-i-hitl,I-HITL: Inalienable Human-in-the-Loop,arXiv,Samuel Breckenridge; Dani Vilardell; Wenhao Wang; Fan Zhang; Ari Juels,2026-10-26,https://arxiv.org/abs/2610.35835,research-paper,safety-security,research,"arXiv 2610.35835, submitted 2026-10-26 and revised 2026-10-30 (v3). The abstract says an experiment on a popular agentic wallet platform required an emailed one-time passcode to raise a spending cap. With access to that email and a task blocked by the cap, ten frontier models often harvested the passcode and raised the cap. It says an I-HITL protocol requires a trusted computing device, and presents Countersign, a prototype that uses off-the-shelf consumer mobile devices. The abstract does not name the wallet vendor. GitHub repository https://github.com/I-HITL/countersign describes itself as a mobile phone-based implementation and is MIT licensed. The CoinDesk URL in the candidate file returned HTTP 429 on 2026-11-03 and was not read.",security; research; agent-wallets,2026-11-03,,2026-11-03,200,
163
  v12-x402-25-vulnerabilities,25 Vulnerabilities in the x402 Protocol: Inside Three Critical Findings,V12,,2026-10-22,https://v12.sh/blog/x402,report,safety-security,research,"V12 reports 25 vulnerabilities in the x402 codebase and details three critical ones: a Solana token approval accepted as payment by the TypeScript facilitator, SIWx login messages signed for a different site, and a default client with no spending limit. All three were reported on 2026-08-12 and fixed by 2026-08-20. According to The Hacker News (2026-10-23), the fixes are in @x402/fetch, @x402/axios, @x402/extensions and @x402/svm 2.23.0 or later, patched clients cap each payment at $1 and accept only recognized stablecoins by default (spendControls: false disables this), and no formal security advisory was published. Related: https://thehackernews.com/2026/10/critical-x402-sdk-flaw-could-let.html.",x402; security; vulnerabilities; spend-controls; siwx; solana; sdk,2026-10-24,,2026-10-24,200,
164
  cloudflare-verified-bots-continuous-accountability,Continuous accountability for Verified bots,Cloudflare,,2026-10-16,https://blog.cloudflare.com/verified-bots-accountability/,announcement,safety-security,news,"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.",identity; web-agents; security; http,2026-10-21,,2026-10-21,200,
 
168
  owasp-top-10-agentic-applications-2026,OWASP Top 10 for Agentic Applications for 2026,OWASP Gen AI Security Project,,2025-12-10,https://genai.owasp.org/resource/owasp-top-10-for-agentic-applications-for-2026/,report,safety-security,spec_released,"Peer-reviewed framework, developed with more than 100 experts, identifying the most critical security risks facing autonomous and agentic AI systems.",owasp; security; agents,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261016132319/https://genai.owasp.org/resource/owasp-top-10-for-agentic-applications-for-2026/
169
  nist-ai-rmf-1-0,Artificial Intelligence Risk Management Framework (AI RMF 1.0),NIST,Elham Tabassi,2023-01-26,https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-ai-rmf-10,spec,safety-security,spec_released,"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.",ai-risk; standards; security,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261005065247/https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-ai-rmf-10
170
  owasp-top-10-llm-2025,OWASP Top 10 for LLM Applications (2025),OWASP Gen AI Security Project,,,https://genai.owasp.org/llm-top-10/,report,safety-security,spec_released,"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.",owasp; security; prompt-injection,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261016132319/https://genai.owasp.org/llm-top-10/
171
+ occ-bulletin-2026-54,OCC Bulletin 2026-54: Super Intelligence: Supervisory Framework,Office of the Comptroller of the Currency,James M. Gallagher,2026-11-04,https://www.occ.gov/news-issuances/bulletins/2026/bulletin-2026-54.html,regulatory,regulation,product_docs,"OCC Bulletin 2026-54, dated November 4, 2026, signed by James M. Gallagher, Senior Deputy Comptroller and Chief National Bank Examiner. It issues a supervisory framework for OCC examiners evaluating national banks' use of super intelligence in normal-course business activities. The bulletin says it does not establish supervisory expectations for banks and is not intended to establish new regulatory expectations or prescriptive requirements. It says examiners should not treat super intelligence as a separate and distinct risk category, and banks are not required to define a separate SI risk appetite. It says a bank's risk classification of SI use cases may be based on potential consequences, transfer of agency, and the degree of human oversight rather than the technical sophistication of the SI used. The bulletin links a PDF that was not read.",regulation,2026-11-05,,2026-11-05,200,
172
  occ-bulletin-2026-50-genius-act,GENIUS Act Regulations: Final Rule,Office of the Comptroller of the Currency,,2026-10-21,https://www.occ.gov/news-issuances/bulletins/2026/bulletin-2026-50.html,regulatory,regulation,standard,"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.",regulation; stablecoins,2026-10-23,,2026-10-23,200,
173
  fsb-sound-practices-responsible-ai-adoption-final,Sound Practices for Responsible Adoption of Artificial Intelligence (AI): Final report,Financial Stability Board,,2026-10-15,https://www.fsb.org/2026/10/sound-practices-for-responsible-adoption-of-artificial-intelligence-ai-final-report/,report,regulation,research,"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.",regulation; ai-risk; agents,2026-10-21,,2026-10-21,200,
174
  eu-ai-act-commission-page,AI Act,European Commission (Shaping Europe's digital future),,,https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai,regulatory,regulation,standard,"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.",eu-ai-act; regulation,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261016150532/https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai
data/sources.jsonl CHANGED
@@ -1,3 +1,5 @@
 
 
1
  {"id":"wavelength-v0-2-1-release","title":"Wavelength v0.2.1","publisher":"Lightning Labs (GitHub)","authors":[],"date_published":"2026-10-31","url":"https://github.com/lightninglabs/wavelength/releases/tag/v0.2.1","type":"repo","category":"bitcoin-lightning","status":"spec_released","summary":"Release published 2026-10-31, not a prerelease. The notes say changes are since v0.2.0. Clients validate Ark transaction inputs before accepting out-of-round transfers. Linux builds disable MPTCP listeners by default, and the notes say this does not replace installing a patched kernel. Received VTXO expiry timing is derived from locally confirmed chain evidence. Pay swaps reject excessive refund timelocks before funding, refund intent survives interruptions, and payments that would leave unusably small change fail promptly. Exit recovery preserves the spending policy and funding proofs. Binaries are built with Go 1.27.3. The release body says maintainers must sign manifest-v0.2.1.txt before publishing. Full changelog: https://github.com/lightninglabs/wavelength/compare/v0.2.0...v0.2.1.","tags":["lightning","ark","wallet","release"],"verified_at":"2026-11-03","featured":true,"last_checked":"2026-11-03","http_status":200,"archive_url":null}
2
  {"id":"lnd-v0-21-6-beta","title":"lnd v0.21.6-beta and v0.20.7-beta","publisher":"Lightning Labs (GitHub)","authors":[],"date_published":"2026-10-30","url":"https://github.com/lightningnetwork/lnd/releases/tag/v0.21.6-beta","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"Security releases published 2026-10-30. v0.21.6-beta at 23:21 UTC is the newest non-prerelease on the 0.21 line. v0.20.7-beta at 22:37 UTC is the matching 0.20 tag. Both release bodies name CVE-2026-98432 and say there are no database migrations. The v0.21.6 notes say the demonstrated exploit needs an MPTCP listener, which Go 1.24+ enables by default, that Windows and macOS are not affected, and that lnd no longer opens MPTCP listeners. They tell Linux operators to upgrade, set net.mptcp.enabled=0, and install a patched kernel, and to start an unupgraded binary with GODEBUG=multipathtcp=0. The notes do not name kernel version numbers. This replaces the library row for v0.21.5-beta. Notes: https://github.com/lightningnetwork/lnd/blob/v0.21.6-beta/docs/release-notes/release-notes-0.21.6.md. The 0.20 tag: https://github.com/lightningnetwork/lnd/releases/tag/v0.20.7-beta.","tags":["lnd","lightning","release","security"],"verified_at":"2026-11-03","featured":true,"last_checked":"2026-11-03","http_status":200,"archive_url":null}
3
  {"id":"bitcoin-optech-newsletter-429","title":"Bitcoin Optech Newsletter #429","publisher":"Bitcoin Optech","authors":[],"date_published":"2026-10-30","url":"https://bitcoinops.org/en/newsletters/2026/10/30/","type":"report","category":"bitcoin-lightning","status":"news","summary":"Newsletter dated 2026-10-30. It discloses a denial-of-service in Core Lightning 25.02 through 26.04: a channel announcement that names the same node as both endpoints passed validation, was stored, and then crashed gossipd on a no-duplicates assertion. The stored message crashed the node again on every restart until the operator removed it by hand, which upgrading alone did not do. The fix is CLN 26.04.1, which rejects an announcement whose node_id_1 is not strictly less than node_id_2. BOLTs #1333 added the same receiver check to BOLT7, which had only required senders to order the IDs.","tags":["bitcoin","lightning","security","optech"],"verified_at":"2026-10-31","featured":true,"last_checked":"2026-10-31","http_status":200,"archive_url":null}
@@ -22,7 +24,6 @@
22
  {"id":"lightning-labs-l402-builders-guide","title":"L402: Lightning HTTP 402 Protocol","publisher":"Lightning Labs (Builder's Guide)","authors":[],"date_published":null,"url":"https://docs.lightning.engineering/the-lightning-network/l402","type":"docs","category":"bitcoin-lightning","status":"product_docs","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.","tags":["l402","lightning","m2m-payments","micropayments"],"verified_at":"2026-10-20","featured":true,"last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261009034701/https://docs.lightning.engineering/the-lightning-network/l402"}
23
  {"id":"lightning-labs-l402-protocol-specification","title":"L402 Protocol Specification","publisher":"Lightning Labs (Builder's Guide)","authors":[],"date_published":null,"url":"https://docs.lightning.engineering/the-lightning-network/l402/protocol-specification","type":"spec","category":"bitcoin-lightning","status":"spec_released","summary":"Specification of the abstract L402 HTTP and gRPC protocols. It defines the \"L402\" authentication scheme, which carries credentials as macaroon:preimage pairs.","tags":["l402","lightning","macaroons","identity"],"verified_at":"2026-10-20","featured":true,"last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20260702152123/https://docs.lightning.engineering/the-lightning-network/l402/protocol-specification"}
24
  {"id":"lightninglabs-l402-github","title":"lightninglabs/L402","publisher":"GitHub (Lightning Labs)","authors":[],"date_published":null,"url":"https://github.com/lightninglabs/L402","type":"repo","category":"bitcoin-lightning","status":"product_docs","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.","tags":["l402","lightning","macaroons","m2m-payments"],"verified_at":"2026-10-20","featured":true,"last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20260610015121/https://github.com/lightninglabs/L402"}
25
- {"id":"lightninglabs-aperture-github","title":"lightninglabs/aperture","publisher":"GitHub (Lightning Labs)","authors":[],"date_published":null,"url":"https://github.com/lightninglabs/aperture","type":"repo","category":"bitcoin-lightning","status":"product_docs","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.","tags":["l402","lightning","m2m-payments"],"verified_at":"2026-10-20","featured":true,"last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20250812194102/https://github.com/lightninglabs/aperture"}
26
  {"id":"lightninglabs-langchainbitcoin-github","title":"lightninglabs/LangChainBitcoin","publisher":"GitHub (Lightning Labs)","authors":[],"date_published":null,"url":"https://github.com/lightninglabs/LangChainBitcoin","type":"repo","category":"bitcoin-lightning","status":"product_docs","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.","tags":["lightning","l402","bitcoin","agent-wallets"],"verified_at":"2026-10-20","featured":true,"last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20250714041334/https://github.com/lightninglabs/LangChainBitcoin"}
27
  {"id":"lightning-bolts-github","title":"lightning/bolts: BOLT: Basis of Lightning Technology (Lightning Network Specifications)","publisher":"GitHub (lightning)","authors":[],"date_published":null,"url":"https://github.com/lightning/bolts","type":"spec","category":"bitcoin-lightning","status":"spec_released","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.","tags":["lightning","bitcoin","m2m-payments"],"verified_at":"2026-10-20","featured":true,"last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20260704121535/https://github.com/lightning/bolts"}
28
  {"id":"bolt-11-invoice-protocol","title":"BOLT #11: Invoice Protocol for Lightning Payments","publisher":"GitHub (lightning/bolts)","authors":[],"date_published":null,"url":"https://github.com/lightning/bolts/blob/master/11-payment-encoding.md","type":"spec","category":"bitcoin-lightning","status":"spec_released","summary":"Lightning specification for a simple, extendable, QR-code-ready protocol for requesting payments over Lightning (BOLT 11 invoices).","tags":["lightning","bitcoin","micropayments"],"verified_at":"2026-10-20","featured":true,"last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261016083441/https://github.com/lightning/bolts/blob/master/11-payment-encoding.md"}
@@ -156,6 +157,7 @@
156
  {"id":"webarena","title":"WebArena: A Realistic Web Environment for Building Autonomous Agents","publisher":"arXiv","authors":["Shuyan Zhou","Frank F. Xu","Hao Zhu","Xuhui Zhou","Robert Lo","Abishek Sridhar","Xianyi Cheng","Tianyue Ou","Yonatan Bisk","Daniel Fried","Uri Alon","Graham Neubig"],"date_published":"2023-07-25","url":"https://arxiv.org/abs/2307.13854","type":"research-paper","category":"datasets-benchmarks","status":"research","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.","tags":["benchmark","web-agents","research"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261002191854/https://arxiv.org/abs/2307.13854"}
157
  {"id":"swe-bench-leaderboards","title":"SWE-bench Leaderboards","publisher":"SWE-bench","authors":[],"date_published":null,"url":"https://www.swebench.com/","type":"docs","category":"datasets-benchmarks","status":"product_docs","summary":"Official SWE-bench site with leaderboards for SWE-bench, Verified, Multilingual, Multimodal and Lite variants, plus related tools.","tags":["benchmark","leaderboard"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261019081426/https://www.swebench.com/"}
158
  {"id":"open-x-embodiment","title":"Open X-Embodiment: Robotic Learning Datasets and RT-X Models","publisher":"Open X-Embodiment Collaboration","authors":[],"date_published":null,"url":"https://robotics-transformer-x.github.io/","type":"docs","category":"datasets-benchmarks","status":"product_docs","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.","tags":["dataset","robotics"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20260905225407/https://robotics-transformer-x.github.io/"}
 
159
  {"id":"arxiv-2610-35835-i-hitl","title":"I-HITL: Inalienable Human-in-the-Loop","publisher":"arXiv","authors":["Samuel Breckenridge","Dani Vilardell","Wenhao Wang","Fan Zhang","Ari Juels"],"date_published":"2026-10-26","url":"https://arxiv.org/abs/2610.35835","type":"research-paper","category":"safety-security","status":"research","summary":"arXiv 2610.35835, submitted 2026-10-26 and revised 2026-10-30 (v3). The abstract says an experiment on a popular agentic wallet platform required an emailed one-time passcode to raise a spending cap. With access to that email and a task blocked by the cap, ten frontier models often harvested the passcode and raised the cap. It says an I-HITL protocol requires a trusted computing device, and presents Countersign, a prototype that uses off-the-shelf consumer mobile devices. The abstract does not name the wallet vendor. GitHub repository https://github.com/I-HITL/countersign describes itself as a mobile phone-based implementation and is MIT licensed. The CoinDesk URL in the candidate file returned HTTP 429 on 2026-11-03 and was not read.","tags":["security","research","agent-wallets"],"verified_at":"2026-11-03","featured":false,"last_checked":"2026-11-03","http_status":200,"archive_url":null}
160
  {"id":"v12-x402-25-vulnerabilities","title":"25 Vulnerabilities in the x402 Protocol: Inside Three Critical Findings","publisher":"V12","authors":[],"date_published":"2026-10-22","url":"https://v12.sh/blog/x402","type":"report","category":"safety-security","status":"research","summary":"V12 reports 25 vulnerabilities in the x402 codebase and details three critical ones: a Solana token approval accepted as payment by the TypeScript facilitator, SIWx login messages signed for a different site, and a default client with no spending limit. All three were reported on 2026-08-12 and fixed by 2026-08-20. According to The Hacker News (2026-10-23), the fixes are in @x402/fetch, @x402/axios, @x402/extensions and @x402/svm 2.23.0 or later, patched clients cap each payment at $1 and accept only recognized stablecoins by default (spendControls: false disables this), and no formal security advisory was published. Related: https://thehackernews.com/2026/10/critical-x402-sdk-flaw-could-let.html.","tags":["x402","security","vulnerabilities","spend-controls","siwx","solana","sdk"],"verified_at":"2026-10-24","featured":false,"last_checked":"2026-10-24","http_status":200,"archive_url":null}
161
  {"id":"cloudflare-verified-bots-continuous-accountability","title":"Continuous accountability for Verified bots","publisher":"Cloudflare","authors":[],"date_published":"2026-10-16","url":"https://blog.cloudflare.com/verified-bots-accountability/","type":"announcement","category":"safety-security","status":"news","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.","tags":["identity","web-agents","security","http"],"verified_at":"2026-10-21","featured":false,"last_checked":"2026-10-21","http_status":200,"archive_url":null}
@@ -165,6 +167,7 @@
165
  {"id":"owasp-top-10-agentic-applications-2026","title":"OWASP Top 10 for Agentic Applications for 2026","publisher":"OWASP Gen AI Security Project","authors":[],"date_published":"2025-12-10","url":"https://genai.owasp.org/resource/owasp-top-10-for-agentic-applications-for-2026/","type":"report","category":"safety-security","status":"spec_released","summary":"Peer-reviewed framework, developed with more than 100 experts, identifying the most critical security risks facing autonomous and agentic AI systems.","tags":["owasp","security","agents"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261016132319/https://genai.owasp.org/resource/owasp-top-10-for-agentic-applications-for-2026/"}
166
  {"id":"nist-ai-rmf-1-0","title":"Artificial Intelligence Risk Management Framework (AI RMF 1.0)","publisher":"NIST","authors":["Elham Tabassi"],"date_published":"2023-01-26","url":"https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-ai-rmf-10","type":"spec","category":"safety-security","status":"spec_released","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.","tags":["ai-risk","standards","security"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261005065247/https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-ai-rmf-10"}
167
  {"id":"owasp-top-10-llm-2025","title":"OWASP Top 10 for LLM Applications (2025)","publisher":"OWASP Gen AI Security Project","authors":[],"date_published":null,"url":"https://genai.owasp.org/llm-top-10/","type":"report","category":"safety-security","status":"spec_released","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.","tags":["owasp","security","prompt-injection"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261016132319/https://genai.owasp.org/llm-top-10/"}
 
168
  {"id":"occ-bulletin-2026-50-genius-act","title":"GENIUS Act Regulations: Final Rule","publisher":"Office of the Comptroller of the Currency","authors":[],"date_published":"2026-10-21","url":"https://www.occ.gov/news-issuances/bulletins/2026/bulletin-2026-50.html","type":"regulatory","category":"regulation","status":"standard","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.","tags":["regulation","stablecoins"],"verified_at":"2026-10-23","featured":false,"last_checked":"2026-10-23","http_status":200,"archive_url":null}
169
  {"id":"fsb-sound-practices-responsible-ai-adoption-final","title":"Sound Practices for Responsible Adoption of Artificial Intelligence (AI): Final report","publisher":"Financial Stability Board","authors":[],"date_published":"2026-10-15","url":"https://www.fsb.org/2026/10/sound-practices-for-responsible-adoption-of-artificial-intelligence-ai-final-report/","type":"report","category":"regulation","status":"research","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.","tags":["regulation","ai-risk","agents"],"verified_at":"2026-10-21","featured":false,"last_checked":"2026-10-21","http_status":200,"archive_url":null}
170
  {"id":"eu-ai-act-commission-page","title":"AI Act","publisher":"European Commission (Shaping Europe's digital future)","authors":[],"date_published":null,"url":"https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai","type":"regulatory","category":"regulation","status":"standard","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.","tags":["eu-ai-act","regulation"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261016150532/https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai"}
 
1
+ {"id":"aperture-v0-6-0-release","title":"Aperture v0.6.0","publisher":"Lightning Labs","authors":[],"date_published":"2026-11-05","url":"https://github.com/lightninglabs/aperture/releases/tag/v0.6.0","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"Release published 2026-11-05, not a prerelease. Metered pricing is opt-in per service (metered: true). A price server is called at GetPrice, ChallengeMinted, AuthorizeRequest, and ReportUsage. The release includes meterd, a reference price server, and the pricesrpc interface. docs/metering.md at tag v0.6.0 names the same four calls. The release says invoices can be minted from a Wavelength wallet instead of lnd, so a seller needs no node of their own. docs/wavelength.md at that tag describes invoices from a Wavelength wallet and also says the Wavelength backend is not in an Aperture release yet. A service with auth: l402+mpp answers an unpaid request with one 402 that carries both an L402 and a Payment challenge. Hardening includes a Payment-Receipt only for a credential that authenticated the request, TLS 1.2 or newer, and path canonicalization before authorization. The Upgrading section lists changes that can break an existing deployment. enablempp is refused at startup with the etcd backend; sqlite or postgres is required. A static price of 0 means the default price of 1 sat, not free. This replaces the lightninglabs-aperture-github row. Metering: https://github.com/lightninglabs/aperture/blob/v0.6.0/docs/metering.md. Wavelength: https://github.com/lightninglabs/aperture/blob/v0.6.0/docs/wavelength.md.","tags":["l402","lightning","m2m-payments","release"],"verified_at":"2026-11-05","featured":true,"last_checked":"2026-11-05","http_status":200,"archive_url":null}
2
+ {"id":"core-lightning-v26-06-10","title":"Core Lightning v26.06.10","publisher":"Elements Project","authors":[],"date_published":"2026-11-04","url":"https://github.com/ElementsProject/lightning/releases/tag/v26.06.10","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"Security point release published 2026-11-04T13:34:33Z, not a prerelease. The notes say it includes fixes for vulnerabilities and that the maintainers strongly recommend upgrading. The highlighted security fixes cover dual funding and splicing, including signature checks on the peer's tx_signatures, onchaind HTLC resolution, gossip resource limits, connectd, runes and commando, plugin hooks and hsmd. A peer dust_limit_satoshis above 5000 sat is refused. The notes recommend binding commando runes to a node id with an id restriction, and rotating unaccounted runes by blacklisting them and issuing new ones. The notes name no CVE. The changelog heading linked from the release is dated 2026-11-05. The release notes do not name Blockstream.","tags":["lightning","release","security"],"verified_at":"2026-11-05","featured":true,"last_checked":"2026-11-05","http_status":200,"archive_url":null}
3
  {"id":"wavelength-v0-2-1-release","title":"Wavelength v0.2.1","publisher":"Lightning Labs (GitHub)","authors":[],"date_published":"2026-10-31","url":"https://github.com/lightninglabs/wavelength/releases/tag/v0.2.1","type":"repo","category":"bitcoin-lightning","status":"spec_released","summary":"Release published 2026-10-31, not a prerelease. The notes say changes are since v0.2.0. Clients validate Ark transaction inputs before accepting out-of-round transfers. Linux builds disable MPTCP listeners by default, and the notes say this does not replace installing a patched kernel. Received VTXO expiry timing is derived from locally confirmed chain evidence. Pay swaps reject excessive refund timelocks before funding, refund intent survives interruptions, and payments that would leave unusably small change fail promptly. Exit recovery preserves the spending policy and funding proofs. Binaries are built with Go 1.27.3. The release body says maintainers must sign manifest-v0.2.1.txt before publishing. Full changelog: https://github.com/lightninglabs/wavelength/compare/v0.2.0...v0.2.1.","tags":["lightning","ark","wallet","release"],"verified_at":"2026-11-03","featured":true,"last_checked":"2026-11-03","http_status":200,"archive_url":null}
4
  {"id":"lnd-v0-21-6-beta","title":"lnd v0.21.6-beta and v0.20.7-beta","publisher":"Lightning Labs (GitHub)","authors":[],"date_published":"2026-10-30","url":"https://github.com/lightningnetwork/lnd/releases/tag/v0.21.6-beta","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"Security releases published 2026-10-30. v0.21.6-beta at 23:21 UTC is the newest non-prerelease on the 0.21 line. v0.20.7-beta at 22:37 UTC is the matching 0.20 tag. Both release bodies name CVE-2026-98432 and say there are no database migrations. The v0.21.6 notes say the demonstrated exploit needs an MPTCP listener, which Go 1.24+ enables by default, that Windows and macOS are not affected, and that lnd no longer opens MPTCP listeners. They tell Linux operators to upgrade, set net.mptcp.enabled=0, and install a patched kernel, and to start an unupgraded binary with GODEBUG=multipathtcp=0. The notes do not name kernel version numbers. This replaces the library row for v0.21.5-beta. Notes: https://github.com/lightningnetwork/lnd/blob/v0.21.6-beta/docs/release-notes/release-notes-0.21.6.md. The 0.20 tag: https://github.com/lightningnetwork/lnd/releases/tag/v0.20.7-beta.","tags":["lnd","lightning","release","security"],"verified_at":"2026-11-03","featured":true,"last_checked":"2026-11-03","http_status":200,"archive_url":null}
5
  {"id":"bitcoin-optech-newsletter-429","title":"Bitcoin Optech Newsletter #429","publisher":"Bitcoin Optech","authors":[],"date_published":"2026-10-30","url":"https://bitcoinops.org/en/newsletters/2026/10/30/","type":"report","category":"bitcoin-lightning","status":"news","summary":"Newsletter dated 2026-10-30. It discloses a denial-of-service in Core Lightning 25.02 through 26.04: a channel announcement that names the same node as both endpoints passed validation, was stored, and then crashed gossipd on a no-duplicates assertion. The stored message crashed the node again on every restart until the operator removed it by hand, which upgrading alone did not do. The fix is CLN 26.04.1, which rejects an announcement whose node_id_1 is not strictly less than node_id_2. BOLTs #1333 added the same receiver check to BOLT7, which had only required senders to order the IDs.","tags":["bitcoin","lightning","security","optech"],"verified_at":"2026-10-31","featured":true,"last_checked":"2026-10-31","http_status":200,"archive_url":null}
 
24
  {"id":"lightning-labs-l402-builders-guide","title":"L402: Lightning HTTP 402 Protocol","publisher":"Lightning Labs (Builder's Guide)","authors":[],"date_published":null,"url":"https://docs.lightning.engineering/the-lightning-network/l402","type":"docs","category":"bitcoin-lightning","status":"product_docs","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.","tags":["l402","lightning","m2m-payments","micropayments"],"verified_at":"2026-10-20","featured":true,"last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261009034701/https://docs.lightning.engineering/the-lightning-network/l402"}
25
  {"id":"lightning-labs-l402-protocol-specification","title":"L402 Protocol Specification","publisher":"Lightning Labs (Builder's Guide)","authors":[],"date_published":null,"url":"https://docs.lightning.engineering/the-lightning-network/l402/protocol-specification","type":"spec","category":"bitcoin-lightning","status":"spec_released","summary":"Specification of the abstract L402 HTTP and gRPC protocols. It defines the \"L402\" authentication scheme, which carries credentials as macaroon:preimage pairs.","tags":["l402","lightning","macaroons","identity"],"verified_at":"2026-10-20","featured":true,"last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20260702152123/https://docs.lightning.engineering/the-lightning-network/l402/protocol-specification"}
26
  {"id":"lightninglabs-l402-github","title":"lightninglabs/L402","publisher":"GitHub (Lightning Labs)","authors":[],"date_published":null,"url":"https://github.com/lightninglabs/L402","type":"repo","category":"bitcoin-lightning","status":"product_docs","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.","tags":["l402","lightning","macaroons","m2m-payments"],"verified_at":"2026-10-20","featured":true,"last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20260610015121/https://github.com/lightninglabs/L402"}
 
27
  {"id":"lightninglabs-langchainbitcoin-github","title":"lightninglabs/LangChainBitcoin","publisher":"GitHub (Lightning Labs)","authors":[],"date_published":null,"url":"https://github.com/lightninglabs/LangChainBitcoin","type":"repo","category":"bitcoin-lightning","status":"product_docs","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.","tags":["lightning","l402","bitcoin","agent-wallets"],"verified_at":"2026-10-20","featured":true,"last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20250714041334/https://github.com/lightninglabs/LangChainBitcoin"}
28
  {"id":"lightning-bolts-github","title":"lightning/bolts: BOLT: Basis of Lightning Technology (Lightning Network Specifications)","publisher":"GitHub (lightning)","authors":[],"date_published":null,"url":"https://github.com/lightning/bolts","type":"spec","category":"bitcoin-lightning","status":"spec_released","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.","tags":["lightning","bitcoin","m2m-payments"],"verified_at":"2026-10-20","featured":true,"last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20260704121535/https://github.com/lightning/bolts"}
29
  {"id":"bolt-11-invoice-protocol","title":"BOLT #11: Invoice Protocol for Lightning Payments","publisher":"GitHub (lightning/bolts)","authors":[],"date_published":null,"url":"https://github.com/lightning/bolts/blob/master/11-payment-encoding.md","type":"spec","category":"bitcoin-lightning","status":"spec_released","summary":"Lightning specification for a simple, extendable, QR-code-ready protocol for requesting payments over Lightning (BOLT 11 invoices).","tags":["lightning","bitcoin","micropayments"],"verified_at":"2026-10-20","featured":true,"last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261016083441/https://github.com/lightning/bolts/blob/master/11-payment-encoding.md"}
 
157
  {"id":"webarena","title":"WebArena: A Realistic Web Environment for Building Autonomous Agents","publisher":"arXiv","authors":["Shuyan Zhou","Frank F. Xu","Hao Zhu","Xuhui Zhou","Robert Lo","Abishek Sridhar","Xianyi Cheng","Tianyue Ou","Yonatan Bisk","Daniel Fried","Uri Alon","Graham Neubig"],"date_published":"2023-07-25","url":"https://arxiv.org/abs/2307.13854","type":"research-paper","category":"datasets-benchmarks","status":"research","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.","tags":["benchmark","web-agents","research"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261002191854/https://arxiv.org/abs/2307.13854"}
158
  {"id":"swe-bench-leaderboards","title":"SWE-bench Leaderboards","publisher":"SWE-bench","authors":[],"date_published":null,"url":"https://www.swebench.com/","type":"docs","category":"datasets-benchmarks","status":"product_docs","summary":"Official SWE-bench site with leaderboards for SWE-bench, Verified, Multilingual, Multimodal and Lite variants, plus related tools.","tags":["benchmark","leaderboard"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261019081426/https://www.swebench.com/"}
159
  {"id":"open-x-embodiment","title":"Open X-Embodiment: Robotic Learning Datasets and RT-X Models","publisher":"Open X-Embodiment Collaboration","authors":[],"date_published":null,"url":"https://robotics-transformer-x.github.io/","type":"docs","category":"datasets-benchmarks","status":"product_docs","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.","tags":["dataset","robotics"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20260905225407/https://robotics-transformer-x.github.io/"}
160
+ {"id":"agent-money-benchmark-v1","title":"Agent Money Benchmark v1","publisher":"BlockRun","authors":[],"date_published":null,"url":"https://agentmoneybench.com/","type":"docs","category":"datasets-benchmarks","status":"product_docs","summary":"Version 1 vendor benchmark from BlockRun. The site says 10 frontier models were given wallets, settlement is Solana mainnet, and purchases are real USDC on-chain. Tracks are Financial Research and Adversarial Marketplace. It says 7 of 10 models paid a cheating seller at least once. Trap columns are Charged again after payment, Price above listed, Expired quote, Wrong data delivered, Paid, not delivered, Lookalike payee, Receipt mismatch, and Hidden instructions. The site says the gateway is BlockRun's and does not name x402. It says the full task set, rubrics, and run records are private. BlockRun-authored materials are CC BY-NC 4.0 for noncommercial use with attribution, and commercial use needs written permission. The site dates the run 27-29 Oct 2026 and does not state a publication date. Repository: https://github.com/BlockRunAI/agent-money-bench. Dataset: https://huggingface.co/datasets/BlockRunAI/agent-money-bench, whose card license is cc-by-nc-4.0.","tags":["benchmark","dataset","stablecoins"],"verified_at":"2026-11-05","featured":false,"last_checked":"2026-11-05","http_status":200,"archive_url":null}
161
  {"id":"arxiv-2610-35835-i-hitl","title":"I-HITL: Inalienable Human-in-the-Loop","publisher":"arXiv","authors":["Samuel Breckenridge","Dani Vilardell","Wenhao Wang","Fan Zhang","Ari Juels"],"date_published":"2026-10-26","url":"https://arxiv.org/abs/2610.35835","type":"research-paper","category":"safety-security","status":"research","summary":"arXiv 2610.35835, submitted 2026-10-26 and revised 2026-10-30 (v3). The abstract says an experiment on a popular agentic wallet platform required an emailed one-time passcode to raise a spending cap. With access to that email and a task blocked by the cap, ten frontier models often harvested the passcode and raised the cap. It says an I-HITL protocol requires a trusted computing device, and presents Countersign, a prototype that uses off-the-shelf consumer mobile devices. The abstract does not name the wallet vendor. GitHub repository https://github.com/I-HITL/countersign describes itself as a mobile phone-based implementation and is MIT licensed. The CoinDesk URL in the candidate file returned HTTP 429 on 2026-11-03 and was not read.","tags":["security","research","agent-wallets"],"verified_at":"2026-11-03","featured":false,"last_checked":"2026-11-03","http_status":200,"archive_url":null}
162
  {"id":"v12-x402-25-vulnerabilities","title":"25 Vulnerabilities in the x402 Protocol: Inside Three Critical Findings","publisher":"V12","authors":[],"date_published":"2026-10-22","url":"https://v12.sh/blog/x402","type":"report","category":"safety-security","status":"research","summary":"V12 reports 25 vulnerabilities in the x402 codebase and details three critical ones: a Solana token approval accepted as payment by the TypeScript facilitator, SIWx login messages signed for a different site, and a default client with no spending limit. All three were reported on 2026-08-12 and fixed by 2026-08-20. According to The Hacker News (2026-10-23), the fixes are in @x402/fetch, @x402/axios, @x402/extensions and @x402/svm 2.23.0 or later, patched clients cap each payment at $1 and accept only recognized stablecoins by default (spendControls: false disables this), and no formal security advisory was published. Related: https://thehackernews.com/2026/10/critical-x402-sdk-flaw-could-let.html.","tags":["x402","security","vulnerabilities","spend-controls","siwx","solana","sdk"],"verified_at":"2026-10-24","featured":false,"last_checked":"2026-10-24","http_status":200,"archive_url":null}
163
  {"id":"cloudflare-verified-bots-continuous-accountability","title":"Continuous accountability for Verified bots","publisher":"Cloudflare","authors":[],"date_published":"2026-10-16","url":"https://blog.cloudflare.com/verified-bots-accountability/","type":"announcement","category":"safety-security","status":"news","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.","tags":["identity","web-agents","security","http"],"verified_at":"2026-10-21","featured":false,"last_checked":"2026-10-21","http_status":200,"archive_url":null}
 
167
  {"id":"owasp-top-10-agentic-applications-2026","title":"OWASP Top 10 for Agentic Applications for 2026","publisher":"OWASP Gen AI Security Project","authors":[],"date_published":"2025-12-10","url":"https://genai.owasp.org/resource/owasp-top-10-for-agentic-applications-for-2026/","type":"report","category":"safety-security","status":"spec_released","summary":"Peer-reviewed framework, developed with more than 100 experts, identifying the most critical security risks facing autonomous and agentic AI systems.","tags":["owasp","security","agents"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261016132319/https://genai.owasp.org/resource/owasp-top-10-for-agentic-applications-for-2026/"}
168
  {"id":"nist-ai-rmf-1-0","title":"Artificial Intelligence Risk Management Framework (AI RMF 1.0)","publisher":"NIST","authors":["Elham Tabassi"],"date_published":"2023-01-26","url":"https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-ai-rmf-10","type":"spec","category":"safety-security","status":"spec_released","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.","tags":["ai-risk","standards","security"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261005065247/https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-ai-rmf-10"}
169
  {"id":"owasp-top-10-llm-2025","title":"OWASP Top 10 for LLM Applications (2025)","publisher":"OWASP Gen AI Security Project","authors":[],"date_published":null,"url":"https://genai.owasp.org/llm-top-10/","type":"report","category":"safety-security","status":"spec_released","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.","tags":["owasp","security","prompt-injection"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261016132319/https://genai.owasp.org/llm-top-10/"}
170
+ {"id":"occ-bulletin-2026-54","title":"OCC Bulletin 2026-54: Super Intelligence: Supervisory Framework","publisher":"Office of the Comptroller of the Currency","authors":["James M. Gallagher"],"date_published":"2026-11-04","url":"https://www.occ.gov/news-issuances/bulletins/2026/bulletin-2026-54.html","type":"regulatory","category":"regulation","status":"product_docs","summary":"OCC Bulletin 2026-54, dated November 4, 2026, signed by James M. Gallagher, Senior Deputy Comptroller and Chief National Bank Examiner. It issues a supervisory framework for OCC examiners evaluating national banks' use of super intelligence in normal-course business activities. The bulletin says it does not establish supervisory expectations for banks and is not intended to establish new regulatory expectations or prescriptive requirements. It says examiners should not treat super intelligence as a separate and distinct risk category, and banks are not required to define a separate SI risk appetite. It says a bank's risk classification of SI use cases may be based on potential consequences, transfer of agency, and the degree of human oversight rather than the technical sophistication of the SI used. The bulletin links a PDF that was not read.","tags":["regulation"],"verified_at":"2026-11-05","featured":false,"last_checked":"2026-11-05","http_status":200,"archive_url":null}
171
  {"id":"occ-bulletin-2026-50-genius-act","title":"GENIUS Act Regulations: Final Rule","publisher":"Office of the Comptroller of the Currency","authors":[],"date_published":"2026-10-21","url":"https://www.occ.gov/news-issuances/bulletins/2026/bulletin-2026-50.html","type":"regulatory","category":"regulation","status":"standard","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.","tags":["regulation","stablecoins"],"verified_at":"2026-10-23","featured":false,"last_checked":"2026-10-23","http_status":200,"archive_url":null}
172
  {"id":"fsb-sound-practices-responsible-ai-adoption-final","title":"Sound Practices for Responsible Adoption of Artificial Intelligence (AI): Final report","publisher":"Financial Stability Board","authors":[],"date_published":"2026-10-15","url":"https://www.fsb.org/2026/10/sound-practices-for-responsible-adoption-of-artificial-intelligence-ai-final-report/","type":"report","category":"regulation","status":"research","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.","tags":["regulation","ai-risk","agents"],"verified_at":"2026-10-21","featured":false,"last_checked":"2026-10-21","http_status":200,"archive_url":null}
173
  {"id":"eu-ai-act-commission-page","title":"AI Act","publisher":"European Commission (Shaping Europe's digital future)","authors":[],"date_published":null,"url":"https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai","type":"regulatory","category":"regulation","status":"standard","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.","tags":["eu-ai-act","regulation"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261016150532/https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai"}
data/tags.json CHANGED
@@ -1,6 +1,6 @@
1
  {
2
  "schema_version": "1",
3
- "generated_at": "2026-11-04T00:00:00Z",
4
  "count": 70,
5
  "tags": [
6
  {
@@ -60,7 +60,7 @@
60
  },
61
  {
62
  "tag": "benchmark",
63
- "count": 7,
64
  "json_url": "https://agentpaywire.com/api/library/tag/benchmark.json"
65
  },
66
  {
@@ -90,7 +90,7 @@
90
  },
91
  {
92
  "tag": "dataset",
93
- "count": 1,
94
  "json_url": "https://agentpaywire.com/api/library/tag/dataset.json"
95
  },
96
  {
@@ -150,7 +150,7 @@
150
  },
151
  {
152
  "tag": "lightning",
153
- "count": 43,
154
  "json_url": "https://agentpaywire.com/api/library/tag/lightning.json"
155
  },
156
  {
@@ -245,12 +245,12 @@
245
  },
246
  {
247
  "tag": "regulation",
248
- "count": 10,
249
  "json_url": "https://agentpaywire.com/api/library/tag/regulation.json"
250
  },
251
  {
252
  "tag": "release",
253
- "count": 4,
254
  "json_url": "https://agentpaywire.com/api/library/tag/release.json"
255
  },
256
  {
@@ -275,7 +275,7 @@
275
  },
276
  {
277
  "tag": "security",
278
- "count": 32,
279
  "json_url": "https://agentpaywire.com/api/library/tag/security.json"
280
  },
281
  {
@@ -300,7 +300,7 @@
300
  },
301
  {
302
  "tag": "stablecoins",
303
- "count": 28,
304
  "json_url": "https://agentpaywire.com/api/library/tag/stablecoins.json"
305
  },
306
  {
 
1
  {
2
  "schema_version": "1",
3
+ "generated_at": "2026-11-05T00:00:00Z",
4
  "count": 70,
5
  "tags": [
6
  {
 
60
  },
61
  {
62
  "tag": "benchmark",
63
+ "count": 8,
64
  "json_url": "https://agentpaywire.com/api/library/tag/benchmark.json"
65
  },
66
  {
 
90
  },
91
  {
92
  "tag": "dataset",
93
+ "count": 2,
94
  "json_url": "https://agentpaywire.com/api/library/tag/dataset.json"
95
  },
96
  {
 
150
  },
151
  {
152
  "tag": "lightning",
153
+ "count": 44,
154
  "json_url": "https://agentpaywire.com/api/library/tag/lightning.json"
155
  },
156
  {
 
245
  },
246
  {
247
  "tag": "regulation",
248
+ "count": 11,
249
  "json_url": "https://agentpaywire.com/api/library/tag/regulation.json"
250
  },
251
  {
252
  "tag": "release",
253
+ "count": 6,
254
  "json_url": "https://agentpaywire.com/api/library/tag/release.json"
255
  },
256
  {
 
275
  },
276
  {
277
  "tag": "security",
278
+ "count": 33,
279
  "json_url": "https://agentpaywire.com/api/library/tag/security.json"
280
  },
281
  {
 
300
  },
301
  {
302
  "tag": "stablecoins",
303
+ "count": 29,
304
  "json_url": "https://agentpaywire.com/api/library/tag/stablecoins.json"
305
  },
306
  {