{ "schema_version": "1", "generated_at": "2026-11-16T00:00:00Z", "disclaimer": { "text": "Not investment advice.", "url": "https://agentpaywire.com/disclaimer.json" }, "$schema": "https://agentpaywire.com/schemas/library.schema.json", "license": "links + original short summaries; content belongs to publishers", "count": 181, "categories": [ { "id": "bitcoin-lightning", "label": "Bitcoin and Lightning", "featured": true, "count": 43, "json_url": "https://agentpaywire.com/api/library/bitcoin-lightning.json", "markdown_url": "https://agentpaywire.com/library/bitcoin-lightning.md", "html_url": "https://agentpaywire.com/library/bitcoin-lightning/" }, { "id": "payments", "label": "Payments", "featured": false, "count": 74, "json_url": "https://agentpaywire.com/api/library/payments.json", "markdown_url": "https://agentpaywire.com/library/payments.md", "html_url": "https://agentpaywire.com/library/payments/" }, { "id": "agent-protocols", "label": "Agent protocols", "featured": false, "count": 34, "json_url": "https://agentpaywire.com/api/library/agent-protocols.json", "markdown_url": "https://agentpaywire.com/library/agent-protocols.md", "html_url": "https://agentpaywire.com/library/agent-protocols/" }, { "id": "robotics-autonomy", "label": "Robotics and autonomy", "featured": false, "count": 4, "json_url": "https://agentpaywire.com/api/library/robotics-autonomy.json", "markdown_url": "https://agentpaywire.com/library/robotics-autonomy.md", "html_url": "https://agentpaywire.com/library/robotics-autonomy/" }, { "id": "iot", "label": "IoT", "featured": false, "count": 4, "json_url": "https://agentpaywire.com/api/library/iot.json", "markdown_url": "https://agentpaywire.com/library/iot.md", "html_url": "https://agentpaywire.com/library/iot/" }, { "id": "datasets-benchmarks", "label": "Datasets and benchmarks", "featured": false, "count": 9, "json_url": "https://agentpaywire.com/api/library/datasets-benchmarks.json", "markdown_url": "https://agentpaywire.com/library/datasets-benchmarks.md", "html_url": "https://agentpaywire.com/library/datasets-benchmarks/" }, { "id": "safety-security", "label": "Safety and security", "featured": false, "count": 9, "json_url": "https://agentpaywire.com/api/library/safety-security.json", "markdown_url": "https://agentpaywire.com/library/safety-security.md", "html_url": "https://agentpaywire.com/library/safety-security/" }, { "id": "regulation", "label": "Regulation", "featured": false, "count": 4, "json_url": "https://agentpaywire.com/api/library/regulation.json", "markdown_url": "https://agentpaywire.com/library/regulation.md", "html_url": "https://agentpaywire.com/library/regulation/" } ], "entries": [ { "id": "bitcoin-optech-newsletter-430", "title": "Bitcoin Optech Newsletter #430", "publisher": "Bitcoin Optech", "authors": [], "date_published": "2026-11-06", "url": "https://bitcoinops.org/en/newsletters/2026/11/06/", "type": "report", "category": "bitcoin-lightning", "status": "news", "summary": "Newsletter dated 2026-11-06. The releases section calls LND v0.21.6-beta and v0.20.7-beta security releases that include the Linux CVE-2026-98432 mitigation described under LND #11456, and says that mitigation does not fix the kernel. It calls Core Lightning 26.06.10 a security release for dual funding, splicing, onchain HTLC resolution, access controls, and other components, with tests temporarily withheld. It calls BTCPay Server 2.4.7 a security release for 85 findings from Anthropic's OSS Scanner, including payout limits, other stores' data, authentication, and resource exhaustion. Separate from those release announcements, the notable-changes section describes LND #11357 as rejecting duplicate BOLT11 payment secrets and incorrect lengths for the payment hash, description hash, payment secret, and receiver public key, instead of ignoring extras or treating a bad length as absent. It describes Core Lightning #9419 as adding an optional failure_reason on listforwards and forward_event for local forwarding failures, and #9592 as making xpay exclude a forwarding node for the rest of a payment after unknown_next_peer twice. The newsletter also covers an ongoing TCP hole-punching discussion and a draft co-signer spending policy that is not assigned a BIP number.", "tags": [ "bitcoin", "lightning", "bolt11", "lnd", "core-lightning", "ldk", "btcpay", "optech" ], "verified_at": "2026-11-07", "featured": true, "last_checked": "2026-11-07", "http_status": 200, "archive_url": null }, { "id": "breez-sdk-spark-0-28-0", "title": "Breez SDK 0.28 (Spark)", "publisher": "Breez (GitHub)", "authors": [], "date_published": "2026-11-05", "url": "https://github.com/breez/spark-sdk/releases/tag/0.28.0", "type": "repo", "category": "bitcoin-lightning", "status": "spec_released", "summary": "Release 0.28.0 published 2026-11-05, not a prerelease. The notes add a bridging client to pay a Spark, Lightning, or USDC/USDT address from another chain or over Lightning. USDC and USDT in that sentence are addresses on another chain, not a claim that the SDK treats them as native Lightning assets. The notes add sending to BIP-352 silent payment addresses and a change that rejects expired Lightning invoices. They also say the parser follows BIP-321 and restricts BIP-353 lookups. Compare: https://github.com/breez/spark-sdk/compare/0.27.0...0.28.0.", "tags": [ "lightning", "spark", "breez", "sdk", "bip352", "release" ], "verified_at": "2026-11-07", "featured": true, "last_checked": "2026-11-07", "http_status": 200, "archive_url": null }, { "id": "getalby-hub-v1-24-6-release", "title": "Release v1.24.6 Julian Assange · getAlby/hub", "publisher": "GitHub (Alby)", "authors": [], "date_published": "2026-11-05", "url": "https://github.com/getAlby/hub/releases/tag/v1.24.6", "type": "repo", "category": "bitcoin-lightning", "status": "product_docs", "summary": "Patch release published 2026-11-05T09:45:44Z, not a prerelease. The notes say it includes bug fixes and security updates, thank Project Loupe, the Bitcoin Red Team, and individual contributors for AI scans, and name no CVE. NWC create_connection errors include unsupported method names. Hub binaries disable MPTCP by default. App pubkeys that are not valid curve keys are rejected. Bundled lnd is v0.21.6-beta. This replaces the v1.24.3 row. Full changelog: https://github.com/getAlby/hub/compare/v1.24.4...v1.24.6.", "tags": [ "lightning", "nwc", "agent-wallets", "security", "tools" ], "verified_at": "2026-11-06", "featured": true, "last_checked": "2026-11-06", "http_status": 200, "archive_url": null }, { "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 }, { "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 }, { "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 }, { "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 }, { "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 }, { "id": "btcpay-server-v2-4-7", "title": "BTCPay Server v2.4.7", "publisher": "BTCPay Server (GitHub)", "authors": [], "date_published": "2026-10-29", "url": "https://github.com/btcpayserver/btcpayserver/releases/tag/v2.4.7", "type": "repo", "category": "bitcoin-lightning", "status": "spec_released", "summary": "Release v2.4.7 published 2026-10-29, not a prerelease. The notes call it a bug-fix release for security, reliability, and payment accounting, and recommend updating, especially for servers shared by multiple merchants. The release says it fixes 85 security findings from Anthropic's OSS Scanner, using that report's severity ratings: 1 critical, 13 high, 52 medium, and 19 low. Those figures are the release's own table, not a CVE list. Named fixes include payout state changes that bypassed pull-payment limits, checkout forms restricted to the owning store, and BitPay API changes that apply the store's confirmation and expiry limits to anonymously created invoices and limit posData to 64 KiB before parsing. The release does not say every vulnerability in BTCPay is fixed.", "tags": [ "bitcoin", "lightning", "btcpay", "merchant", "security" ], "verified_at": "2026-11-07", "featured": true, "last_checked": "2026-11-07", "http_status": 200, "archive_url": null }, { "id": "l402sdk-v0-2-0-release", "title": "L402sdk 0.2.0", "publisher": "Lightning Labs", "authors": [], "date_published": "2026-10-29", "url": "https://github.com/lightninglabs/L402sdk/blob/main/CHANGELOG.md", "type": "repo", "category": "bitcoin-lightning", "status": "product_docs", "summary": "L402sdk 0.2.0 is dated 2026-10-29 in CHANGELOG.md. Budgets include routing fees and concurrent payment reservations. Automatic payments require a backend that enforces fee limits before submission. A zero fee limit allows only zero-fee routes. Invalid or amountless invoices are rejected before the wallet is called. npm @lightninglabs/l402 0.2.0 was published 2026-10-29T13:46:37.700Z and its repository is this project. The GitHub releases API returned 404 for tag v0.2.0 on 2026-11-04. This replaces the lightninglabs-l402sdk row. Related library entry: lightninglabs-l402-github (https://github.com/lightninglabs/L402).", "tags": [ "l402", "lightning", "sdk", "release" ], "verified_at": "2026-11-04", "featured": true, "last_checked": "2026-11-04", "http_status": 200, "archive_url": null }, { "id": "eclair-v0-14-6-release", "title": "Eclair v0.14.6", "publisher": "ACINQ (GitHub)", "authors": [], "date_published": "2026-10-27", "url": "https://github.com/ACINQ/eclair/releases/tag/v0.14.6", "type": "repo", "category": "bitcoin-lightning", "status": "product_docs", "summary": "Patch release published 2026-10-27. GitHub marks it not a prerelease. The release says it contains security hardening fixes that malicious nodes could exploit, and thanks @erickcestari for responsible disclosures. The release notes add require-confirmed-inputs-for-splicing, enabled by default, so splices spend only confirmed inputs. They say setting it to false is unsafe because a peer may double-spend an unconfirmed parent after signing. The release says it is fully compatible with previous versions and that channels do not need to be closed. Notes: https://github.com/ACINQ/eclair/blob/master/docs/release-notes/eclair-v0.14.6.md.", "tags": [ "eclair", "lightning", "release", "security", "trampoline", "splicing" ], "verified_at": "2026-10-31", "featured": true, "last_checked": "2026-10-31", "http_status": 200, "archive_url": null }, { "id": "getalby-js-sdk-v9-0-0-release", "title": "Release v9.0.0 · getAlby/js-sdk", "publisher": "GitHub (Alby)", "authors": [], "date_published": "2026-10-27", "url": "https://github.com/getAlby/js-sdk/releases/tag/v9.0.0", "type": "repo", "category": "bitcoin-lightning", "status": "product_docs", "summary": "Breaking release published 2026-10-27. The notes say Nip47TimeoutValues.publishTimeout is removed and the publish timeout is fixed per client, while replyTimeout stays per method. A relay that does not reply OK within 5 seconds now rejects with Nip47PublishTimeoutError. Deprecated nwc multi_* methods are removed, matching their removal from NIP-47, and Nip47Method replaces Nip47SingleMethod. An NWC reply that fails to decrypt is rejected. The full changelog link is v8.1.1...v9.0.0. This replaces the library row for v8.1.0.", "tags": [ "nwc", "nostr", "lightning", "agent-wallets", "tools" ], "verified_at": "2026-11-03", "featured": true, "last_checked": "2026-11-03", "http_status": 200, "archive_url": null }, { "id": "lightning-labs-wavelength-docs", "title": "Wavelength docs: llms.txt and Build with agents", "publisher": "Lightning Labs", "authors": [], "date_published": "2026-10-23", "url": "https://wavelength.lightning.engineering/llms.txt", "type": "docs", "category": "bitcoin-lightning", "status": "product_docs", "summary": "Machine-readable docs index for the Wavelength SDK, a self-custodial Bitcoin, Lightning, and Ark wallet. Every docs page has a markdown twin at the same URL with .md appended, and https://wavelength.lightning.engineering/llms-full.txt holds the whole corpus. The Build with agents page is https://wavelength.lightning.engineering/agents.md. `wavecli mcp serve` runs a stdio MCP server that exposes each daemon RPC as a typed tool; create and unlock are omitted. `wavecli schema` dumps method schemas as JSON. Related: https://wavelength.lightning.engineering/cli/mcp.md, https://wavelength.lightning.engineering/cli/schema.md.", "tags": [ "lightning", "ark", "wallet", "mcp", "llms-txt", "agent-tooling" ], "verified_at": "2026-10-25", "featured": true, "last_checked": "2026-10-25", "http_status": 200, "archive_url": null }, { "id": "lightning-labs-wavelength-mainnet", "title": "Ride the Wave: Integrate Bitcoin Payments with Wavelength on Mainnet", "publisher": "Lightning Labs", "authors": [], "date_published": "2026-10-23", "url": "https://lightning.engineering/posts/2026-10-23-wavelength-mainnet-launch/", "type": "announcement", "category": "bitcoin-lightning", "status": "product_docs", "summary": "Wavelength, Lightning Labs' self-custodial wallet toolkit on an Ark-like settlement layer, is live on mainnet (alpha; repo release v0.2.0 on 2026-10-23). Agents can drive the wallet over MCP via `wavecli mcp serve`, pay L402 APIs, and get receive-only macaroons via `wavecli bakemacaroon`; retried requests do not pay twice. Current limits: 300,000 sats per mainnet account, 50,000 sats per VTXO, 0.25% service fee on Lightning sends and receives plus routing fees, and funds need a free automatic refresh roughly every two weeks. Docs ship llms.txt and llms-full.txt with .md twins of every page. License: MIT (GitHub repo). Related: https://wavelength.lightning.engineering/llms.txt, https://wavelength.lightning.engineering/llms-full.txt, https://wavelength.lightning.engineering/agents/, https://github.com/lightninglabs/wavelength, https://github.com/lightninglabs/wavelength/releases/tag/v0.2.0.", "tags": [ "lightning", "ark", "wallet", "mcp", "l402", "macaroons", "llms-txt", "agent-tooling" ], "verified_at": "2026-10-24", "featured": true, "last_checked": "2026-10-24", "http_status": 200, "archive_url": null }, { "id": "bitcoin-optech-newsletter-428", "title": "Bitcoin Optech Newsletter #428", "publisher": "Bitcoin Optech", "authors": [], "date_published": "2026-10-23", "url": "https://bitcoinops.org/en/newsletters/2026/10/23/", "type": "report", "category": "bitcoin-lightning", "status": "news", "summary": "Covers Lichen, a single-issuer layer 2 with trust-minimized onchain exits, and a proposal for hash-preimage syntax in descriptors (BIP379). Also covers the Eclair 0.14.4/0.14.5 security releases, the LND 0.21.5/0.20.6 release candidates, LDK #5126 (a BOLT12 one-hop blinded path CLTV fix), LND #10919 (experimental local reputation against channel jamming), BTCPay Server fixes for duplicate Lightning payouts and Greenfield API key scope escalation, and BOLTs #1352 (simple taproot channel spec corrections).", "tags": [ "bitcoin", "lightning", "bolt12", "eclair", "lnd", "ldk", "btcpay", "optech" ], "verified_at": "2026-10-24", "featured": true, "last_checked": "2026-10-24", "http_status": 200, "archive_url": null }, { "id": "lightning-bolts-pr-1357-bolt11-duplicate-payment-hashes", "title": "bolt11: reject duplicate payment hashes in invoices", "publisher": "GitHub (lightning/bolts)", "authors": [ "Roasbeef" ], "date_published": "2026-10-19", "url": "https://github.com/lightning/bolts/pull/1357", "type": "spec", "category": "bitcoin-lightning", "status": "spec_released", "summary": "Merged change to the BOLT #11 specification that requires readers to reject an invoice with more than one payment hash, with updated test vectors. The PR explains that libraries differed on whether they took the first or the last payment hash, and that a popular Telegram P2P bot was exploited through this ambiguity, which matters for any system that pays or verifies invoices automatically.", "tags": [ "lightning", "standards", "security", "m2m-payments" ], "verified_at": "2026-10-21", "featured": true, "last_checked": "2026-10-21", "http_status": 200, "archive_url": null }, { "id": "bitcoin-optech-newsletter-427", "title": "Bitcoin Optech Newsletter #427", "publisher": "Bitcoin Optech", "authors": [], "date_published": "2026-10-16", "url": "https://bitcoinops.org/en/newsletters/2026/10/16/", "type": "report", "category": "bitcoin-lightning", "status": "news", "summary": "Newsletter for the week of 2026-10-16. It summarizes the disclosure of two denial-of-service vulnerabilities in Eclair v0.14.0 and earlier, both fixed in v0.14.1, and Adam Gibson's proposal for running multi-round two-party contracts inside a Lightning channel while settling disputes on-chain in a constant number of transactions.", "tags": [ "lightning", "security", "standards" ], "verified_at": "2026-10-22", "last_checked": "2026-10-22", "http_status": 200, "archive_url": null }, { "id": "lightning-enable-l402-is-ready", "title": "L402 Is Ready. The Missing Layer Is Adoption.", "publisher": "Lightning Enable", "authors": [ "Michael Rahel" ], "date_published": "2026-10-15", "url": "https://docs.lightningenable.com/blog/l402-is-ready-the-missing-layer-is-adoption", "type": "announcement", "category": "bitcoin-lightning", "status": "news", "summary": "Michael Rahel writes that L402 is ready and that adoption is the missing layer. The post describes an HTTP 402 response carrying a Lightning invoice and a macaroon, then a retry that presents the token and the payment preimage.", "tags": [ "l402", "lightning", "macaroons", "m2m-payments" ], "verified_at": "2026-10-22", "featured": true, "last_checked": "2026-10-22", "http_status": 200, "archive_url": null }, { "id": "lightning-labs-l402-for-agents", "title": "The Future Is Now: Why L402 Is the Internet-Native Payments Protocol for Agents", "publisher": "Lightning Labs", "authors": [ "Michael Levin" ], "date_published": "2026-03-11", "url": "https://lightning.engineering/posts/2026-03-11-L402-for-agents/", "type": "announcement", "category": "bitcoin-lightning", "status": "news", "summary": "Lightning Labs post explaining how L402 puts HTTP 402 Payment Required to work by pairing it with the Lightning Network and cryptographic authentication tokens. Any Lightning-enabled client can pay for and authenticate with an L402 API instantly, with no signup, API key or prior relationship, and the post covers updates to the L402 bLIP specification.", "tags": [ "l402", "lightning", "bitcoin", "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/20260703094933/https://lightning.engineering/posts/2026-03-11-L402-for-agents/" }, { "id": "lightning-labs-agent-tools-launch", "title": "The Agents Are Here and They Want to Transact: Powering the AI Economy with Lightning", "publisher": "Lightning Labs", "authors": [ "Michael Levin" ], "date_published": "2026-02-11", "url": "https://lightning.engineering/posts/2026-02-11-ln-agent-tools/", "type": "announcement", "category": "bitcoin-lightning", "status": "news", "summary": "Launch post for Lightning Agent Tools: seven composable open-source skills that let AI agents run Lightning nodes, pay L402-gated APIs, host paid endpoints and query nodes via MCP. It also introduces lnget, an L402-aware command-line HTTP client.", "tags": [ "lightning", "l402", "agent-wallets", "mcp", "bitcoin" ], "verified_at": "2026-10-20", "featured": true, "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260908091514/https://lightning.engineering/posts/2026-02-11-ln-agent-tools/" }, { "id": "nip-47-bolt12-pull-1952", "title": "Adding support for main bolt12 commands to NIP-47", "publisher": "GitHub (nostr-protocol/nips)", "authors": [ "21M4TW" ], "date_published": "2025-06-11", "url": "https://github.com/nostr-protocol/nips/pull/1952", "type": "spec", "category": "bitcoin-lightning", "status": "proposal", "summary": "Open pull request, not merged as of 2026-10-22, that asks NIP-47 to let a Lightning client use Nostr Wallet Connect to create BOLT12 offers and to fetch and pay BOLT12 invoices. NWC BOLT12 offer creation and payment is not standardized yet, so check wallet support.", "tags": [ "nostr", "nwc", "bolt12", "lightning", "standards" ], "verified_at": "2026-10-22", "last_checked": "2026-10-22", "http_status": 200, "archive_url": null }, { "id": "lightning-labs-ai-for-all-langchain", "title": "AI for All: Powering APIs and Large Language Models with Lightning", "publisher": "Lightning Labs", "authors": [ "Olaoluwa Osuntokun", "Michael Levin" ], "date_published": "2023-07-06", "url": "https://lightning.engineering/posts/2023-07-05-l402-langchain/", "type": "announcement", "category": "bitcoin-lightning", "status": "news", "summary": "Lightning Labs announcement of developer tools built on L402 and LangChain, including LangChainBitcoin. With these tools, agents can hold a Bitcoin balance, send and receive over Lightning, and pay for L402-gated APIs.", "tags": [ "l402", "lightning", "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/20260422152959/https://lightning.engineering/posts/2023-07-05-l402-langchain/" }, { "id": "podcast-namespace-value-spec", "title": "The \"podcast:value\" Specification", "publisher": "Podcast Index (podcast-namespace)", "authors": [ "Dave Jones", "Gigi", "Evan Feenstra", "Paul Itoi" ], "date_published": "2021-09-01", "url": "https://github.com/Podcastindex-org/podcast-namespace/blob/main/docs/examples/value/value.md", "type": "spec", "category": "bitcoin-lightning", "status": "spec_released", "summary": "Podcasting 2.0 specification (v1.4) for a feed-level \"value block\" that lets listeners stream near-real-time Lightning micropayments directly to creators (for example via keysend), calculated per minute of consumption.", "tags": [ "lightning", "streaming-payments", "micropayments", "bitcoin" ], "verified_at": "2026-10-20", "featured": true, "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261016002843/https://github.com/Podcastindex-org/podcast-namespace/blob/main/docs/examples/value/value.md" }, { "id": "arxiv-lightning-micropayments-iot", "title": "Enabling Micro-payments on IoT Devices using Bitcoin Lightning Network", "publisher": "arXiv", "authors": [ "Ahmet Kurt", "Suat Mercan", "Enes Erdin", "Kemal Akkaya" ], "date_published": "2020-12-19", "url": "https://arxiv.org/abs/2012.10576", "type": "research-paper", "category": "bitcoin-lightning", "status": "research", "summary": "Proposes a protocol that lets resource-constrained IoT devices use Lightning through a gateway node, with 3-of-3 multisignature channels so the device signs every channel operation. It was demonstrated on a Raspberry Pi in a toll-payment scenario.", "tags": [ "lightning", "iot", "m2m-payments", "micropayments", "research" ], "verified_at": "2026-10-20", "featured": true, "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260403081751/https://arxiv.org/abs/2012.10576" }, { "id": "lightning-network-paper", "title": "The Bitcoin Lightning Network: Scalable Off-Chain Instant Payments", "publisher": "lightning.network", "authors": [ "Joseph Poon", "Thaddeus Dryja" ], "date_published": "2016-01-14", "url": "https://lightning.network/lightning-network-paper.pdf", "type": "research-paper", "category": "bitcoin-lightning", "status": "research", "summary": "Foundational paper (draft v0.5.9.2) proposing a decentralized network of micropayment channels whose value transfers happen off-blockchain. The aim is to scale Bitcoin to high transaction volumes without custodial third parties.", "tags": [ "lightning", "bitcoin", "micropayments", "research" ], "verified_at": "2026-10-20", "featured": true, "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261012231826/http://lightning.network/lightning-network-paper.pdf" }, { "id": "lightning-agent-tools-github", "title": "lightninglabs/lightning-agent-tools", "publisher": "GitHub (Lightning Labs)", "authors": [], "date_published": null, "url": "https://github.com/lightninglabs/lightning-agent-tools", "type": "repo", "category": "bitcoin-lightning", "status": "product_docs", "summary": "AI agent toolkit (skills plus an MCP server) for Lightning payments: node operation, L402 API payments, paid endpoint hosting and scoped macaroon credentials. Its default security model uses a remote signer that keeps private keys off the agent machine.", "tags": [ "lightning", "l402", "agent-wallets", "mcp", "security" ], "verified_at": "2026-10-20", "featured": true, "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260519020054/https://github.com/lightninglabs/lightning-agent-tools" }, { "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" }, { "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" }, { "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" }, { "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" }, { "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" }, { "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" }, { "id": "bolt-12-offers-spec", "title": "BOLT #12: Negotiation Protocol for Lightning Payments", "publisher": "GitHub (lightning/bolts)", "authors": [], "date_published": null, "url": "https://github.com/lightning/bolts/blob/master/12-offer-encoding.md", "type": "spec", "category": "bitcoin-lightning", "status": "spec_released", "summary": "Lightning specification for offers, invoice requests, invoices, invoice errors and payer proofs. It is designed to address limitations of the BOLT 11 invoice format.", "tags": [ "lightning", "bolt12", "bitcoin", "identity" ], "verified_at": "2026-10-20", "featured": true, "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261011083615/https://github.com/lightning/bolts/blob/master/12-offer-encoding.md" }, { "id": "bolt12-org", "title": "BOLT 12", "publisher": "bolt12.org", "authors": [], "date_published": null, "url": "https://bolt12.org/", "type": "docs", "category": "bitcoin-lightning", "status": "product_docs", "summary": "Explainer site for BOLT 12, a protocol upgrade to the Lightning Network that enables reusable payment requests, stronger receiver privacy and better censorship resistance.", "tags": [ "lightning", "bolt12", "bitcoin" ], "verified_at": "2026-10-20", "featured": true, "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260626222536/https://bolt12.org/" }, { "id": "nostr-nip-47-wallet-connect", "title": "NIP-47: Nostr Wallet Connect (NWC)", "publisher": "GitHub (nostr-protocol/nips)", "authors": [], "date_published": null, "url": "https://github.com/nostr-protocol/nips/blob/master/47.md", "type": "spec", "category": "bitcoin-lightning", "status": "spec_released", "summary": "Nostr Implementation Possibility that defines a standardized protocol for clients to access a remote Lightning wallet over Nostr, with commands such as pay_invoice and make_invoice.", "tags": [ "lightning", "nostr", "nwc", "agent-wallets" ], "verified_at": "2026-10-20", "featured": true, "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261009054929/https://github.com/nostr-protocol/nips/blob/master/47.md" }, { "id": "bitcoin-whitepaper", "title": "Bitcoin: A Peer-to-Peer Electronic Cash System", "publisher": "bitcoin.org", "authors": [ "Satoshi Nakamoto" ], "date_published": null, "url": "https://bitcoin.org/bitcoin.pdf", "type": "research-paper", "category": "bitcoin-lightning", "status": "research", "summary": "Foundational paper proposing purely peer-to-peer electronic cash. A proof-of-work timestamp chain solves double-spending without a trusted third party.", "tags": [ "bitcoin", "research" ], "verified_at": "2026-10-20", "featured": true, "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261015235313/https://bitcoin.org/bitcoin.pdf" }, { "id": "lightninglabs-lnget-github", "title": "lightninglabs/lnget", "publisher": "GitHub (Lightning Labs)", "authors": [], "date_published": null, "url": "https://github.com/lightninglabs/lnget", "type": "repo", "category": "bitcoin-lightning", "status": "product_docs", "summary": "A wget/curl-style command-line client that pays L402 Lightning invoices automatically, caches the resulting tokens and retries the request. Per the docs it offers JSON output, a per-request spending cap and an MCP mode for agents.", "tags": [ "l402", "lightning", "agent-wallets", "tools", "mcp" ], "verified_at": "2026-10-20", "featured": true, "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260211194037/https://github.com/lightninglabs/lnget" }, { "id": "lightning-agent-tools-l402-and-lnget", "title": "L402 and lnget (lightning-agent-tools docs)", "publisher": "GitHub (Lightning Labs)", "authors": [], "date_published": null, "url": "https://github.com/lightninglabs/lightning-agent-tools/blob/main/docs/l402-and-lnget.md", "type": "docs", "category": "bitcoin-lightning", "status": "product_docs", "summary": "Lightning Labs guide on how agents use lnget to reach L402-gated endpoints, covering backend options (lnd, Lightning Node Connect, embedded Neutrino) and bounded per-request spending.", "tags": [ "l402", "lightning", "agent-wallets", "security" ], "verified_at": "2026-10-20", "featured": true, "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260320133408/https://github.com/lightninglabs/lightning-agent-tools/blob/main/docs/l402-and-lnget.md" }, { "id": "getalby-mcp-github", "title": "getAlby/mcp", "publisher": "GitHub (Alby)", "authors": [], "date_published": null, "url": "https://github.com/getAlby/mcp", "type": "repo", "category": "bitcoin-lightning", "status": "product_docs", "summary": "An MCP server that connects an LLM agent to a Lightning wallet over Nostr Wallet Connect (NWC).", "tags": [ "lightning", "nwc", "nostr", "mcp", "agent-wallets" ], "verified_at": "2026-10-20", "featured": true, "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260505141713/https://github.com/getAlby/mcp" }, { "id": "l402-org", "title": "L402: native payments for MCP, AI agents, APIs and data", "publisher": "l402.org", "authors": [], "date_published": null, "url": "https://www.l402.org/", "type": "spec", "category": "bitcoin-lightning", "status": "product_docs", "summary": "Site describing an offers-based L402 flow in which a server answers HTTP 402 with JSON payment offers and the client retries after payment. This is distinct from Lightning Labs’ macaroon-based L402 specification. The site does not name another publisher.", "tags": [ "l402", "lightning", "m2m-payments", "mcp" ], "verified_at": "2026-10-20", "featured": true, "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260927044919/https://www.l402.org/" }, { "id": "nostr-nip-90-data-vending-machine", "title": "NIP-90: Data Vending Machine", "publisher": "GitHub (nostr-protocol/nips)", "authors": [], "date_published": null, "url": "https://github.com/nostr-protocol/nips/blob/master/90.md", "type": "spec", "category": "bitcoin-lightning", "status": "spec_released", "summary": "Nostr spec for on-demand computation ('money in, data out'). Customers publish job requests (kinds 5000-5999), service providers return results (6000-6999) and feedback (7000), and payment is typically made over Lightning. The spec itself is marked draft and 'unrecommended'.", "tags": [ "nostr", "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/20261007111747/https://github.com/nostr-protocol/nips/blob/master/90.md" }, { "id": "l402apps-com", "title": "L402 Apps", "publisher": "L402 Apps", "authors": [], "date_published": null, "url": "https://www.l402apps.com/", "type": "directory", "category": "bitcoin-lightning", "status": "product_docs", "summary": "Directory of apps and APIs presented as reachable through L402 payment gateways.", "tags": [ "l402", "lightning", "directory" ], "verified_at": "2026-10-20", "featured": true, "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260615114727/https://www.l402apps.com/" }, { "id": "voltage-cli", "title": "Voltage CLI", "publisher": "Voltage", "authors": [], "date_published": null, "url": "https://github.com/voltagecloud/voltage-cli", "type": "repo", "category": "bitcoin-lightning", "status": "product_docs", "summary": "Command-line client for the Voltage API. The README says it creates wallets and receives and sends Lightning payments, and on-chain payments where enabled, from a terminal, a script, or an AI agent. A change is only described until --execute is added. Every payment carries an ID, and the CLI never resubmits one on its own. Output is a table on a terminal and stable JSON when piped. License: MIT. Related: https://voltage.cloud/blog/prompt-to-payment-lightning-cli-agent-pack.", "tags": [ "lightning", "bitcoin", "tools", "agent-wallets" ], "verified_at": "2026-10-23", "featured": false, "last_checked": "2026-10-23", "http_status": 200, "archive_url": null }, { "id": "x402-python-sdk-2-27-0", "title": "x402 Python SDK 2.27.0", "publisher": "x402 Foundation", "authors": [], "date_published": "2026-11-04", "url": "https://pypi.org/project/x402/2.27.0/", "type": "repo", "category": "payments", "status": "product_docs", "summary": "Python package x402 2.27.0. PyPI lists the upload at 2026-11-04T20:03:25Z. The changelog heading is [2.27.0] - 2026-11-04. SVM exact payments in this SDK support Solana transaction version 1: facilitators advertise and accept extra.transactionVersions [0, 1] by default, and clients build the highest shared version. transaction_versions=[0] keeps a signer on version 0. The changelog describes this as the Python SDK, not as a requirement of every exact scheme. SIWX record_nonce runs after access is granted, and incomplete nonce-tracking is rejected. The upto Permit2 facilitator returns structured invalid_upto_evm_payload and invalid_upto_evm_required_amount errors. A throwing after_verify, after_settle, on_verify_failure, or on_settle_failure hook is logged and skipped; before_verify and before_settle still fail closed. x402[svm] requires solders>=0.29.0 and httpx and no longer installs solana. The GitHub releases API returned 404 for tag pypi-x402@v2.27.0 on 2026-11-06. Changelog: https://github.com/x402-foundation/x402/blob/main/python/x402/CHANGELOG.md. Related library entry: coinbase-x402-github (https://github.com/coinbase/x402).", "tags": [ "x402", "sdk" ], "verified_at": "2026-11-06", "featured": false, "last_checked": "2026-11-06", "http_status": 200, "archive_url": null }, { "id": "arxiv-2611-05586-anduin-x402-reputation", "title": "Anduin: A Sybil-Resistant Agentic Marketplace Reputation System", "publisher": "Circle Research (arXiv)", "authors": [ "Reza Ramji", "Preston Vander Vos", "Ziming Zeng", "Duc V. Le" ], "date_published": "2026-11-03", "url": "https://arxiv.org/abs/2611.05586", "type": "research-paper", "category": "payments", "status": "research", "summary": "Research paper, arXiv 2611.05586v1, submitted 2026-11-03. The PDF title is Anduin: A Sybil-Resistant Agentic Marketplace Reputation System. It lists Reza Ramji, Preston Vander Vos, Ziming Zeng, and Duc V. Le under Circle Research. A footnote says Ramji's work was done while the author was at Circle. The paper asks whether provider ratings can be built from payments already settled onchain, without changing the payment protocol. The introduction reports 66,073,201 x402 payments across 16 blockchains from 2026-03-23 through 2026-08-26, from 162,882 buyers and 50,390 providers, totalling $6.1 million, with a median payment of $0.01. Ratings come from a bipartite buyer-provider payment graph. Theorems 5.1 and 5.2 bound the max-flow rating by the attacker's outlay and, for that construction, by the querying buyer's own historical spend, under the paper's graph assumptions. This is not a production deployment. Section 6 uses a 90-day look-back ending 2026-06-21 and a cohort of 813 buyers. For the amplified construction with fee-inclusive dollar weights, Table 3 reports a top-1 capture cost of $8,259, 20 percent of those buyers' combined spend of $41,331, against $358 for collaborative filtering in the same row. Appendix A gives the authors' identification rules. On EVM they use EIP-3009 and the Permit2 exact and upto proxy addresses, and they keep direct EIP-3009 and multicall rows only when the facilitator or seller is already known. On Solana they keep an outgoing stablecoin transfer whose fee payer differs from the source authority when the fee payer is a known facilitator or the destination is a known seller. The appendix says EIP-3009, multicall, and Solana transfers with both an unknown facilitator and an unregistered seller are not captured.", "tags": [ "x402", "research", "reputation", "sybil" ], "verified_at": "2026-11-08", "featured": false, "last_checked": "2026-11-08", "http_status": 200, "archive_url": null }, { "id": "stripe-link-cli", "title": "stripe/link-cli", "publisher": "Stripe (GitHub)", "authors": [], "date_published": "2026-10-29", "url": "https://github.com/stripe/link-cli", "type": "repo", "category": "payments", "status": "product_docs", "summary": "MIT-licensed CLI. The README says it lets an agent get payment credentials for one-time purchases and recurring payments without storing the card, and that it can run as a local MCP server with command link-cli and args --mcp. It says this is available to US and Canadian Link accounts. GitHub published @stripe/link-cli 1.0.0 on 2026-10-29: generated MCP configs run the installed binary instead of npx, and balance eligibility is removed from user info. 1.0.1 on 2026-10-30 fixes MPP payments rejected after approval and adds --use-approval-policy to mpp pay. The README documents mpp pay for Machine Payments Protocol purchases. A Tempo customer story says Link balances are settled in stablecoins on Tempo and are rolling out to Instinct users in eligible US regions. It does not name USDC for that balance.", "tags": [ "agent-wallets", "mcp", "tools" ], "verified_at": "2026-10-31", "featured": false, "last_checked": "2026-10-31", "http_status": 200, "archive_url": null }, { "id": "stripe-treasury-for-agents", "title": "Introducing Stripe Treasury for agents", "publisher": "Stripe", "authors": [], "date_published": "2026-10-21", "url": "https://stripe.com/newsroom/news/treasury-for-agents", "type": "announcement", "category": "payments", "status": "news", "summary": "Stripe announced Stripe Treasury for agents, which lets a startup use an agent to check balances, pay invoices, transfer funds, and convert currencies. The business chooses which accounts and data the agent can access, whether it can read or take action, and when money movement requires human approval; the page says creating cards is coming soon and spending limits follow in the coming weeks.", "tags": [ "agent-wallets", "mcp", "tools" ], "verified_at": "2026-10-22", "last_checked": "2026-10-22", "http_status": 200, "archive_url": null }, { "id": "singularity-layer-training-lab-x402", "title": "Training Lab, now over x402", "publisher": "Singularity Layer", "authors": [], "date_published": "2026-10-21", "url": "https://www.x402layer.cc/blog/training-lab-x402", "type": "announcement", "category": "payments", "status": "news", "summary": "Singularity Layer's Training Lab post says an agent can request a training run, receive HTTP 402 with an exact price, and pay in USDC on Base or Solana or in USDG on Robinhood Chain. It states a limit of up to $500 per order and 3 paid runs per wallet per day over x402.", "tags": [ "x402", "stablecoins", "micropayments", "tools" ], "verified_at": "2026-10-22", "last_checked": "2026-10-22", "http_status": 200, "archive_url": null }, { "id": "polygon-oms-agent-spend-controls", "title": "Agent spend controls in Polygon Open Money Stack", "publisher": "Polygon Labs", "authors": [], "date_published": "2026-10-21", "url": "https://polygon.technology/blog/agent-spend-controls", "type": "announcement", "category": "payments", "status": "news", "summary": "Polygon Labs post, dated 2026-10-21, introducing agent spend controls in Polygon Open Money Stack. A product creates a scoped permission on a wallet the customer already uses: a stablecoin budget, approved payment actions, and an expiry. The worked example is a maximum USDC spend. The post says those terms are recorded in the wallet's onchain Sessions Module, that the agent and backend cannot increase the budget, widen the approved actions, or extend the expiry after approval, and that the wallet rejects a request outside the rule at the contract level. The team can turn the rule off. The post links the Smart Sessions docs at https://docs.polygon.technology/wallets/smart-sessions. Those docs say a remote party gets limited, time-bounded, revocable access, enforced by the on-chain Sessions Module; approved grants are native-token or ERC-20 transfer grants; the remote backend cannot broaden its own grants; and the wallet owner revokes one session with revokeAccess. The docs index https://docs.polygon.technology/llms.txt links that page. The post does not name a chain id or a contract address.", "tags": [ "agent-wallets", "stablecoins", "spend-controls" ], "verified_at": "2026-10-27", "featured": false, "last_checked": "2026-10-27", "http_status": 200, "archive_url": null }, { "id": "visa-bill-billtrust-trusted-agent-b2b-pilot", "title": "Visa, BILL and Billtrust Launch First Live Pilot for Trusted AI Agent Payments Between Buyer and Supplier Platforms", "publisher": "Visa", "authors": [], "date_published": "2026-10-20", "url": "https://investor.visa.com/news/news-details/2026/Visa-BILL-and-Billtrust-Launch-First-Live-Pilot-for-Trusted-AI-Agent-Payments-Between-Buyer-and-Supplier-Platforms/default.aspx", "type": "announcement", "category": "payments", "status": "news", "summary": "Visa press release on a live pilot in which a BILL payment agent, registered through Visa's Trusted Agent Protocol and Agentic Directory, uses tokenized credentials to pay approved supplier invoices through Billtrust portals. Billtrust uses the Trusted Agent Protocol to recognize and authenticate the agent in place of CAPTCHA-style bot blocking, without a separate agent login.", "tags": [ "card-networks", "identity", "tokenization", "m2m-payments" ], "verified_at": "2026-10-21", "featured": false, "last_checked": "2026-10-21", "http_status": 200, "archive_url": null }, { "id": "theblock-mastercard-agent-pay-early-access", "title": "Mastercard opens early access to AI agent payments following pilots with Coinbase, Base and Cloudflare", "publisher": "The Block", "authors": [ "James Hunt" ], "date_published": "2026-10-20", "url": "https://www.theblock.co/news/business/2026-10-20-mastercard-opens-early-access-to-ai-agent-payments-following-pilots-with-coinbase-base-and-cloudflare-421406", "type": "announcement", "category": "payments", "status": "news", "summary": "The Block reports that Mastercard has opened early access to Agent Pay for Machines, including buyer- and seller-side APIs, a developer toolkit, and a sandbox, after pilots with Cloudflare, Ant International, BVNK, AIsa, Base, and Coinbase. The article says the project is still a pilot and is not commercially available. In a Cloudflare Connect demonstration, an agent made nine payments to two providers using x402; Coinbase Developer Platform supplied the wallet and Base was the settlement network. Merchants returned HTTP 402, payment vouchers can be batched, and BVNK used Mastercard's Global Money Platform so sellers can be paid in fiat or stablecoins.", "tags": [ "x402", "stablecoins", "card-networks", "m2m-payments" ], "verified_at": "2026-10-21", "last_checked": "2026-10-21", "http_status": 200, "archive_url": null }, { "id": "mastercard-agent-pay-for-machines-in-action", "title": "What happens when AI agents start paying each other? Watch Mastercard Agent Pay for Machines in action", "publisher": "Mastercard", "authors": [], "date_published": "2026-10-20", "url": "https://www.mastercard.com/global/en/news-and-trends/press/2026/october/Mastercard-Agent-Pay-for-Machines-in-action.html", "type": "announcement", "category": "payments", "status": "news", "summary": "Mastercard's press page describes Agent Pay for Machines as an x402-based flow in which a service returns HTTP 402 and an agent presents a digitally signed payment voucher within a spending limit that providers can combine and redeem later. Early Access covers buyer- and seller-side APIs; the Cloudflare Connect pilot names Coinbase Developer Platform for wallet funding, Base as the on-chain settlement network, and BVNK as the agent wallet.", "tags": [ "x402", "card-networks", "m2m-payments", "agent-wallets" ], "verified_at": "2026-10-22", "last_checked": "2026-10-22", "http_status": 200, "archive_url": null }, { "id": "circle-cpn-managed-payments", "title": "Turn Agent Traffic Into Revenue With CPN Managed Payments", "publisher": "Circle", "authors": [], "date_published": "2026-10-19", "url": "https://www.circle.com/blog/turn-agent-traffic-into-revenue-with-cpn-managed-payments", "type": "announcement", "category": "payments", "status": "news", "summary": "Circle blog post on CPN Managed Payments for eligible businesses that sell data, content, or access to AI agents. The business keeps the product, pricing, metering, and customer relationship. Circle screens and accepts each payment, attributes it to the business, and pays out to the business's bank account in local currency when requested. The post's example is an x402- or MPP-enabled API charged at 0.002 USDC per call.", "tags": [ "stablecoins", "x402", "m2m-payments" ], "verified_at": "2026-10-21", "last_checked": "2026-10-21", "http_status": 200, "archive_url": null }, { "id": "proof-circle-agents-prove-who-they-act-for-and-pay-in-usdc", "title": "Proof and Circle Show How AI Agents Can Prove Who They Act For and Pay in USDC", "publisher": "Proof", "authors": [], "date_published": "2026-10-19", "url": "https://www.proof.com/blog/proof-and-circle-show-how-ai-agents-can-prove-who-they-act-for-and-pay-in-usdc", "type": "announcement", "category": "payments", "status": "news", "summary": "Proof and Circle Internet Group announced a collaboration and a Money20/20 demonstration in which an agent presents a Proof credential via x401 and pays the merchant in USDC over x402 from a Circle Agent Wallet.", "tags": [ "x402", "identity", "stablecoins", "agent-wallets" ], "verified_at": "2026-10-22", "last_checked": "2026-10-22", "http_status": 200, "archive_url": null }, { "id": "chainalysis-north-america-2026-agentic-x402", "title": "2026 North America Crypto Adoption: $3.02T, Agentic Rails", "publisher": "Chainalysis", "authors": [ "Chainalysis Team" ], "date_published": "2026-10-14", "url": "https://www.chainalysis.com/blog/north-america-crypto-adoption-2026/", "type": "report", "category": "payments", "status": "research", "summary": "Chapter of Chainalysis' 2026 Geography of Crypto report that includes on-chain research on x402 agent payments. It reports over 138 million x402 transactions on Base by the end of the period, with more than 87% of payments between a hundredth of a cent and ten cents. It also finds that the share of agent wallets that received a second funding within 30 days of the first rose from 70.6% (Q3 2025 cohort) to 89.3% (Q2 2026 cohort). American wallets account for 88.1% of geolocated AI model inference transactions, 41.8% of payments to agent frameworks and tool catalogs, and 23.2% of payments to data and search APIs. Chinese-funded AI agents took 0.1% of model inference.", "tags": [ "x402", "stablecoins", "micropayments", "m2m-payments", "market-data" ], "verified_at": "2026-10-23", "featured": false, "last_checked": "2026-10-23", "http_status": 200, "archive_url": null }, { "id": "shop-mcp", "title": "Add shopping and Shop Pay checkout to any agent with Shop MCP", "publisher": "Shopify", "authors": [], "date_published": "2026-10-13", "url": "https://shopify.dev/changelog/posts/add-shopping-and-shop-pay-checkout-to-any-agent-with-shop-mcp", "type": "docs", "category": "payments", "status": "product_docs", "summary": "Shopify changelog post dated 2026-10-13. It says Shop MCP is live at https://mcp.shop.com, with a skill description at https://mcp.shop.com/skill.md. Search and product tools named there are search_catalog, lookup_catalog, and get_product. It says search works without credentials, and that an API key is created in the Shopify Dev Dashboard. It says carts and checkout work without sign-in, and that a signed-in shopper's purchase is completed with complete_checkout after the shopper confirms the total and payment method. The Shop Pay docs say the buyer connects a Shop account once and approves each purchase in Shop Pay, and that the agent gets a one-time credential to complete checkout, even outside Shopify: https://shopify.dev/docs/agents/carts-and-checkout/shop-pay.", "tags": [ "mcp", "agentic-commerce", "tools" ], "verified_at": "2026-10-31", "featured": false, "last_checked": "2026-10-31", "http_status": 200, "archive_url": null }, { "id": "blackrock-machine-native-economy", "title": "The Machine-Native Economy: AI and Digital Assets", "publisher": "BlackRock", "authors": [ "Robert Mitchnick" ], "date_published": "2026-10-05", "url": "https://www.blackrock.com/us/financial-professionals/insights/machine-native-economy", "type": "report", "category": "payments", "status": "research", "summary": "BlackRock insight arguing that LLMs and blockchains share a machine-native, token-based foundation and that agentic commerce requires machine-native payment rails. It states that stablecoins and native cryptoassets can serve as machine-native instruments for machine-to-machine payments.", "tags": [ "stablecoins", "m2m-payments", "tokenization", "market-data" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261009205047/https://www.blackrock.com/us/financial-professionals/insights/machine-native-economy" }, { "id": "cloudflare-monetization-gateway-x402", "title": "x402 protocol", "publisher": "Cloudflare", "authors": [], "date_published": "2026-09-30", "url": "https://developers.cloudflare.com/monetization-gateway/x402/", "type": "docs", "category": "payments", "status": "product_docs", "summary": "Cloudflare Monetization Gateway docs for x402 version 2. The page, last updated 2026-09-30, names two client-facing headers, PAYMENT-REQUIRED and PAYMENT-SIGNATURE, each carrying Base64-encoded JSON. Network identifiers are CAIP-2. The gateway uses the exact scheme for a fixed price and the upto scheme for a variable price. The same product publishes https://developers.cloudflare.com/monetization-gateway/llms.txt. Its overview says the gateway can charge for MCP tools. This page does not name PAYMENT-RESPONSE and does not document a separate Monetization Gateway MCP server.", "tags": [ "x402", "http", "standards", "mcp", "llms-txt" ], "verified_at": "2026-10-22", "last_checked": "2026-10-22", "http_status": 200, "archive_url": null }, { "id": "waller-payments-age-ai-agents", "title": "Payments in the age of AI agents", "publisher": "Board of Governors of the Federal Reserve System (via BIS central bankers' speeches)", "authors": [ "Christopher J. Waller" ], "date_published": "2026-09-29", "url": "https://www.bis.org/speeches/20261005-payments-age-ai-agents", "type": "regulatory", "category": "payments", "status": "news", "summary": "Speech by Federal Reserve Governor Christopher J. Waller at Sibos 2026 in Miami on how AI agents may shape payments. Published on the BIS central bankers' speeches site.", "tags": [ "regulation", "m2m-payments", "stablecoins" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261008221104/https://www.bis.org/speeches/20261005-payments-age-ai-agents" }, { "id": "mckinsey-global-payments-report-2026", "title": "The 2026 Global Payments Report: Operational excellence in an invisible world", "publisher": "McKinsey & Company", "authors": [ "Gustavo Tayar", "Matteo Mantoan", "Uzayr Jeenah", "Amit Gandhi", "Erica Solino", "Gaia Thorel", "Julia Simchuk", "Reema Jain" ], "date_published": "2026-09-25", "url": "https://www.mckinsey.com/industries/financial-services/our-insights/global-payments-report", "type": "report", "category": "payments", "status": "research", "summary": "McKinsey's annual global payments report, which sizes the industry at roughly $2.6 trillion in revenue from 3.8 trillion transactions. It reviews growth drivers and the shift toward \"invisible\" payments.", "tags": [ "market-data", "research" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": null, "archive_url": "http://web.archive.org/web/20260930211737/https://www.mckinsey.com/industries/financial-services/our-insights/global-payments-report" }, { "id": "ietf-draft-httpauth-payment", "title": "The \"Payment\" HTTP Authentication Scheme (draft-httpauth-payment-01)", "publisher": "IETF Datatracker", "authors": [ "Brendan Ryan", "Jake Moxey", "Tom Meagher", "Jeff Weinstein", "Steve Kaliski" ], "date_published": "2026-09-09", "url": "https://datatracker.ietf.org/doc/draft-httpauth-payment/", "type": "spec", "category": "payments", "status": "individual_draft", "summary": "Internet-Draft defining a payment-method-agnostic HTTP authentication scheme for 402 flows: the server sends WWW-Authenticate: Payment with challenge parameters and the client retries with Authorization: Payment and a credential. Revision 01 is dated 2026-09-09 and is an active draft, not an RFC.", "tags": [ "m2m-payments", "http", "standards", "interop" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261014085833/https://datatracker.ietf.org/doc/draft-httpauth-payment/" }, { "id": "arxiv-2609-02208-agentic-settlement-protocol", "title": "Agentic Settlement Protocol: An Application Profile for Refundable, Delayed-Fulfilment Agent Commerce on Stablecoin Rails", "publisher": "arXiv", "authors": [ "Behnam (Beny) Mohammadkhani", "Atul Khekade", "Ritesh Kakkad" ], "date_published": "2026-09-02", "url": "https://arxiv.org/abs/2609.02208", "type": "research-paper", "category": "payments", "status": "research", "summary": "Design paper, arXiv 2609.02208, submitted 2026-09-02. It specifies the Agentic Settlement Protocol, an application profile over on-chain authorize-and-capture escrow for agent purchases whose fulfilment is confirmed off-chain and which can be refunded. The abstract lists a normative interface specification (x402 scheme, vault ABI, operator and connector APIs, conformance levels). The abstract page names a 17-case conformance suite in Appendix B, and the HTML edition's Appendix F requires Appendix B cases 1-17 for ASP-Lite. The reference deployment targets the XDC Network. The abstract says measurement is left to follow-up work.", "tags": [ "x402", "stablecoins", "agentic-commerce", "research" ], "verified_at": "2026-10-25", "featured": false, "last_checked": "2026-10-25", "http_status": 200, "archive_url": null }, { "id": "arxiv-beyond-the-mandate-ap2-security", "title": "Beyond the Mandate: A Systematic Security Analysis of the Agent Payments Protocol (AP2)", "publisher": "arXiv", "authors": [ "Avital Aviv", "Parth A. Gandh", "Ron Bitton", "Asaf Shabtai" ], "date_published": "2026-08-24", "url": "https://arxiv.org/abs/2608.23858", "type": "research-paper", "category": "payments", "status": "research", "summary": "Security analysis of Google's AP2. It finds that signed Checkout and Payment Mandates protect transaction data after signing, while agent interactions before authorization (A2A messages, MCP inputs) stay outside that protection.", "tags": [ "ap2", "security", "research" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260923112346/https://arxiv.org/abs/2608.23858" }, { "id": "linux-foundation-x402-foundation-operational-launch", "title": "Linux Foundation Announces Operational Launch of x402 Foundation to Standardize Internet-Native Payments for AI Agents and Applications", "publisher": "The Linux Foundation", "authors": [], "date_published": "2026-07-14", "url": "https://www.linuxfoundation.org/press/linux-foundation-announces-operational-launch-of-x402-foundation-to-standardize-internet-native-payments-for-ai-agents-and-applications", "type": "announcement", "category": "payments", "status": "news", "summary": "Press release announcing the operational launch of the x402 Foundation under the Linux Foundation, with 40 founding members, to steward x402 as an open standard for internet-native payments by AI agents and applications.", "tags": [ "x402", "m2m-payments", "agent-wallets" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260921055124/https://www.linuxfoundation.org/press/linux-foundation-announces-operational-launch-of-x402-foundation-to-standardize-internet-native-payments-for-ai-agents-and-applications" }, { "id": "boe-breeden-agents-of-change", "title": "Agents of change", "publisher": "Bank of England (via BIS central bankers' speeches)", "authors": [ "Sarah Breeden" ], "date_published": "2026-06-30", "url": "https://www.bis.org/speeches/20260730-agents-change.pdf", "type": "regulatory", "category": "payments", "status": "news", "summary": "Speech by Bank of England Deputy Governor Sarah Breeden at the ECB Sintra Forum on how agentic AI is changing cyber risk, markets and payments. It argues central banks must adapt quickly, strengthen resilience and cooperate globally.", "tags": [ "regulation", "security" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261014040922/https://www.bis.org/speeches/20260730-agents-change.pdf" }, { "id": "mastercard-agent-pay-for-machines", "title": "Mastercard launches Agent Pay for Machines to unlock super-fast, always-on payments", "publisher": "Mastercard", "authors": [], "date_published": "2026-06-10", "url": "https://www.mastercard.com/us/en/news-and-trends/press/2026/june/mastercard-launches-agent-pay-for-machines.html", "type": "announcement", "category": "payments", "status": "news", "summary": "Mastercard press release launching Agent Pay for Machines, a service for continuous, high-velocity agent-to-agent transactions and microtransactions. It lists more than 30 early supporters, including Adyen, Coinbase, Stripe and Tempo.", "tags": [ "card-networks", "m2m-payments" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 403, "archive_url": "http://web.archive.org/web/20261003095645/https://www.mastercard.com/us/en/news-and-trends/press/2026/june/mastercard-launches-agent-pay-for-machines.html" }, { "id": "fed-payments-innovation-roundtable-2026-05-26", "title": "Meeting Between Board Members and Staff of the Federal Reserve System and Representatives from Payment and Technology Industries for the Payments Innovation Roundtable", "publisher": "Board of Governors of the Federal Reserve System", "authors": [], "date_published": "2026-05-26", "url": "https://www.federalreserve.gov/paymentsystems/files/payments-innovation-roundtable-meeting-20260526.pdf", "type": "regulatory", "category": "payments", "status": "news", "summary": "Meeting summary of a Federal Reserve roundtable (Governors Waller, Barr and Cook) with payments and technology firms, including Visa, Mastercard, Stripe, Coinbase, Google and Skyfire. The discussion covered AI in payments, with a particular focus on agentic commerce.", "tags": [ "regulation", "card-networks", "stablecoins" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261015115524/https://www.federalreserve.gov/paymentsystems/files/payments-innovation-roundtable-meeting-20260526.pdf" }, { "id": "solana-pay-sh-google-cloud", "title": "Solana Foundation Launches Pay.sh in Collaboration with Google Cloud", "publisher": "Solana Foundation", "authors": [], "date_published": "2026-05-05", "url": "https://solana.com/news/solana-foundation-launches-pay-sh-in-collaboration-with-google-cloud", "type": "announcement", "category": "payments", "status": "news", "summary": "Solana Foundation announcement dated 2026-05-05 of Pay.sh, built with Google Cloud. The page describes a gateway where an agent pays per request in stablecoins on Solana via x402, with no account and no API key. It names Google Cloud APIs including Gemini and BigQuery, and says the catalog also includes more than 50 community APIs. The page also says Pay.sh is built on x402 and MPP.", "tags": [ "x402", "stablecoins", "m2m-payments", "agents" ], "verified_at": "2026-10-22", "last_checked": "2026-10-22", "http_status": 200, "archive_url": null }, { "id": "imf-how-agentic-ai-will-reshape-payments", "title": "How Agentic AI Will Reshape Payments", "publisher": "International Monetary Fund", "authors": [], "date_published": "2026-04-24", "url": "https://www.imf.org/en/publications/imf-notes/issues/2026/04/22/how-agentic-ai-will-reshape-payments-575560", "type": "report", "category": "payments", "status": "research", "summary": "IMF Note examining how agentic AI may affect authorization, liquidity, settlement, compliance and resilience in payment systems, using an intent, authorization and settlement framework. It highlights the tension between probabilistic AI behavior and the deterministic requirements of payment infrastructure.", "tags": [ "regulation", "research", "security" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260629110549/https://www.imf.org/en/publications/imf-notes/issues/2026/04/22/how-agentic-ai-will-reshape-payments-575560" }, { "id": "arxiv-sok-security-llm-agents-agentic-commerce", "title": "SoK: Security of Autonomous LLM Agents in Agentic Commerce", "publisher": "arXiv", "authors": [ "Qian'ang Mao", "Jiaxin Wang", "Ya Liu", "Li Zhu", "Cong Ma", "Jiaqi Yan" ], "date_published": "2026-04-15", "url": "https://arxiv.org/abs/2604.15367", "type": "research-paper", "category": "payments", "status": "research", "summary": "Systematization of knowledge on the security of autonomous LLM agents that negotiate, purchase and transact across on-chain and off-chain environments. It covers protocols such as ERC-8004 and AP2.", "tags": [ "security", "ap2", "research", "identity" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261006050702/https://arxiv.org/abs/2604.15367" }, { "id": "arxiv-apex-agent-payment-execution", "title": "APEX: Agent Payment Execution with Policy for Autonomous Agent API Access", "publisher": "arXiv", "authors": [ "Mohd Safwan Uddin", "Mohammed Mouzam", "Mohammed Imran", "Syed Badar Uddin Faizan" ], "date_published": "2026-04-02", "url": "https://arxiv.org/abs/2604.02023", "type": "research-paper", "category": "payments", "status": "research", "summary": "Research system that adapts HTTP 402-style payment gating to UPI-like real-time fiat workflows, with policy-governed spend control for autonomous agents calling APIs.", "tags": [ "m2m-payments", "research", "security" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260403123042/https://arxiv.org/abs/2604.02023" }, { "id": "linux-foundation-launching-x402-foundation", "title": "Linux Foundation is Launching the x402 Foundation and Welcoming the Contribution of the x402 Protocol", "publisher": "The Linux Foundation", "authors": [], "date_published": "2026-04-02", "url": "https://www.linuxfoundation.org/press/linux-foundation-is-launching-the-x402-foundation-and-welcoming-the-contribution-of-the-x402-protocol", "type": "announcement", "category": "payments", "status": "news", "summary": "Press release, issued at MCP Dev Summit North America, announcing a new x402 Foundation to steward the open x402 protocol for payments over HTTP.", "tags": [ "x402", "m2m-payments" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261015094937/https://www.linuxfoundation.org/press/linux-foundation-is-launching-the-x402-foundation-and-welcoming-the-contribution-of-the-x402-protocol" }, { "id": "stripe-introducing-machine-payments-protocol", "title": "Introducing the Machine Payments Protocol", "publisher": "Stripe", "authors": [ "Jeff Weinstein", "Steve Kaliski" ], "date_published": "2026-03-18", "url": "https://stripe.com/blog/machine-payments-protocol", "type": "announcement", "category": "payments", "status": "news", "summary": "Stripe blog post launching the Machine Payments Protocol (MPP), an open, internet-native standard for agent payments co-authored by Tempo and Stripe.", "tags": [ "m2m-payments", "stablecoins", "agent-wallets" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261015094944/https://stripe.com/blog/machine-payments-protocol" }, { "id": "visa-card-spec-sdk-mpp", "title": "Visa introduces card specification and SDK for Machine Payments Protocol", "publisher": "Visa", "authors": [], "date_published": "2026-03-18", "url": "https://corporate.visa.com/en/sites/visa-perspectives/innovation/visa-card-specification-sdk-for-machine-payments-protocol.html", "type": "announcement", "category": "payments", "status": "news", "summary": "Visa announcement of a card specification and SDK that enable card-based payments for autonomous agents within Stripe and Tempo's Machine Payments Protocol. It coincided with Tempo's mainnet launch.", "tags": [ "card-networks", "m2m-payments" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": null }, { "id": "arxiv-a402-binding-payments-service-execution", "title": "A402: Binding Cryptocurrency Payments to Service Execution for Agentic Commerce", "publisher": "arXiv", "authors": [ "Yue Li", "Lei Wang", "Kaixuan Wang", "Zhiqiang Yang", "Ke Wang", "Zhi Guan", "Jianbo Gao" ], "date_published": "2026-03-01", "url": "https://arxiv.org/abs/2603.01179", "type": "research-paper", "category": "payments", "status": "research", "summary": "Proposes A402, a trust-minimized payment architecture with Atomic Service Channels that bind cryptocurrency payments to service execution and result delivery. It addresses an atomicity gap the authors identify in x402.", "tags": [ "x402", "security", "research" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260815005030/https://arxiv.org/abs/2603.01179" }, { "id": "arxiv-zero-trust-runtime-verification-ap2", "title": "Zero-Trust Runtime Verification for Agentic Payment Protocols: Mitigating Replay and Context-Binding Failures in AP2", "publisher": "arXiv", "authors": [ "Qianlong Lan", "Anuj Kaul", "Shaun Jones", "Stephanie Westrum" ], "date_published": "2026-02-06", "url": "https://arxiv.org/abs/2602.06345", "type": "research-paper", "category": "payments", "status": "research", "summary": "eBay-authored paper on runtime behaviors (retries, concurrency, orchestration) that can cause replay and context-binding failures in mandate-based protocols such as AP2 and UCP. It proposes zero-trust runtime verification to mitigate them.", "tags": [ "ap2", "security", "research" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260827173930/https://arxiv.org/abs/2602.06345" }, { "id": "bis-wp1310-ai-agents-cash-management", "title": "AI agents for cash management in payment systems", "publisher": "Bank for International Settlements", "authors": [ "Iñaki Aldasoro", "Ajit Desai" ], "date_published": "2025-11-26", "url": "https://www.bis.org/publ/work1310.htm", "type": "research-paper", "category": "payments", "status": "research", "summary": "BIS Working Paper 1310 examining how generative AI can help manage cash and liquidity in real-time gross settlement (RTGS) payment systems.", "tags": [ "research", "regulation" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260610031525/https://www.bis.org/publ/work1310.htm" }, { "id": "mckinsey-agentic-commerce-opportunity", "title": "The agentic commerce opportunity: How AI agents are ushering in a new era for consumers and merchants", "publisher": "McKinsey & Company", "authors": [], "date_published": "2025-10-17", "url": "https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-agentic-commerce-opportunity-how-ai-agents-are-ushering-in-a-new-era-for-consumers-and-merchants", "type": "report", "category": "payments", "status": "research", "summary": "McKinsey QuantumBlack report on how AI agents are changing commerce for consumers and merchants.", "tags": [ "market-data", "research" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": null, "archive_url": "http://web.archive.org/web/20260613093650/https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-agentic-commerce-opportunity-how-ai-agents-are-ushering-in-a-new-era-for-consumers-and-merchants?" }, { "id": "visa-trusted-agent-protocol-press-release", "title": "Visa Introduces Trusted Agent Protocol: An Ecosystem-Led Framework for AI Commerce", "publisher": "Visa", "authors": [], "date_published": "2025-10-14", "url": "https://usa.visa.com/about-visa/newsroom/press-releases.releaseId.21716.html", "type": "announcement", "category": "payments", "status": "news", "summary": "Visa press release introducing the Trusted Agent Protocol, developed with Cloudflare, to support secure communication between AI agents and merchants and help merchants tell legitimate agents apart from malicious bots.", "tags": [ "card-networks", "identity", "security" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260621131201/https://usa.visa.com/about-visa/newsroom/press-releases.releaseId.21716.html" }, { "id": "mastercard-agentic-commerce-tools-sep-2025", "title": "Mastercard unveils new tools and collaborations to power smarter, safer agentic commerce", "publisher": "Mastercard", "authors": [], "date_published": "2025-09-10", "url": "https://www.mastercard.com/global/en/news-and-trends/press/2025/september/mastercard-unveils-new-tools-and-collaborations-to-power-smarter,-safer-agentic-commerce.html", "type": "announcement", "category": "payments", "status": "news", "summary": "Mastercard press release on new developer tools, expanded consulting services and ecosystem collaborations for AI-powered payments, aimed at trusted agentic transaction standards.", "tags": [ "card-networks", "tokenization", "identity" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 403, "archive_url": "http://web.archive.org/web/20260605202222/https://www.mastercard.com/global/en/news-and-trends/press/2025/september/mastercard-unveils-new-tools-and-collaborations-to-power-smarter,-safer-agentic-commerce.html" }, { "id": "cloudflare-pay-per-crawl", "title": "Introducing pay per crawl: Enabling content owners to charge AI crawlers for access", "publisher": "Cloudflare Blog", "authors": [], "date_published": "2025-07-01", "url": "https://blog.cloudflare.com/introducing-pay-per-crawl/", "type": "announcement", "category": "payments", "status": "news", "summary": "Cloudflare announcement of pay per crawl, which lets content owners charge AI crawlers for access using HTTP 402 responses. It is a machine-payable content model at CDN scale.", "tags": [ "m2m-payments", "micropayments", "web-agents" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261016042320/https://blog.cloudflare.com/introducing-pay-per-crawl/" }, { "id": "x402-whitepaper", "title": "x402: An open standard for internet-native payments", "publisher": "Coinbase Developer Platform", "authors": [ "Erik Reppel", "Ronnie Caspers", "Kevin Leffew", "Danny Organ", "Dan Kim", "Nemil Dalal" ], "date_published": "2025-05-06", "url": "https://www.x402.org/x402-whitepaper.pdf", "type": "spec", "category": "payments", "status": "research", "summary": "Whitepaper describing x402, an HTTP-based protocol that uses onchain payments for agents, context retrieval and APIs. It explains why traditional rails fail for autonomous payments and how x402 works.", "tags": [ "x402", "stablecoins", "m2m-payments" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260605201607/https://www.x402.org/x402-whitepaper.pdf" }, { "id": "solana-foundation-payment-channels", "title": "payment-channels", "publisher": "Solana Foundation", "authors": [], "date_published": null, "url": "https://github.com/solana-foundation/payment-channels", "type": "repo", "category": "payments", "status": "product_docs", "summary": "README of solana-foundation/payment-channels, read from main on 2026-11-16. program/payment_channels/src/lib.rs declares the program id CHNLxYvVA28MJP9PrFuDXccuoGXAx7jBacfLEkahyGsX. A mainnet-beta getAccountInfo the same day returned an executable account for that id, owned by BPFLoaderUpgradeab1e11111111111111111111111. That call does not show that the deployed binary matches this commit. The README says the token payer escrows a spending ceiling, a merchant claims only what signed off-chain vouchers authorize, and the unspent remainder is refunded. instructions/mod.rs sets VOUCHER_MAGIC to [0x56, 0x01] and asserts VOUCHER_PAYLOAD_SIZE == 50. The README table is two magic bytes, a 32-byte channel id, a little-endian u64 cumulative amount, and a little-endian i64 expires_at; 0 disables expiry. settle does not carry the voucher in its own instruction data. It reads the 50-byte message from the preceding Ed25519 precompile instruction. The README says one open and one settle replace a transaction per payment. After the channel is sealed, distribute pays the settled amount and refunds the rest. That refund is a separate instruction. The README says the program backs MPP session and x402 upto. The x402 SVM upto spec, read the same day, names this program id as the current mainnet deployment and says open escrows maxAmount and distribute refunds deposit minus the actual amount. draft-solana-session-00 describes a 50-byte voucher and a channel program whose address is declared in the challenge. It does not hardcode this program id. LICENSE is MIT, copyright 2026 Moonsong-Labs. The README does not state a mainnet launch date. GitHub records the repository as created 2026-04-14. https://solana.com/payment-channels was not read (HTTP 429). https://solana-foundation.github.io/payment-channels/ returned HTTP 200.", "tags": [ "x402", "solana" ], "verified_at": "2026-11-16", "featured": false, "last_checked": "2026-11-16", "http_status": 200, "archive_url": null }, { "id": "circle-agent-marketplace-discovery-api", "title": "Discover x402 services", "publisher": "Circle", "authors": [], "date_published": null, "url": "https://developers.circle.com/agent-stack/agent-marketplace/discovery-api", "type": "docs", "category": "payments", "status": "product_docs", "summary": "Circle's discovery page, checked 2026-11-07, says one public endpoint lists x402 services that accept USDC, with no API key and no account. The documented request is GET https://api.circle.com/v2/x402/discovery/resources. A read of that URL with limit=1 on the same day returned HTTP 200 and JSON with x402Version 2, items[].accepts[] carrying scheme, network, asset, amount, and payTo, metadata.input and metadata.output, and pagination.limit, offset, and total. The page documents filters for category, network, maxUsdPrice, supportsVanillax402, supportsCircleGateway, and siwx, and a type of http or mcp. It says limit defaults to 50 and the maximum is 200. The page links https://agents.circle.com/.well-known/openapi.json, which returned HTTP 200 the same day. This is Circle's catalog. It is not an Agent Paywire listing, and this card does not record a catalog total because that number changes.", "tags": [ "x402", "directory", "discovery", "openapi", "usdc" ], "verified_at": "2026-11-07", "featured": false, "last_checked": "2026-11-07", "http_status": 200, "archive_url": null }, { "id": "link-balance-agent-wallet-purchases", "title": "Set up a balance for agent wallet purchases", "publisher": "Link (Stripe)", "authors": [], "date_published": null, "url": "https://support.link.com/questions/set-up-a-balance-for-agent-wallet-purchases", "type": "docs", "category": "payments", "status": "product_docs", "summary": "Link support page. article:modified_time is 2026-10-21. The page does not state a publication date. Setup asks for date of birth and the last four digits of an SSN, and all nine digits if that check fails. The user sets a per-purchase limit, the maximum the agent can spend without requesting approval. Money is added with a supported credit or debit card. The page says money in the balance is held as USDC. A custodial balance is a wallet managed by Bridge, a Stripe company. A self-custodial balance is accessed with Privy, and the page says Link does not hold those assets as a custodian. An agent cannot skip approval for a purchase above the per-purchase limit.", "tags": [ "agent-wallets", "stablecoins" ], "verified_at": "2026-11-03", "featured": false, "last_checked": "2026-11-03", "http_status": 200, "archive_url": null }, { "id": "coinbase-business-accept-x402-payments", "title": "Accept Agentic Payments with x402", "publisher": "Coinbase Developer Platform", "authors": [], "date_published": null, "url": "https://docs.cdp.coinbase.com/coinbase-business/checkout-apis/accept-x402-payments", "type": "docs", "category": "payments", "status": "product_docs", "summary": "Coinbase Business Checkouts docs. The page does not state a publish date. POST https://business.coinbase.com/api/v1/checkouts returns an x402_url. The page says paying that URL authorizes a gasless USDC payment on Base using EIP-3009, and that Coinbase captures and settles it server-side. It says the checkout moves ACTIVE, then PROCESSING, then COMPLETED, and that COMPLETED is the source of truth for settlement. PROCESSING may not be observed. A rejected payment returns another 402 and leaves the checkout ACTIVE. FAILED, EXPIRED, and DEACTIVATED are also listed. The page says checkouts advertise the EVM auth-capture scheme.", "tags": [ "x402", "stablecoins" ], "verified_at": "2026-10-31", "featured": false, "last_checked": "2026-10-31", "http_status": 200, "archive_url": null }, { "id": "x402-org", "title": "x402", "publisher": "x402", "authors": [], "date_published": null, "url": "https://www.x402.org/", "type": "spec", "category": "payments", "status": "product_docs", "summary": "Official x402 site, describing it as an open standard for internet-native payments that enables agentic payments at scale.", "tags": [ "x402", "m2m-payments", "stablecoins" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261012224709/https://x402.org/" }, { "id": "coinbase-x402-github", "title": "coinbase/x402", "publisher": "GitHub (Coinbase)", "authors": [], "date_published": null, "url": "https://github.com/coinbase/x402", "type": "repo", "category": "payments", "status": "spec_released", "summary": "Reference repository for x402, \"a payments protocol for the internet. Built on HTTP.\"", "tags": [ "x402", "m2m-payments" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260917165755/https://github.com/coinbase/x402" }, { "id": "google-ap2-github", "title": "google-agentic-commerce/AP2", "publisher": "GitHub (Google Agentic Commerce)", "authors": [], "date_published": null, "url": "https://github.com/google-agentic-commerce/AP2", "type": "repo", "category": "payments", "status": "spec_released", "summary": "Official repository of the Agent Payments Protocol (AP2), described as \"Building a Secure and Interoperable Future for AI-Driven Payments.\"", "tags": [ "ap2", "identity", "security" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260913134535/https://github.com/google-agentic-commerce/AP2" }, { "id": "agentic-commerce-protocol-site", "title": "Agentic Commerce Protocol", "publisher": "Agentic Commerce Protocol", "authors": [], "date_published": null, "url": "https://www.agenticcommerce.dev/", "type": "spec", "category": "payments", "status": "product_docs", "summary": "Official ACP site describing an Apache-2.0 open standard for programmatic commerce flows between buyers, AI agents and businesses, in which businesses remain merchant of record.", "tags": [ "acp" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260916115909/https://www.agenticcommerce.dev/" }, { "id": "acp-github", "title": "agentic-commerce-protocol/agentic-commerce-protocol", "publisher": "GitHub (Agentic Commerce Protocol)", "authors": [], "date_published": null, "url": "https://github.com/agentic-commerce-protocol/agentic-commerce-protocol", "type": "repo", "category": "payments", "status": "spec_released", "summary": "Specification repository for the Agentic Commerce Protocol, an interaction model and open standard for buyers, their AI agents and businesses, currently maintained by OpenAI and Stripe.", "tags": [ "acp" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261004130551/https://github.com/agentic-commerce-protocol/agentic-commerce-protocol" }, { "id": "stripe-docs-acp", "title": "Agentic Commerce Protocol", "publisher": "Stripe Docs", "authors": [], "date_published": null, "url": "https://docs.stripe.com/agentic-commerce/protocols/acp", "type": "docs", "category": "payments", "status": "product_docs", "summary": "Stripe documentation for ACP, described as an open standard created by Stripe, OpenAI and Meta. It covers agentic checkout, cart and feed, and delegated payment and authentication building blocks.", "tags": [ "acp", "tokenization" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261016221903/https://docs.stripe.com/agentic-commerce/protocols/acp" }, { "id": "stripe-docs-mpp", "title": "MPP", "publisher": "Stripe Docs", "authors": [], "date_published": null, "url": "https://docs.stripe.com/payments/machine/mpp", "type": "docs", "category": "payments", "status": "product_docs", "summary": "Stripe documentation on accepting agent payments with the Machine Payments Protocol: servers respond with HTTP 402 and payment details, and agents authorize payment and retry to receive the resource and a receipt.", "tags": [ "m2m-payments", "stablecoins" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261014090103/https://docs.stripe.com/payments/machine/mpp" }, { "id": "visa-developer-trusted-agent-protocol", "title": "Getting started with Trusted Agent Protocol", "publisher": "Visa Developer", "authors": [], "date_published": null, "url": "https://developer.visa.com/capabilities/trusted-agent-protocol/overview", "type": "docs", "category": "payments", "status": "product_docs", "summary": "Visa developer documentation for merchants and infrastructure providers. It presents the Trusted Agent Protocol as a verifiable cryptographic standard for recognizing Visa-approved AI agents.", "tags": [ "card-networks", "identity", "security" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261012112504/https://developer.visa.com/capabilities/trusted-agent-protocol/overview" }, { "id": "visa-developer-intelligent-commerce", "title": "Visa Intelligent Commerce", "publisher": "Visa Developer", "authors": [], "date_published": null, "url": "https://developer.visa.com/capabilities/visa-intelligent-commerce/overview", "type": "docs", "category": "payments", "status": "product_docs", "summary": "Visa Developer Center product page for Visa Intelligent Commerce, available to acquirer and issuer banks. The full documentation is restricted to authorized users.", "tags": [ "card-networks", "tokenization" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 403, "archive_url": "http://web.archive.org/web/20261003065321/https://developer.visa.com/capabilities/visa-intelligent-commerce/overview" }, { "id": "bis-project-agenti", "title": "Project Agenti", "publisher": "Bank for International Settlements", "authors": [], "date_published": null, "url": "https://www.bis.org/node/87745", "type": "regulatory", "category": "payments", "status": "research", "summary": "BIS Innovation Hub project with the Bank of Canada and the Swiss National Bank that uses agentic AI to model payment behaviour and intraday liquidity in wholesale payment systems.", "tags": [ "research", "regulation" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": null }, { "id": "x402-bazaar-extension-docs", "title": "Bazaar (Discovery Layer)", "publisher": "x402 (docs.x402.org)", "authors": [], "date_published": null, "url": "https://docs.x402.org/extensions/bazaar", "type": "docs", "category": "payments", "status": "product_docs", "summary": "Documentation for the x402 Bazaar extension. Facilitators can catalog payable HTTP endpoints and MCP tools and expose list and search discovery endpoints, so agents can find x402 resources together with their input/output schemas and prices.", "tags": [ "x402", "directory", "m2m-payments", "interop" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261005104256/https://docs.x402.org/extensions/bazaar" }, { "id": "x402-bazaar-spec-github", "title": "specs/extensions/bazaar.md", "publisher": "GitHub (x402 Foundation)", "authors": [], "date_published": null, "url": "https://github.com/x402-foundation/x402/blob/main/specs/extensions/bazaar.md", "type": "spec", "category": "payments", "status": "spec_released", "summary": "Normative spec for the Bazaar extension. It covers facilitator validation of the discovery info and the optional GET /discovery/resources and /discovery/search APIs, which filter by type, payTo, scheme and network and paginate with offsets or cursors.", "tags": [ "x402", "directory", "interop" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": null }, { "id": "cdp-x402-bazaar", "title": "x402 Bazaar (Discovery Layer), CDP", "publisher": "Coinbase Developer Documentation", "authors": [], "date_published": null, "url": "https://docs.cdp.coinbase.com/x402/bazaar", "type": "docs", "category": "payments", "status": "product_docs", "summary": "Coinbase's hosted Bazaar catalog of x402 resources seen by the CDP Facilitator. It offers a public paginated list, hybrid semantic search with price, network and asset filters, and an MCP interface. The read endpoints need no API key.", "tags": [ "x402", "stablecoins", "directory", "mcp" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260712073149/https://docs.cdp.coinbase.com/x402/bazaar" }, { "id": "x402scan-discovery-spec", "title": "x402scan Discovery & Registration Spec", "publisher": "GitHub (Merit Systems)", "authors": [], "date_published": null, "url": "https://github.com/Merit-Systems/x402scan/blob/main/docs/DISCOVERY.md", "type": "spec", "category": "payments", "status": "spec_released", "summary": "Describes how x402scan discovers paid endpoints. It reads OpenAPI first, with per-operation x-payment-info pricing and a declared 402 response, and falls back to a /.well-known/x402 resource list. The live 402 challenge overrides static metadata.", "tags": [ "x402", "openapi", "interop", "directory" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260130040413/https://github.com/Merit-Systems/x402scan/blob/main/docs/DISCOVERY.md" }, { "id": "x402scan", "title": "x402scan: x402 Ecosystem Explorer", "publisher": "Merit Systems", "authors": [], "date_published": null, "url": "https://www.x402scan.com/", "type": "directory", "category": "payments", "status": "product_docs", "summary": "Explorer and registry for x402 that tracks servers, transactions, buyers, merchants and facilitators across chains. It publishes an OpenAPI spec, an RFC 9727 api-catalog and a health endpoint. Most read API calls are paid via x402.", "tags": [ "x402", "stablecoins", "directory", "market-data" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260812203604/https://www.x402scan.com/" }, { "id": "mpp-dev", "title": "MPP: Machine Payments Protocol", "publisher": "mpp.dev", "authors": [], "date_published": null, "url": "https://mpp.dev/", "type": "spec", "category": "payments", "status": "product_docs", "summary": "Documentation hub for the Machine Payments Protocol, which standardizes HTTP 402 challenges, credentials and receipts for machine payments across methods including stablecoins, cards and Lightning. It publishes llms.txt, per-page Markdown, an MCP server card and an Agent Skills index.", "tags": [ "m2m-payments", "stablecoins", "lightning", "interop" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261006012625/https://mpp.dev/" }, { "id": "mpp-discovery", "title": "Discovery (MPP)", "publisher": "mpp.dev", "authors": [], "date_published": null, "url": "https://mpp.dev/advanced/discovery", "type": "docs", "category": "payments", "status": "product_docs", "summary": "Explains how an MPP server advertises payment terms ahead of time in an OpenAPI 3.1 document, with paid operations annotated by x-payment-info, while the runtime 402 challenge remains authoritative.", "tags": [ "m2m-payments", "openapi", "interop" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261003141031/https://mpp.dev/advanced/discovery" }, { "id": "mpp-services-directory", "title": "MPP services", "publisher": "mpp.dev", "authors": [], "date_published": null, "url": "https://mpp.dev/services", "type": "directory", "category": "payments", "status": "product_docs", "summary": "Curated directory of APIs that accept MPP payments, also available as JSON at /api/services with per-endpoint payment intent, method, asset and amount.", "tags": [ "m2m-payments", "directory", "stablecoins" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260826050535/https://mpp.dev/services" }, { "id": "402index", "title": "402 Index", "publisher": "402 Index", "authors": [], "date_published": null, "url": "https://402index.io/", "type": "directory", "category": "payments", "status": "product_docs", "summary": "Protocol-agnostic directory of HTTP 402 paid APIs (L402, x402, MPP) with health probing, payment verification and semantic search. It exposes a JSON API, RSS, webhooks and an MCP server, and aggregates Bazaar, Satring, l402apps and MPP listings.", "tags": [ "l402", "x402", "directory", "lightning", "stablecoins" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260825161802/https://402index.io/" }, { "id": "402index-github", "title": "ryanthegentry/402index", "publisher": "GitHub (402 Index)", "authors": [], "date_published": null, "url": "https://github.com/ryanthegentry/402index", "type": "repo", "category": "payments", "status": "product_docs", "summary": "MIT-licensed source for 402 Index, including an npm MCP server package, self-serve registration through a probe that validates the 402 challenge, and YAML listings accepted by pull request.", "tags": [ "l402", "x402", "directory", "mcp" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": null }, { "id": "satring", "title": "satring: Curated Paid API Directory for AI Agents", "publisher": "satring", "authors": [], "date_published": null, "url": "https://satring.com/", "type": "directory", "category": "payments", "status": "product_docs", "summary": "Curated directory of paid APIs that accept L402, x402 (USDC on Base) or MPP. It has a free summary tier and paid bulk export, analytics and reputation, plus /.well-known/l402 and /.well-known/x402 payment descriptors and an agent.json.", "tags": [ "l402", "x402", "directory", "lightning" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260711060251/https://satring.com/" }, { "id": "x402-new", "title": "x402.new: The x402 Directory", "publisher": "x402.new", "authors": [], "date_published": null, "url": "https://x402.new/", "type": "directory", "category": "payments", "status": "product_docs", "summary": "Directory of x402-payable APIs rebuilt from the public x402 discovery network. Each service page lists price, networks, method, inputs, an example response and 30-day call statistics. It offers paid featured placement.", "tags": [ "x402", "stablecoins", "directory" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260403014505/https://x402.new/" }, { "id": "hal-service-directory", "title": "Hal Service Directory", "publisher": "Hal", "authors": [], "date_published": null, "url": "https://directory.halmarket.dev/", "type": "directory", "category": "payments", "status": "product_docs", "summary": "Marketplace directory of pay-per-call agent services that sellers price per call, paid over Lightning or USDC via x402. It publishes llms.txt and an OpenAPI description of the directory.", "tags": [ "lightning", "x402", "directory", "m2m-payments" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": null }, { "id": "ucp-dev", "title": "Universal Commerce Protocol (UCP)", "publisher": "Universal Commerce Protocol", "authors": [], "date_published": null, "url": "https://ucp.dev/", "type": "spec", "category": "payments", "status": "product_docs", "summary": "Site for the Universal Commerce Protocol, an open agentic-commerce standard.", "tags": [ "interop", "agents", "standards" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261016171038/https://ucp.dev/" }, { "id": "ucp-github", "title": "Universal-Commerce-Protocol/ucp", "publisher": "GitHub (Universal Commerce Protocol)", "authors": [], "date_published": null, "url": "https://github.com/universal-commerce-protocol/ucp", "type": "repo", "category": "payments", "status": "spec_released", "summary": "Specification and documentation repository for the Universal Commerce Protocol.", "tags": [ "interop", "standards" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260920171720/https://github.com/Universal-Commerce-Protocol/ucp" }, { "id": "circle-agent-stack", "title": "Agent stack", "publisher": "Circle", "authors": [], "date_published": null, "url": "https://developers.circle.com/agent-stack", "type": "docs", "category": "payments", "status": "product_docs", "summary": "Circle's Agent stack documentation says an AI agent can hold and transact USDC and other tokens, discover and pay for x402 services, and operate within compliance guardrails. The page lists Circle CLI, Agent Wallets with custom spending policies, Agent Nanopayments, an Agent Marketplace, and a hosted x402 facilitator.", "tags": [ "x402", "stablecoins", "agent-wallets", "tools" ], "verified_at": "2026-10-22", "last_checked": "2026-10-22", "http_status": 200, "archive_url": null }, { "id": "buy-services-your-agents-can-buy", "title": "Services your agents can buy", "publisher": "buy", "authors": [], "date_published": null, "url": "https://usebuy.ai", "type": "directory", "category": "payments", "status": "product_docs", "summary": "The buy site lists services an agent can pay for per request with one wallet on Celo, and says the catalogue held 782 tools when prices were read on 2026-10-13. The how-it-works section says the caller sets a spending cap per call.", "tags": [ "directory", "stablecoins", "tools", "agents" ], "verified_at": "2026-10-22", "last_checked": "2026-10-22", "http_status": 200, "archive_url": null }, { "id": "celo-x402-facilitator", "title": "x402 Facilitator — Celo", "publisher": "Celo Core Co.", "authors": [], "date_published": null, "url": "https://x402.celo.org", "type": "docs", "category": "payments", "status": "product_docs", "summary": "x402.celo.org is a hosted x402 facilitator for Celo. The static homepage names Celo Core Co. and does not list assets. Checked on 2026-10-31, https://x402.celo.org/skill.md and GET https://api.x402.celo.org/supported list the same 10 mainnet assets on eip155:42220. USDC, USDT, and USAT use assetTransferMethod eip3009. wARS, wBRL, wMXN, wCOP, wPEN, and wCLP use permit2. cNGN uses permit2. The skill says settlement gas is paid by the facilitator and that the facilitator sponsors the Permit2 allowance for the other Permit2 assets. It says cNGN is the exception: a first-time payer must send approve(Permit2, amount) and pays that gas.", "tags": [ "x402", "stablecoins", "tools" ], "verified_at": "2026-10-31", "last_checked": "2026-10-31", "http_status": 200, "archive_url": null }, { "id": "stripe-docs-mcp", "title": "Model Context Protocol (MCP)", "publisher": "Stripe Docs", "authors": [], "date_published": null, "url": "https://docs.stripe.com/mcp", "type": "docs", "category": "payments", "status": "product_docs", "summary": "Stripe documentation for its Model Context Protocol server, labeled public preview. The server URL is https://mcp.stripe.com. Clients authenticate with OAuth or with an agent API key passed as a bearer token in the Authorization header. A GET of https://mcp.stripe.com with no API key returned HTTP 401 on 2026-10-23. Treasury tools on the server are labeled public preview. Related library entry: stripe-treasury-for-agents.", "tags": [ "mcp", "agent-wallets", "tools" ], "verified_at": "2026-10-23", "featured": false, "last_checked": "2026-10-23", "http_status": 200, "archive_url": null }, { "id": "visa-trusted-agent-protocol-reference", "title": "Trusted Agent Protocol sample implementation", "publisher": "Visa", "authors": [], "date_published": null, "url": "https://github.com/visa/trusted-agent-protocol", "type": "repo", "category": "payments", "status": "product_docs", "summary": "Visa's GitHub repository for a Trusted Agent Protocol sample implementation. The repository includes the modules agent-registry, tap-agent, and merchant-backend. The README says an agent signature includes a timestamp, a session identifier, a key identifier, and an algorithm identifier, and that the signature is bound to the merchant domain and the operation. License: not open source. LICENSE.md requires the Visa Developer Center Terms of Use (https://developer.visa.com/terms), including the Visa Trusted Agent Protocol Product Terms. Related library entries: visa-developer-trusted-agent-protocol and visa-bill-billtrust-trusted-agent-b2b-pilot.", "tags": [ "card-networks", "identity", "security" ], "verified_at": "2026-10-23", "featured": false, "last_checked": "2026-10-23", "http_status": 200, "archive_url": null }, { "id": "stripe-docs-mpp-sessions", "title": "Accept streaming payments", "publisher": "Stripe Docs", "authors": [], "date_published": null, "url": "https://docs.stripe.com/payments/machine/mpp/sessions", "type": "docs", "category": "payments", "status": "product_docs", "summary": "Stripe documentation for MPP sessions. An agent deposits USDC into a session on Tempo. The server charges for each unit of work in increments as small as 0.000001 USDC and settles funds to the Stripe balance in increments of 0.01 USD or more. Any sub-cent remainder, such as when a client closes a session, is forfeited. Related library entries: stripe-docs-mpp, stripe-introducing-machine-payments-protocol, and stripe-docs-mcp.", "tags": [ "m2m-payments", "stablecoins" ], "verified_at": "2026-10-23", "featured": false, "last_checked": "2026-10-23", "http_status": 200, "archive_url": null }, { "id": "mcp-ruby-sdk-tier-1", "title": "The Official Ruby SDK for MCP Reaches Tier 1", "publisher": "Model Context Protocol Blog", "authors": [ "Koichi Ito" ], "date_published": "2026-10-30", "url": "https://blog.modelcontextprotocol.io/posts/ruby-sdk-tier-1/", "type": "announcement", "category": "agent-protocols", "status": "news", "summary": "MCP Blog post by Koichi Ito, dated 2026-10-30. The official Ruby SDK is now a Tier 1 SDK, and the post says it joins the TypeScript, Python, C#, Go, and Rust SDKs. Starting with version 1.2.0 of the mcp gem, the post says the SDK fully supports the 2026-07-28 MCP specification. It says the SDK passes 100% of the scored server and client conformance scenarios for both the 2025-11-25 and 2026-07-28 requirement sets, measured with the standard MCP conformance suite. The post does not use the word sixth. The post links the tiering system at https://modelcontextprotocol.io/community/sdk-tiers, the gem at https://rubygems.org/gems/mcp, and the v1.2.0 tag at https://github.com/modelcontextprotocol/ruby-sdk/releases/tag/v1.2.0.", "tags": [ "mcp", "sdk" ], "verified_at": "2026-11-04", "featured": false, "last_checked": "2026-11-04", "http_status": 200, "archive_url": null }, { "id": "mcp-sep-3392-extension-lifecycle", "title": "SEP-3392: Extension Lifecycle", "publisher": "GitHub (Model Context Protocol)", "authors": [ "Peter Alexander" ], "date_published": "2026-10-29", "url": "https://github.com/modelcontextprotocol/modelcontextprotocol/pull/3392", "type": "docs", "category": "agent-protocols", "status": "standard", "summary": "Process SEP. The merged document header status is Final. The pull request merged on 2026-10-29. An extension starts as Experimental, may advance to Beta, and then either becomes Stable as an extension or is promoted into the core specification. The stage is the directory specification/experimental, specification/beta, or specification/stable. The document says the repository name does not show the stage, and that an earlier draft used experimental-ext-, beta-ext-, and ext- prefixes. Its transition table, under the heading Stage at Final, classifies ext-apps and ext-auth as Stable, ext-skills, ext-tasks, and ext-server-card as Beta, and experimental-ext-interceptors, experimental-ext-variants, experimental-ext-triggers-events, and experimental-ext-tool-annotations as Experimental. It says Extension Maintainers move the specification into that directory and a Core Maintainer approves the move.", "tags": [ "mcp", "standards" ], "verified_at": "2026-10-31", "featured": false, "last_checked": "2026-10-31", "http_status": 200, "archive_url": null }, { "id": "mcp-sep-3398-release-cycle-updates", "title": "SEP-3398: Release Cycle Updates", "publisher": "GitHub (Model Context Protocol)", "authors": [ "Kurtis Van Gent" ], "date_published": "2026-10-27", "url": "https://github.com/modelcontextprotocol/modelcontextprotocol/pull/3398", "type": "docs", "category": "agent-protocols", "status": "product_docs", "summary": "Process SEP for the Model Context Protocol. The header status is Accepted. It was created 2026-09-17, accepted 2026-10-14, and the pull request merged on 2026-10-27. The author is Kurtis Van Gent. Specification releases occur every six months, generally on the last Tuesday of March and September. Release managers confirm the exact date in each cycle's published calendar. The SEP moves the release previously targeted for December 2026 to March 30, 2027, the last Tuesday of March, subject to confirmation in the transition calendar. Soft freeze is 2.5 months before release, the SDK beta is 1.5 months before release, and hard freeze is 1 month before release. The published release calendar defines the exact milestone dates. The SEP says it introduces no protocol messages, schema changes, version-negotiation changes, or new requirements for deployed clients and servers. The pull request's accepted label says an accepted SEP still requires final wording and a reference implementation.", "tags": [ "mcp", "standards" ], "verified_at": "2026-10-28", "featured": false, "last_checked": "2026-10-28", "http_status": 200, "archive_url": null }, { "id": "erc-tba-agent-income-statements", "title": "ERC-TBA: Agent Income Statements", "publisher": "Fellowship of Ethereum Magicians", "authors": [ "priors-agents" ], "date_published": "2026-10-22", "url": "https://ethereum-magicians.org/t/erc-tba-agent-income-statements/30047", "type": "spec", "category": "agent-protocols", "status": "individual_draft", "summary": "Draft profile of the ERC-8004 Reputation Registry, posted by priors-agents on 2026-10-22. It specifies chained, Merkle-rooted statements of what an agent's agentWallet received in one asset, under tag2 x402.statement, with windows cut at ERC-721 Transfer and MetadataSet(\"agentWallet\") logs so the figures can be rebuilt from token logs. The repository has a verifier, a reference writer, and a checker. The author says the reference implementation is not audited and must not be deployed without an external audit. The thread was still active on 2026-10-25. Repository: https://github.com/priors-agents/erc-agent-income-statements.", "tags": [ "identity", "x402" ], "verified_at": "2026-10-26", "featured": false, "last_checked": "2026-10-26", "http_status": 200, "archive_url": null }, { "id": "mcp-tasks-and-events-working-group", "title": "Tasks and Events Charter", "publisher": "Model Context Protocol", "authors": [], "date_published": "2026-10-16", "url": "https://modelcontextprotocol.io/community/working-groups/tasks-events", "type": "docs", "category": "agent-protocols", "status": "product_docs", "summary": "The Tasks and Events Working Group charter says the group continues Tasks, described as MCP's foundation for durable asynchronous execution, and will specify server-initiated notifications. Its changelog records a rename on 2026-10-16, and the resources section links SEP-2663: Tasks Extension.", "tags": [ "mcp", "standards", "agents" ], "verified_at": "2026-10-22", "last_checked": "2026-10-22", "http_status": 200, "archive_url": null }, { "id": "ietf-draft-prakash-aip-02", "title": "Agent Identity Protocol (draft-prakash-aip-02)", "publisher": "IETF", "authors": [ "S. Prakash" ], "date_published": "2026-10-10", "url": "https://datatracker.ietf.org/doc/html/draft-prakash-aip-02", "type": "spec", "category": "agent-protocols", "status": "individual_draft", "summary": "Individual Internet-Draft, not a standard. Published 2026-10-10, intended status Standards Track, expires 2027-04-13. It specifies a delegation chain so a relying party can check who granted authority and that no hop widened it. The encodings are a chain of JWTs or a Biscuit token. MCP carries the token in the X-AIP-Token header, A2A carries it in metadata.aip_token, and generic HTTP uses an Authorization header with the AIP scheme.", "tags": [ "mcp", "a2a", "http", "identity", "standards" ], "verified_at": "2026-10-22", "last_checked": "2026-10-22", "http_status": 200, "archive_url": null }, { "id": "mcp-sep-2127-server-cards", "title": "SEP-2127: MCP Server Cards - HTTP Server Discovery", "publisher": "GitHub (Model Context Protocol)", "authors": [], "date_published": "2026-10-06", "url": "https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2127", "type": "spec", "category": "agent-protocols", "status": "spec_released", "summary": "Merged MCP enhancement proposal for pre-connection discovery of remote MCP servers through Server Cards, advertised from a domain-level /.well-known/ai-catalog.json. It supersedes the earlier SEP-1649 approach. The server-card schema is still marked experimental.", "tags": [ "mcp", "interop", "standards" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261015061132/https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2127" }, { "id": "mcp-specification-2026-07-28", "title": "Specification - Model Context Protocol (Version 2026-07-28)", "publisher": "Model Context Protocol", "authors": [], "date_published": "2026-07-28", "url": "https://modelcontextprotocol.io/specification/2026-07-28", "type": "spec", "category": "agent-protocols", "status": "spec_released", "summary": "Latest dated version of the Model Context Protocol specification, covering architecture, base protocol, lifecycle, transports, authorization and client and server features. The version identifier is the date.", "tags": [ "mcp", "interop", "tools" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261020010758/https://modelcontextprotocol.io/specification/2026-07-28" }, { "id": "ietf-dns-aid", "title": "DNS for AI Discovery (draft-mozleywilliams-dnsop-dnsaid-02)", "publisher": "IETF Datatracker", "authors": [ "Jim Mozley", "Nic Williams", "Behcet Sarikaya", "Roland Schott", "Jeffrey Damick" ], "date_published": "2026-05-27", "url": "https://datatracker.ietf.org/doc/draft-mozleywilliams-dnsop-dnsaid/", "type": "spec", "category": "agent-protocols", "status": "individual_draft", "summary": "Internet-Draft for publishing AI agent endpoints and capability metadata in DNS using SVCB records and DNS-SD-style indexes, with DNSSEC/DANE for validation. Active individual draft, revision 02.", "tags": [ "interop", "identity", "standards" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260923065951/https://datatracker.ietf.org/doc/draft-mozleywilliams-dnsop-dnsaid/" }, { "id": "ap2-protocol-llms", "title": "AP2 documentation (llms.txt)", "publisher": "AP2", "authors": [], "date_published": "2026-04-28", "url": "https://ap2-protocol.org/llms.txt", "type": "docs", "category": "agent-protocols", "status": "product_docs", "summary": "Machine-readable index for the AP2 v0.2 documentation. It links Markdown pages for the specification, flows, Checkout Mandate, and Payment Mandate. The home page it links names the AP2 v0.2 release and the FIDO Alliance donation, and lists human-present and human-not-present samples for cards and x402. Related library entry: google-ap2-github (https://github.com/google-agentic-commerce/AP2).", "tags": [ "ap2", "standards" ], "verified_at": "2026-10-26", "featured": false, "last_checked": "2026-10-26", "http_status": 200, "archive_url": null }, { "id": "cloudflare-agent-readiness", "title": "Introducing the Agent Readiness score. Check to see if your site is agent-ready", "publisher": "Cloudflare Blog", "authors": [], "date_published": "2026-04-17", "url": "https://blog.cloudflare.com/agent-readiness", "type": "announcement", "category": "agent-protocols", "status": "news", "summary": "Cloudflare post introducing an Agent Readiness score and the isitagentready.com scanner, which checks emerging standards such as llms.txt, Markdown negotiation, Content Signals, RFC 9727 API catalogs, MCP Server Cards, A2A Agent Cards, Agent Skills and the x402/MPP commerce protocols.", "tags": [ "interop", "web-agents", "standards" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261006003600/https://blog.cloudflare.com/agent-readiness/" }, { "id": "mcp-specification-2025-06-18", "title": "Specification - Model Context Protocol (Version 2025-06-18)", "publisher": "Model Context Protocol", "authors": [], "date_published": "2025-06-18", "url": "https://modelcontextprotocol.io/specification/2025-06-18", "type": "spec", "category": "agent-protocols", "status": "spec_released", "summary": "Earlier dated revision of the MCP specification, covering authorization, transports, roots, sampling, elicitation, prompts and resources.", "tags": [ "mcp", "interop", "tools" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260924095810/https://modelcontextprotocol.io/specification/2025-06-18" }, { "id": "llms-txt", "title": "The /llms.txt file, v2", "publisher": "llmstxt.org", "authors": [ "Jeremy Howard" ], "date_published": "2024-09-03", "url": "https://llmstxt.org/", "type": "spec", "category": "agent-protocols", "status": "proposal", "summary": "Proposal to standardise an /llms.txt file that gives agents information about how to use a website. The page was last modified on 10 August 2026.", "tags": [ "llms-txt", "interop" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261016034533/https://llmstxt.org/" }, { "id": "openapi-3-1-0", "title": "OpenAPI Specification v3.1.0", "publisher": "OpenAPI Initiative", "authors": [], "date_published": "2021-02-15", "url": "https://spec.openapis.org/oas/v3.1.0.html", "type": "spec", "category": "agent-protocols", "status": "spec_released", "summary": "Standard, programming-language-agnostic interface description for HTTP APIs, widely used to describe tools and APIs for programmatic consumers.", "tags": [ "openapi", "interop" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261008125912/https://spec.openapis.org/oas/v3.1.0.html" }, { "id": "x402-scheme-exact-svm", "title": "Exact Payment Scheme for Solana Virtual Machine (SVM) (`exact`)", "publisher": "x402 Foundation (GitHub)", "authors": [], "date_published": null, "url": "https://github.com/x402-foundation/x402/blob/main/specs/schemes/exact/scheme_exact_svm.md", "type": "spec", "category": "agent-protocols", "status": "spec_released", "summary": "Specification for the x402 exact scheme on Solana, read from main on 2026-11-08. The file does not state a publication date. Its latest commit is 2026-11-06, pull request #3615. PaymentRequirements extra includes feePayer and may include a memo of at most 256 bytes, a recentBlockhash, a lastValidBlockHeight decimal string, and splits. The resource server sends the payload to the sponsor's /verify endpoint and, after success, to /settle. The sponsor then signs as feePayer and submits the transaction. Section 3.1 classifies top-level instructions by program ID and discriminator instead of absolute position. Lighthouse instructions whose first data byte is 2 through 17, program L2TExMFKdjpN9kozasaurPirfHy9P8sbXoAN1qA3S95, may appear anywhere. The allowlist table calls that program Phantom assertions. MemoryWrite, MemoryClose, empty data, and unknown variants must be rejected. A sponsor may set preflight and postflight instruction-tuple allowlists. Both default to empty. Pull request #3615 also edits the Go, Python, and TypeScript facilitator source on main. Those notes are still unreleased fragments under go/.changes/unreleased, python/x402/changelog.d, and typescript/.changeset. npm @x402/svm 2.30.0 was published 2026-11-04, and PyPI x402 2.27.0 was uploaded the same day. instruction_layout.py is absent from tag pypi-x402@v2.27.0. This card does not say a published npm or PyPI package accepts Phantom Lighthouse guards. Pull request #4171, merged 2026-11-06, changes docs/schemes/exact.mdx only.", "tags": [ "x402", "solana", "svm", "standards" ], "verified_at": "2026-11-08", "featured": false, "last_checked": "2026-11-08", "http_status": 200, "archive_url": null }, { "id": "x402-scheme-exact-lnbtc", "title": "x402 scheme: exact on Bitcoin Lightning (lnbtc)", "publisher": "x402 Foundation (GitHub)", "authors": [], "date_published": null, "url": "https://github.com/x402-foundation/x402/blob/main/specs/schemes/exact/scheme_exact_lnbtc.md", "type": "spec", "category": "agent-protocols", "status": "spec_released", "summary": "Specification for the x402 exact scheme on Lightning. It says the facilitator checks SHA-256(preimage) equals payment_hash and that the invoice signing key matches payTo. It supports only the bolt11 asset transfer method and the upfront flow. Mainnet MUST use lnbtc:000000000019d6689c085ae165831e93 and BOLT11 currency bc. Testnet MUST use lnbtc:000000000933ea01ad0ee984209779ba and currency tb. amount MUST be a decimal string of a positive integer number of millisatoshis, and bare numbers MUST NOT default to satoshis. The file does not state a publication date.", "tags": [ "x402", "lightning", "standards" ], "verified_at": "2026-11-03", "featured": true, "last_checked": "2026-11-03", "http_status": 200, "archive_url": null }, { "id": "x402-scheme-batch-settlement", "title": "x402 scheme: batch-settlement", "publisher": "x402 Foundation (GitHub)", "authors": [], "date_published": null, "url": "https://github.com/x402-foundation/x402/blob/main/specs/schemes/batch-settlement/scheme_batch_settlement.md", "type": "spec", "category": "agent-protocols", "status": "spec_released", "summary": "Specification for the x402 batch-settlement scheme. The client provides a cryptographic payment commitment at request time, access is granted immediately, and value moves later through the network binding. The client commits up to PaymentRequirements.amount and the server may charge less. For exact and upto, the settlement result contains an onchain transaction hash. For batch-settlement it contains a commitment identifier. Bindings in the same directory are scheme_batch_settlement_evm.md, scheme_batch_settlement_svm.md, and scheme_batch_settlement_cloudflare.md. The file does not state a publication date.", "tags": [ "x402", "standards" ], "verified_at": "2026-11-03", "featured": false, "last_checked": "2026-11-03", "http_status": 200, "archive_url": null }, { "id": "a2a-protocol-specification", "title": "Agent2Agent (A2A) Protocol Specification", "publisher": "A2A Protocol", "authors": [], "date_published": null, "url": "https://a2a-protocol.org/latest/specification/", "type": "spec", "category": "agent-protocols", "status": "spec_released", "summary": "Official A2A specification (latest released version 1.0.0), an open standard for communication and interoperability between independent, potentially opaque AI agent systems built on different frameworks or by different vendors.", "tags": [ "a2a", "interop" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261009134313/https://a2a-protocol.org/latest/specification/" }, { "id": "rfc-9421-http-message-signatures", "title": "RFC 9421: HTTP Message Signatures", "publisher": "IETF", "authors": [ "A. Backman", "J. Richer", "M. Sporny" ], "date_published": null, "url": "https://datatracker.ietf.org/doc/html/rfc9421", "type": "spec", "category": "agent-protocols", "status": "standard", "summary": "IETF Proposed Standard defining how to create, encode and verify digital signatures over components of HTTP messages. It can serve as a building block for authenticating automated clients. Published February 2024 (no day given, so date_published is null).", "tags": [ "identity", "security", "http" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261006063814/https://datatracker.ietf.org/doc/html/rfc9421" }, { "id": "mcp-registry", "title": "Official MCP Registry", "publisher": "Model Context Protocol", "authors": [], "date_published": null, "url": "https://registry.modelcontextprotocol.io/", "type": "directory", "category": "agent-protocols", "status": "product_docs", "summary": "Official registry of MCP servers with an unauthenticated read API (GET /v0.1/servers) supporting cursor pagination, name search and updated_since for incremental sync by downstream aggregators.", "tags": [ "mcp", "directory", "interop" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261009210501/https://registry.modelcontextprotocol.io/" }, { "id": "mcp-registry-github", "title": "modelcontextprotocol/registry", "publisher": "GitHub (Model Context Protocol)", "authors": [], "date_published": null, "url": "https://github.com/modelcontextprotocol/registry", "type": "repo", "category": "agent-protocols", "status": "product_docs", "summary": "Source, OpenAPI reference and server.json schema for the community-driven MCP Registry, including the publishing flow and namespace verification.", "tags": [ "mcp", "directory", "tools" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260910002125/https://github.com/modelcontextprotocol/registry" }, { "id": "mcp-ext-server-card", "title": "modelcontextprotocol/ext-server-card", "publisher": "GitHub (Model Context Protocol)", "authors": [], "date_published": null, "url": "https://github.com/modelcontextprotocol/experimental-ext-server-card", "type": "repo", "category": "agent-protocols", "status": "product_docs", "summary": "Experimental extension that holds the TypeScript and JSON Schema source for MCP Server Cards. A card describes a remote server's identity and transport endpoints; tools are listed at runtime, not on the card.", "tags": [ "mcp", "interop" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": null }, { "id": "ai-catalog", "title": "AI Catalog", "publisher": "AI Catalog (Agent-Card)", "authors": [], "date_published": null, "url": "https://ai-catalog.io/", "type": "spec", "category": "agent-protocols", "status": "proposal", "summary": "Cross-protocol draft standard for a typed, nestable JSON catalog that lists heterogeneous AI artifacts (MCP servers, A2A agents, datasets and more) for discovery. It is developed by members of several AI protocol communities.", "tags": [ "interop", "mcp", "a2a", "standards" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260919213800/https://ai-catalog.io/" }, { "id": "a2a-agent-discovery", "title": "Agent Discovery (A2A Protocol)", "publisher": "A2A Protocol", "authors": [], "date_published": null, "url": "https://a2a-protocol.org/latest/topics/agent-discovery/", "type": "docs", "category": "agent-protocols", "status": "product_docs", "summary": "A2A guidance on finding agents through a well-known Agent Card URL (/.well-known/agent-card.json), curated registries, or direct configuration. It notes that the spec does not prescribe a registry API.", "tags": [ "a2a", "interop" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261007210746/https://a2a-protocol.org/latest/topics/agent-discovery/" }, { "id": "a2a-registry-org", "title": "Global A2A Registry", "publisher": "A2A Registry", "authors": [], "date_published": null, "url": "https://www.a2a-registry.org/", "type": "directory", "category": "agent-protocols", "status": "product_docs", "summary": "Free public registry of A2A agents that is itself discoverable as an A2A agent. It offers natural-language agent search and DNS- and GitHub-based verification, and its agent card includes an extension that declares a payment model.", "tags": [ "a2a", "directory", "identity" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261014041221/https://www.a2a-registry.org/" }, { "id": "wildcard-agents-json", "title": "wild-card-ai/agents-json", "publisher": "GitHub (Wildcard)", "authors": [], "date_published": null, "url": "https://github.com/wild-card-ai/agents-json", "type": "repo", "category": "agent-protocols", "status": "product_docs", "summary": "agents.json, an OpenAPI-based contract published at /.well-known/agents.json that describes multi-step API 'flows' for agents, linking the outputs of one operation to the inputs of the next.", "tags": [ "interop", "openapi", "tools" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260616065942/https://github.com/wild-card-ai/agents-json" }, { "id": "agentskills-io", "title": "Agent Skills", "publisher": "Agentic AI Foundation (AAIF, Linux Foundation)", "authors": [], "date_published": null, "url": "https://agentskills.io/", "type": "spec", "category": "agent-protocols", "status": "spec_released", "summary": "Open format for packaging agent capabilities as SKILL.md files with YAML frontmatter, plus a discovery index schema used by sites at /.well-known/agent-skills/index.json (for example docs.x402.org and mpp.dev). Anthropic donated the Agent Skills standard (SKILL.md folders) to the Agentic AI Foundation under the Linux Foundation, including the name, the GitHub org, and the agentskills.io domain. Source: https://www.anthropic.com/news/donating-agent-skills-to-the-agentic-ai-foundation.", "tags": [ "interop", "tools", "agents" ], "verified_at": "2026-10-24", "last_checked": "2026-10-24", "http_status": 200, "archive_url": null }, { "id": "agents-md", "title": "AGENTS.md", "publisher": "agents.md", "authors": [], "date_published": null, "url": "https://agents.md/", "type": "spec", "category": "agent-protocols", "status": "spec_released", "summary": "Simple open format for a README-style instruction file aimed at coding agents. mpp.dev publishes one and links it from its API catalog.", "tags": [ "interop", "agents" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261019005759/https://agents.md/" }, { "id": "rfc-9727-api-catalog", "title": "RFC 9727: api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs", "publisher": "IETF", "authors": [ "K. Smith" ], "date_published": null, "url": "https://www.rfc-editor.org/rfc/rfc9727", "type": "spec", "category": "agent-protocols", "status": "standard", "summary": "Standards-track RFC (June 2025) defining /.well-known/api-catalog and the api-catalog link relation, which return a linkset of a publisher's APIs with links to their descriptions, docs and status endpoints.", "tags": [ "openapi", "interop", "standards", "http" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260427180630/https://www.rfc-editor.org/rfc/rfc9727" }, { "id": "rfc-9728-oauth-protected-resource-metadata", "title": "RFC 9728: OAuth 2.0 Protected Resource Metadata", "publisher": "IETF", "authors": [ "M.B. Jones", "P. Hunt", "A. Parecki" ], "date_published": null, "url": "https://www.rfc-editor.org/rfc/rfc9728", "type": "spec", "category": "agent-protocols", "status": "standard", "summary": "Standards-track RFC (April 2025) defining metadata that a protected resource publishes so clients can learn how to obtain tokens for it. Remote MCP authorization relies on it.", "tags": [ "identity", "security", "standards", "mcp" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20260427180635/https://www.rfc-editor.org/rfc/rfc9728" }, { "id": "content-signals", "title": "Content Signals", "publisher": "contentsignals.org", "authors": [], "date_published": null, "url": "https://contentsignals.org/", "type": "spec", "category": "agent-protocols", "status": "spec_released", "summary": "robots.txt extension (Content-Signal: search=, ai-input=, ai-train=) that declares how crawled content may be used, settable per user-agent. mpp.dev, x402scan and x402.org use it.", "tags": [ "web-agents", "interop", "regulation" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261014220907/https://contentsignals.org/" }, { "id": "webmcp-github", "title": "webmachinelearning/webmcp", "publisher": "GitHub (W3C Web Machine Learning CG)", "authors": [], "date_published": null, "url": "https://github.com/webmachinelearning/webmcp", "type": "repo", "category": "agent-protocols", "status": "product_docs", "summary": "Community Group proposal that lets a web page register tools for in-browser agents (document.modelContext.registerTool with a JSON Schema input). It is a CG draft, not a W3C standard.", "tags": [ "mcp", "web-agents", "tools" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261007193802/https://github.com/webmachinelearning/webmcp" }, { "id": "glama-mcp-servers", "title": "Glama MCP server directory", "publisher": "Glama", "authors": [], "date_published": null, "url": "https://glama.ai/mcp/servers", "type": "directory", "category": "agent-protocols", "status": "product_docs", "summary": "Large MCP server and remote connector directory, described as a superset of the official MCP Registry. Each server is scanned and scored, and the directory has a public REST API with OpenAPI and an RFC 9727 api-catalog.", "tags": [ "mcp", "directory", "security" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261010122735/https://glama.ai/mcp/servers" }, { "id": "proof-x401", "title": "x401 — Identity protocol for agentic commerce", "publisher": "Proof", "authors": [], "date_published": null, "url": "https://proof.com/x401", "type": "spec", "category": "agent-protocols", "status": "proposal", "summary": "Proof's x401 page describes an identity protocol for agentic commerce, labeled v0.1.0 and in active development. A service returns HTTP 401 with a base64url JSON PROOF-REQUIRED header that names an OpenID4VP presentation of a jwt_vc_json credential; the page also names PROOF-PRESENTATION and PROOF-RESPONSE.", "tags": [ "identity", "standards", "http", "agents" ], "verified_at": "2026-10-22", "last_checked": "2026-10-22", "http_status": 200, "archive_url": null }, { "id": "iso-21423-2026-industrial-mobile-robots-interoperability", "title": "ISO 21423:2026 Robotics — Industrial mobile robots — Communications and interoperability", "publisher": "ISO/TC 299", "authors": [], "date_published": "2026-10-14", "url": "https://www.iso.org/standard/86749.html", "type": "spec", "category": "robotics-autonomy", "status": "standard", "summary": "International Standard (edition 1) that specifies communication requirements between industrial mobile robots, their fleet managers and other equipment and applications in a shared industrial environment, such as ERP tools, lifts, alarms and automated doors. Safety and navigation requirements are out of scope, as are consumer, medical, military and public-road uses.", "tags": [ "robotics", "standards", "interop", "industrial-iot" ], "verified_at": "2026-10-21", "featured": false, "last_checked": "2026-10-21", "http_status": 200, "archive_url": null }, { "id": "ul-4600-evaluation-autonomous-products", "title": "UL 4600: Standard for Evaluation of Autonomous Products", "publisher": "UL Standards & Engagement", "authors": [], "date_published": "2023-03-17", "url": "https://www.shopulstandards.com/ProductDetail.aspx?productId=UL4600", "type": "spec", "category": "robotics-autonomy", "status": "standard", "summary": "ANSI/UL 4600 (3rd edition) covers safety principles, risk mitigation, tools, techniques and lifecycle processes for building and evaluating a safety case for vehicles that operate autonomously without human supervision.", "tags": [ "autonomy-safety", "standards" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261008112248/https://www.shopulstandards.com/ProductDetail.aspx?productid=UL4600" }, { "id": "iso-iec-22989-ai-concepts-terminology", "title": "ISO/IEC 22989:2022 Information technology — Artificial intelligence — Artificial intelligence concepts and terminology", "publisher": "ISO/IEC JTC 1/SC 42", "authors": [], "date_published": "2022-07-19", "url": "https://www.iso.org/standard/74296.html", "type": "spec", "category": "robotics-autonomy", "status": "standard", "summary": "International Standard that establishes AI terminology and describes AI concepts for use in developing other standards and in communication among stakeholders.", "tags": [ "ai-standards", "standards" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 403, "archive_url": "http://web.archive.org/web/20261017045149/https://www.iso.org/standard/74296.html" }, { "id": "ros2-github", "title": "ros2/ros2", "publisher": "GitHub (ROS 2)", "authors": [], "date_published": null, "url": "https://github.com/ros2/ros2", "type": "repo", "category": "robotics-autonomy", "status": "product_docs", "summary": "Main repository of ROS 2, the Robot Operating System, described as a meta operating system for robots.", "tags": [ "ros2", "robotics" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261014210520/https://github.com/ros2/ros2" }, { "id": "w3c-wot-architecture-1-1", "title": "Web of Things (WoT) Architecture 1.1", "publisher": "W3C", "authors": [], "date_published": "2023-12-05", "url": "https://www.w3.org/TR/wot-architecture11/", "type": "spec", "category": "iot", "status": "standard", "summary": "W3C Recommendation defining the abstract architecture of the Web of Things for interoperability across IoT platforms and application domains.", "tags": [ "wot", "interop", "standards" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261016075929/https://www.w3.org/TR/wot-architecture11/" }, { "id": "mqtt-v5-0", "title": "MQTT Version 5.0", "publisher": "OASIS", "authors": [], "date_published": "2019-03-07", "url": "https://docs.oasis-open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html", "type": "spec", "category": "iot", "status": "standard", "summary": "OASIS Standard for MQTT v5.0, a lightweight publish/subscribe messaging protocol for IoT and machine-to-machine communication.", "tags": [ "mqtt", "m2m", "standards" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261016073950/https://docs.oasis-open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html" }, { "id": "csa-matter", "title": "Matter", "publisher": "Connectivity Standards Alliance", "authors": [], "date_published": null, "url": "https://csa-iot.org/all-solutions/matter/", "type": "spec", "category": "iot", "status": "standard", "summary": "Connectivity Standards Alliance page for Matter, an industry-unifying standard for reliable, secure, interoperable connectivity between smart home devices, with access to the specification and certification.", "tags": [ "matter", "standards", "interop" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261014120214/https://csa-iot.org/all-solutions/matter/" }, { "id": "opc-ua", "title": "OPC Unified Architecture (OPC UA)", "publisher": "OPC Foundation", "authors": [], "date_published": null, "url": "https://opcfoundation.org/about/opc-technologies/opc-ua/", "type": "spec", "category": "iot", "status": "standard", "summary": "OPC Foundation landing page for OPC Unified Architecture. It describes features such as server discovery, a hierarchical address space, permission-based read/write and subscriptions, and links companion specifications for industry domains.", "tags": [ "opc-ua", "industrial-iot", "standards" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261015163046/https://opcfoundation.org/about/opc-technologies/opc-ua/" }, { "id": "arxiv-authorizationbench-agent-authorization-alignment", "title": "Act on Your Behalf, Beyond Your Authorization: Benchmarking LLM Agent Authorization Alignment", "publisher": "arXiv", "authors": [ "Zhiping Zhang", "Franklin Mingzhe Li", "Zihao Huang", "Tianshi Li" ], "date_published": "2026-10-20", "url": "https://arxiv.org/abs/2610.27548", "type": "research-paper", "category": "datasets-benchmarks", "status": "research", "summary": "The paper introduces AuthorizationBench, 286 executable tasks across ten domains, built from documented real-world cases, that test whether agents stay within the authorization a user granted. Across 6,864 trajectories from 24 model, reasoning-effort and harness configurations, agents acted outside their authorization in 19.2% of runs. Higher reasoning effort left the aggregate rate nearly unchanged.", "tags": [ "benchmark", "security", "research" ], "verified_at": "2026-10-21", "featured": false, "last_checked": "2026-10-21", "http_status": 200, "archive_url": null }, { "id": "arxiv-2610-17378-merchant-side-readiness-benchmark", "title": "Get In, Decide, Prove: A Merchant-Side Readiness Benchmark for Agentic Commerce", "publisher": "arXiv", "authors": [], "date_published": "2026-10-12", "url": "https://arxiv.org/abs/2610.17378", "type": "research-paper", "category": "datasets-benchmarks", "status": "research", "summary": "A benchmark that checks whether merchant sites let agents in, publish terms precise enough to decide a purchase (total cost, refund terms, service date, variant) and leave evidence of what was agreed. In a census of 555 merchant sites, the home page was unreadable to both declared bot and headless-browser profiles at 105 sites (18.9%). The all-in total was decidable at only 18 of 330 merchants assessed.", "tags": [ "benchmark", "agentic-commerce", "merchant-readiness", "bot-access" ], "verified_at": "2026-10-24", "featured": false, "last_checked": "2026-10-24", "http_status": 200, "archive_url": null }, { "id": "tau-bench", "title": "τ-bench: A Benchmark for Tool-Agent-User Interaction in Real-World Domains", "publisher": "arXiv", "authors": [ "Shunyu Yao", "Noah Shinn", "Pedram Razavi", "Karthik Narasimhan" ], "date_published": "2024-06-17", "url": "https://arxiv.org/abs/2406.12045", "type": "research-paper", "category": "datasets-benchmarks", "status": "research", "summary": "Benchmark of dynamic conversations between a language-model-simulated user and an agent equipped with domain-specific API tools and policy guidelines. Success is scored by comparing the final database state with an annotated goal state, and the paper introduces the pass^k reliability metric.", "tags": [ "benchmark", "tools", "research" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261015183045/https://arxiv.org/abs/2406.12045" }, { "id": "gaia-benchmark", "title": "GAIA: a benchmark for General AI Assistants", "publisher": "arXiv", "authors": [ "Grégoire Mialon", "Clémentine Fourrier", "Craig Swift", "Thomas Wolf", "Yann LeCun", "Thomas Scialom" ], "date_published": "2023-11-21", "url": "https://arxiv.org/abs/2311.12983", "type": "research-paper", "category": "datasets-benchmarks", "status": "research", "summary": "Benchmark of real-world questions for general AI assistants that require reasoning, multimodality, web browsing and tool use.", "tags": [ "benchmark", "research" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261011183417/https://arxiv.org/abs/2311.12983" }, { "id": "swe-bench-paper", "title": "SWE-bench: Can Language Models Resolve Real-World GitHub Issues?", "publisher": "arXiv", "authors": [ "Carlos E. Jimenez", "John Yang", "Alexander Wettig", "Shunyu Yao", "Kexin Pei", "Ofir Press", "Karthik Narasimhan" ], "date_published": "2023-10-10", "url": "https://arxiv.org/abs/2310.06770", "type": "research-paper", "category": "datasets-benchmarks", "status": "research", "summary": "Evaluation framework of 2,294 software engineering problems drawn from real GitHub issues and pull requests across 12 popular Python repositories.", "tags": [ "benchmark", "research" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261011232036/https://arxiv.org/abs/2310.06770" }, { "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" }, { "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/" }, { "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/" }, { "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 }, { "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 }, { "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 }, { "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 }, { "id": "arxiv-approve-what-exactly-agent-step-up-authorization", "title": "Approve What, Exactly? Effect Binding and Trusted Rendering for Agent Step-Up Authorization", "publisher": "arXiv", "authors": [ "Sai Varun Kodathala", "Prashanth Pollishetty", "Jaylen Cargill" ], "date_published": "2026-10-15", "url": "https://arxiv.org/abs/2610.21063", "type": "research-paper", "category": "safety-security", "status": "research", "summary": "The paper defines twelve attacks on the human-approval path of agent actions (such as decoy recipients, amount cancellation and threshold splitting) and runs them against AP2, Microsoft's action-bound approval design and MCP elicitation. An audit of ten agent runtimes finds no third-party verifiable approval record. The authors propose ASU, a gateway that renders the approval card from a canonical effect descriptor and has a user passkey sign its digest, and they verify it formally with Tamarin.", "tags": [ "security", "ap2", "mcp", "identity", "research" ], "verified_at": "2026-10-21", "featured": false, "last_checked": "2026-10-21", "http_status": 200, "archive_url": null }, { "id": "ietf-webbotauth-httpsig-protocol", "title": "HTTP Message Signatures for automated traffic (draft-ietf-webbotauth-httpsig-protocol-00)", "publisher": "IETF Datatracker", "authors": [ "Thibault Meunier", "Sandor Major" ], "date_published": "2026-09-01", "url": "https://datatracker.ietf.org/doc/draft-ietf-webbotauth-httpsig-protocol/", "type": "spec", "category": "safety-security", "status": "working_group_draft", "summary": "IETF working-group draft (Web Bot Auth) under which bots and agents identify themselves by signing requests with RFC 9421 HTTP Message Signatures, with keys discoverable from a published key directory. It replaces the earlier individual architecture draft.", "tags": [ "identity", "security", "http", "web-agents" ], "verified_at": "2026-10-20", "last_checked": "2026-10-20", "http_status": 200, "archive_url": "http://web.archive.org/web/20261004055551/https://datatracker.ietf.org/doc/draft-ietf-webbotauth-httpsig-protocol/" }, { "id": "arxiv-formal-analysis-agent-payment-protocols", "title": "A Formal Analysis of Agent Payment Protocols", "publisher": "arXiv", "authors": [ "Ke Jiang", "Mohan Yu", "Yuan Chang", "Mohit Kumar Jangid", "Jianyu Niu", "Cong Wang", "Yinqian Zhang" ], "date_published": "2026-08-30", "url": "https://arxiv.org/abs/2609.00060", "type": "research-paper", "category": "safety-security", "status": "research", "summary": "Paper published on arXiv on 2026-08-30 as 2609.00060v1. It formalizes x402, MPP, ACP, and AP2 in Tamarin. The abstract reports 18 shared security principles and 40 previously undocumented formal-consistency findings, across 86 verification cases.", "tags": [ "x402", "security", "research" ], "verified_at": "2026-10-22", "last_checked": "2026-10-22", "http_status": 200, "archive_url": null }, { "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/" }, { "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" }, { "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/" }, { "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 }, { "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 }, { "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 }, { "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" } ] }