{ "schema_version": "1", "generated_at": "2026-11-06T00:00:00Z", "disclaimer": { "text": "Not investment advice.", "url": "https://agentpaywire.com/disclaimer.json" }, "description": "Checked protocol facts. Bitcoin and Lightning protocols are first. Each fact has a source URL and a verified_at date. Null means the cited pages do not state that field.", "markdown_url": "https://agentpaywire.com/api/protocol-facts.md", "count": 11, "protocols": [ { "id": "l402", "name": "L402", "featured": true, "spec_url": { "value": "https://docs.lightning.engineering/the-lightning-network/l402/protocol-specification", "source": "https://docs.lightning.engineering/the-lightning-network/l402/protocol-specification", "verified_at": "2026-10-20" }, "http_status_codes": { "value": [ 402 ], "source": "https://docs.lightning.engineering/the-lightning-network/l402/protocol-specification", "verified_at": "2026-10-20" }, "http_headers": { "value": [ { "name": "WWW-Authenticate", "direction": "server to client", "role": "Challenge using the L402 scheme, with a base64 macaroon and a Lightning invoice." }, { "name": "Authorization", "direction": "client to server", "role": "L402 credential: base64 macaroon, a colon, then the hex-encoded invoice preimage. Multiple macaroons are comma-separated before the colon." } ], "source": "https://docs.lightning.engineering/the-lightning-network/l402/protocol-specification", "verified_at": "2026-10-20" }, "payment_rail": { "value": "Lightning", "source": "https://docs.lightning.engineering/the-lightning-network/l402/protocol-specification", "verified_at": "2026-10-20" }, "networks": { "value": [ { "name": "Lightning", "caip2": null, "asset": "bitcoin", "contract": null } ], "source": "https://docs.lightning.engineering/the-lightning-network/l402/protocol-specification", "verified_at": "2026-10-20" }, "facilitators": null, "client_libraries": { "value": [ { "name": "lightninglabs/lnget", "url": "https://github.com/lightninglabs/lnget" }, { "name": "lightninglabs/L402sdk 0.2.0. From this version, automatic payments require a backend that enforces a fee limit before submission. A zero fee limit allows only zero-fee routes.", "url": "https://github.com/lightninglabs/L402sdk/blob/main/CHANGELOG.md" } ], "source": "https://github.com/lightninglabs/L402sdk/blob/main/CHANGELOG.md", "verified_at": "2026-11-04" }, "pay_flow": { "value": [ "Request the resource.", "Read the HTTP 402 challenge: WWW-Authenticate carries an L402 macaroon and a Lightning invoice.", "Pay the invoice and take the preimage.", "Retry with Authorization: L402 :." ], "source": "https://docs.lightning.engineering/the-lightning-network/l402/protocol-specification", "verified_at": "2026-10-20" }, "notes": { "value": "The same credential is reused until the server revokes it and issues a new 402. The gRPC binding uses HTTP 200 with Grpc-Status 402 and puts the macaroon and invoice in grpc-status-details-bin. The HTTP Authorization header is the same.", "source": "https://docs.lightning.engineering/the-lightning-network/l402/protocol-specification", "verified_at": "2026-10-20" }, "implementation": { "value": "Aperture v0.6.0, published 2026-11-05 and not a prerelease, says a service with auth: l402+mpp answers an unpaid request with one 402 that carries both an L402 and a Payment challenge, and accepts either. MPP charges and sessions stay opt-in (enablempp, enablesessions). enablempp is refused at startup with the etcd backend; sqlite or postgres is required. A static price of 0 means the default price of 1 sat, not free.", "source": "https://github.com/lightninglabs/aperture/releases/tag/v0.6.0", "verified_at": "2026-11-05" }, "example": { "value": "GET https://api.agentpaywire.com/v1/search?q=bitcoin with no Authorization header returns HTTP 402 and a BOLT11 invoice for 100 sats. Pay the invoice, then retry with Authorization: L402 :. sha256 of that preimage matches the payment hash. One payment grants 100 requests for 30 days. The same credit price covers GET https://api.agentpaywire.com/v1/updates, GET https://api.agentpaywire.com/v1/digest, and GET https://api.agentpaywire.com/v1/changes. Discovery: https://agentpaywire.com/.well-known/l402. The files on https://agentpaywire.com stay free.", "source": "https://agentpaywire.com/.well-known/l402", "verified_at": "2026-10-20" } }, { "id": "bolt12", "name": "BOLT 12", "featured": true, "spec_url": { "value": "https://github.com/lightning/bolts/blob/master/12-offer-encoding.md", "source": "https://github.com/lightning/bolts/blob/master/12-offer-encoding.md", "verified_at": "2026-10-20" }, "http_status_codes": null, "http_headers": null, "payment_rail": { "value": "Lightning", "source": "https://github.com/lightning/bolts/blob/master/12-offer-encoding.md", "verified_at": "2026-10-20" }, "networks": { "value": [ { "name": "Lightning", "caip2": null, "asset": "bitcoin", "contract": null } ], "source": "https://github.com/lightning/bolts/blob/master/12-offer-encoding.md", "verified_at": "2026-10-20" }, "facilitators": null, "client_libraries": null, "pay_flow": { "value": [ "The receiver publishes an offer. The human-readable prefix is lno.", "The payer sends an invoice request over Lightning. The human-readable prefix is lnr. The request repeats the offer fields.", "The receiver replies with an invoice.", "The payer pays that invoice." ], "source": "https://github.com/lightning/bolts/blob/master/12-offer-encoding.md", "verified_at": "2026-10-20" }, "notes": { "value": "Offers, invoice requests, and invoices are TLV messages. The ASCII form is a human-readable prefix, the character 1, then a bech32-style data string. There is no checksum. Writers use all lowercase or all uppercase, and should use uppercase in QR codes. offer_amount may be in another currency; the issuer converts it to millisatoshis on the invoice.", "source": "https://github.com/lightning/bolts/blob/master/12-offer-encoding.md", "verified_at": "2026-10-20" } }, { "id": "bip21", "name": "BIP 21", "featured": true, "spec_url": { "value": "https://github.com/bitcoin/bips/blob/master/bip-0021.mediawiki", "source": "https://github.com/bitcoin/bips/blob/master/bip-0021.mediawiki", "verified_at": "2026-10-20" }, "http_status_codes": null, "http_headers": null, "payment_rail": { "value": "Bitcoin on-chain", "source": "https://github.com/bitcoin/bips/blob/master/bip-0021.mediawiki", "verified_at": "2026-10-20" }, "networks": { "value": [ { "name": "Bitcoin", "caip2": null, "asset": "BTC", "contract": null } ], "source": "https://github.com/bitcoin/bips/blob/master/bip-0021.mediawiki", "verified_at": "2026-10-20" }, "facilitators": null, "client_libraries": { "value": [ { "name": "Bitcoin-Qt", "url": null } ], "source": "https://github.com/bitcoin/bips/blob/master/bip-0021.mediawiki", "verified_at": "2026-10-20" }, "pay_flow": { "value": [ "Read a bitcoin: URI. The scheme is case-insensitive. The path is a bitcoin address.", "Read optional query keys: amount in decimal BTC, label, and message.", "The client must not pay the URI without user authorization.", "Treat any req- parameter the client does not implement as making the whole URI invalid. Other unknown parameters can be ignored." ], "source": "https://github.com/bitcoin/bips/blob/master/bip-0021.mediawiki", "verified_at": "2026-10-20" }, "notes": { "value": "The BIP text says it is superseded by BIP 321. Amounts use a period as the decimal separator and must not contain commas.", "source": "https://github.com/bitcoin/bips/blob/master/bip-0021.mediawiki", "verified_at": "2026-10-20" } }, { "id": "nwc", "name": "NWC (NIP-47)", "featured": true, "spec_url": { "value": "https://github.com/nostr-protocol/nips/blob/master/47.md", "source": "https://github.com/nostr-protocol/nips/blob/master/47.md", "verified_at": "2026-10-20" }, "http_status_codes": null, "http_headers": null, "payment_rail": { "value": "Lightning", "source": "https://github.com/nostr-protocol/nips/blob/master/47.md", "verified_at": "2026-10-20" }, "networks": { "value": [ { "name": "Lightning via a NIP-47 wallet service", "caip2": null, "asset": "bitcoin", "contract": null } ], "source": "https://github.com/nostr-protocol/nips/blob/master/47.md", "verified_at": "2026-10-20" }, "facilitators": null, "client_libraries": null, "pay_flow": { "value": [ "The wallet service gives the user a nostr+walletconnect:// URI with its pubkey, one or more relay URLs, and a client secret.", "The client reads the info event (kind 13194) for supported methods.", "To pay, the client encrypts a pay_invoice request and publishes kind 23194 to the relay.", "The wallet service pays the BOLT 11 invoice and returns kind 23195 with the preimage, or an error." ], "source": "https://github.com/nostr-protocol/nips/blob/master/47.md", "verified_at": "2026-10-20" }, "notes": { "value": "pay_invoice takes a BOLT 11 invoice. amount, when set, is millisatoshis. make_invoice amount is also millisatoshis. get_info reports network as mainnet, testnet, signet, or regtest. NIP-44 is the preferred encryption. Missing the encryption tag means NIP-04.", "source": "https://github.com/nostr-protocol/nips/blob/master/47.md", "verified_at": "2026-10-20" } }, { "id": "x402", "name": "x402", "featured": false, "spec_url": { "value": "https://docs.x402.org/core-concepts/http-402", "source": "https://docs.x402.org/core-concepts/http-402", "verified_at": "2026-10-20" }, "http_status_codes": { "value": [ 402 ], "source": "https://docs.x402.org/core-concepts/http-402", "verified_at": "2026-10-20" }, "http_headers": { "value": [ { "name": "PAYMENT-REQUIRED", "direction": "server to client", "role": "Base64-encoded PaymentRequired object, sent with HTTP 402. V2." }, { "name": "PAYMENT-SIGNATURE", "direction": "client to server", "role": "Base64-encoded PaymentPayload sent when retrying after HTTP 402." }, { "name": "PAYMENT-RESPONSE", "direction": "server to client", "role": "Base64-encoded SettlementResponse after settlement is attempted." } ], "source": "https://docs.x402.org/core-concepts/http-402", "verified_at": "2026-10-20" }, "payment_rail": { "value": "V2 schemes on the HTTP 402 page: exact and upto settle during the request, and batch-settlement confirms the authorization first and redeems on-chain later.", "source": "https://docs.x402.org/core-concepts/http-402", "verified_at": "2026-10-20" }, "networks": { "value": [ { "name": "Base", "caip2": "eip155:8453", "asset": null, "contract": null }, { "name": "Ethereum", "caip2": "eip155:1", "asset": null, "contract": null }, { "name": "Solana", "caip2": "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp", "asset": null, "contract": null }, { "name": "Base Sepolia", "caip2": "eip155:84532", "asset": null, "contract": null } ], "source": "https://docs.x402.org/guides/migration-v1-to-v2", "verified_at": "2026-10-20" }, "facilitators": { "value": [ { "name": "Facilitator used in the V2 seller example", "url": "https://x402.org/facilitator" } ], "source": "https://docs.x402.org/guides/migration-v1-to-v2", "verified_at": "2026-10-20" }, "client_libraries": { "value": [ { "name": "@x402/axios", "url": null }, { "name": "@x402/evm", "url": null }, { "name": "@x402/core", "url": null } ], "source": "https://docs.x402.org/guides/migration-v1-to-v2", "verified_at": "2026-10-20" }, "pay_flow": { "value": [ "The client requests the resource.", "The server returns HTTP 402 and a PAYMENT-REQUIRED header.", "The client signs a payment payload and retries with PAYMENT-SIGNATURE.", "The server verifies the payload itself or via a facilitator /verify call, then settles itself or via /settle.", "The server returns the resource and a PAYMENT-RESPONSE header. A failed settlement is another 402." ], "source": "https://docs.x402.org/core-concepts/facilitator", "verified_at": "2026-10-20" }, "notes": { "value": "V2 network ids use CAIP-2. The migration guide maps base to eip155:8453, ethereum to eip155:1, and solana to solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp. It does not publish a USDC contract address. V1 header names were X-PAYMENT and X-PAYMENT-RESPONSE. The scheme names exact, upto, and batch-settlement are on the HTTP 402 page.", "source": "https://docs.x402.org/guides/migration-v1-to-v2", "verified_at": "2026-10-20" }, "schemes": { "value": [ { "name": "exact", "bindings": [ "algo", "aptos", "canton", "cardano", "casper", "concordium", "evm", "hedera", "keeta", "lnbtc", "near", "starknet", "stellar", "sui", "svm", "ton", "xrpl" ], "notes": "specs/schemes/exact/scheme_exact_lnbtc.md says mainnet MUST use lnbtc:000000000019d6689c085ae165831e93 and testnet MUST use lnbtc:000000000933ea01ad0ee984209779ba. amount is a positive integer millisatoshi string. Bare numbers must not default to satoshis." }, { "name": "upto", "bindings": [ "evm", "svm", "xrpl" ], "notes": null }, { "name": "batch-settlement", "bindings": [ "cloudflare", "evm", "svm" ], "notes": null }, { "name": "auth-capture", "bindings": [ "evm" ], "notes": null } ], "source": "https://github.com/x402-foundation/x402/tree/main/specs/schemes", "verified_at": "2026-11-03" }, "implementation": { "value": "Python SDK 2.27.0, changelog heading 2026-11-04, says its SVM exact facilitators advertise and accept extra.transactionVersions [0, 1] by default. Clients build the highest version shared with the facilitator. Passing transaction_versions=[0] keeps that SDK on version 0. This is the Python SDK implementation. The exact scheme notes above do not say every binding must advertise transactionVersions.", "source": "https://github.com/x402-foundation/x402/blob/main/python/x402/CHANGELOG.md", "verified_at": "2026-11-06" } }, { "id": "mpp", "name": "MPP", "featured": false, "spec_url": { "value": "https://mpp.dev/protocol", "source": "https://mpp.dev/protocol", "verified_at": "2026-10-20" }, "http_status_codes": { "value": [ 402 ], "source": "https://mpp.dev/protocol/http-402", "verified_at": "2026-10-20" }, "http_headers": { "value": [ { "name": "WWW-Authenticate", "direction": "server to client", "role": "Payment challenge. Required parameters include id, intent, method, realm, and request." }, { "name": "Authorization", "direction": "client to server", "role": "Payment credential when the challenge does not set a header parameter." }, { "name": "Payment-Authorization", "direction": "client to server", "role": "Payment credential when the challenge sets header to Payment-Authorization." }, { "name": "Payment-Receipt", "direction": "server to client", "role": "Receipt after a successful payment." } ], "source": "https://mpp.dev/protocol/transports/http", "verified_at": "2026-10-20" }, "payment_rail": { "value": "Cards through Shared Payment Tokens, or stablecoins. Stripe docs name Tempo as a stablecoin network and say Tempo transfers use USDC.e.", "source": "https://docs.stripe.com/payments/machine/mpp", "verified_at": "2026-10-20" }, "networks": { "value": [ { "name": "Tempo", "caip2": null, "asset": null, "contract": null } ], "source": "https://docs.stripe.com/payments/machine/mpp", "verified_at": "2026-10-20" }, "facilitators": { "value": [ { "name": "Stripe", "url": "https://docs.stripe.com/payments/machine/mpp" } ], "source": "https://docs.stripe.com/payments/machine/mpp", "verified_at": "2026-10-20" }, "client_libraries": { "value": [ { "name": "mppx", "url": "https://mpp.dev/" } ], "source": "https://docs.stripe.com/payments/machine/mpp", "verified_at": "2026-10-20" }, "pay_flow": { "value": [ "The client requests the resource with no payment credential.", "The server returns HTTP 402 and a WWW-Authenticate Payment challenge.", "The client retries with an Authorization or Payment-Authorization credential.", "The server returns HTTP 200 and a Payment-Receipt header." ], "source": "https://mpp.dev/protocol/transports/http", "verified_at": "2026-10-20" }, "notes": { "value": "The challenges page uses 0x20c0000000000000000000006a37DA5C996874BE as an OUSD-on-Tempo example and says the sample identifiers are illustrative. This file does not treat that address as a canonical contract. CAIP-2 is not stated there.", "source": "https://mpp.dev/protocol/challenges", "verified_at": "2026-10-20" }, "implementation": { "value": "Aperture v0.6.0, published 2026-11-05 and not a prerelease, says a service with auth: l402+mpp answers an unpaid request with one 402 that carries both an L402 and a Payment challenge, and accepts either. MPP charges and sessions stay opt-in (enablempp, enablesessions). enablempp is refused at startup with the etcd backend; sqlite or postgres is required. A static price of 0 means the default price of 1 sat, not free.", "source": "https://github.com/lightninglabs/aperture/releases/tag/v0.6.0", "verified_at": "2026-11-05" } }, { "id": "ap2", "name": "AP2", "featured": false, "spec_url": { "value": "https://github.com/google-agentic-commerce/AP2/blob/main/docs/ap2/specification.md", "source": "https://github.com/google-agentic-commerce/AP2/blob/main/docs/ap2/specification.md", "verified_at": "2026-10-20" }, "http_status_codes": null, "http_headers": null, "payment_rail": { "value": "A Payment Mandate authorizes a payment instrument for a checkout. The instrument is not limited to one rail by the specification page.", "source": "https://github.com/google-agentic-commerce/AP2/blob/main/docs/ap2/specification.md", "verified_at": "2026-10-20" }, "networks": null, "facilitators": null, "client_libraries": { "value": [ { "name": "ap2 Python package (install from the repository)", "url": "https://github.com/google-agentic-commerce/AP2" } ], "source": "https://github.com/google-agentic-commerce/AP2/blob/main/README.md", "verified_at": "2026-10-20" }, "pay_flow": { "value": [ "The merchant gives the shopping agent a merchant-signed checkout JWT.", "A trusted surface signs a Checkout Mandate bound to a hash of that JWT.", "The shopping agent presents a Payment Mandate bound to the same checkout hash.", "The credential provider, network, and merchant payment processor verify the Payment Mandate.", "A signed Payment Receipt is returned after the mandate is accepted or rejected." ], "source": "https://github.com/google-agentic-commerce/AP2/blob/main/docs/ap2/specification.md", "verified_at": "2026-10-20" }, "notes": { "value": "A closed Payment Mandate uses vct mandate.payment.1. A closed Checkout Mandate uses vct mandate.checkout.1. AP2 does not define the commerce APIs around it. The specification says it is compatible with UCP. The pages checked do not name an HTTP status code or header.", "source": "https://github.com/google-agentic-commerce/AP2/blob/main/docs/ap2/specification.md", "verified_at": "2026-10-20" }, "docs_url": { "value": "https://ap2-protocol.org/llms.txt", "source": "https://ap2-protocol.org/llms.txt", "verified_at": "2026-10-26" }, "version": { "value": "v0.2", "source": "https://ap2-protocol.org/ap2/specification/index.md", "verified_at": "2026-10-26" }, "governance": { "value": "Google donated AP2 to the FIDO Alliance on 2026-04-28, transitioning ownership to the Alliance.", "source": "https://blog.google/products-and-platforms/platforms/google-pay/agent-payments-protocol-fido-alliance/", "verified_at": "2026-10-26" } }, { "id": "acp", "name": "ACP", "featured": false, "spec_url": { "value": "https://www.agenticcommerce.dev/", "source": "https://www.agenticcommerce.dev/", "verified_at": "2026-10-20" }, "http_status_codes": null, "http_headers": null, "payment_rail": { "value": "Delegated payment tokens between buyers, agents, and businesses, plus checkout payment processing. The docs do not name one chain or asset.", "source": "https://docs.stripe.com/agentic-commerce/protocols/acp", "verified_at": "2026-10-20" }, "networks": null, "facilitators": null, "client_libraries": null, "pay_flow": { "value": [ "An agent creates, updates, and completes a checkout session, including the cart and fulfillment options.", "Delegate payment passes a payment token from the buyer through the agent to the business.", "Delegate authentication uses OAuth 2.0 when the agent acts for the buyer.", "Webhooks report order, shipping, delivery, and refund updates." ], "source": "https://docs.stripe.com/agentic-commerce/protocols/acp", "verified_at": "2026-10-20" }, "notes": { "value": "Stripe describes ACP as an open standard created by Stripe, OpenAI, and Meta. The page points at agenticcommerce.dev for the specification. It does not name HTTP payment headers or status codes.", "source": "https://docs.stripe.com/agentic-commerce/protocols/acp", "verified_at": "2026-10-20" } }, { "id": "ucp", "name": "UCP", "featured": false, "spec_url": { "value": "https://ucp.dev/", "source": "https://ucp.dev/", "verified_at": "2026-10-20" }, "http_status_codes": null, "http_headers": null, "payment_rail": { "value": "Secure payment via AP2, using payment mandates and verifiable credentials.", "source": "https://ucp.dev/", "verified_at": "2026-10-20" }, "networks": null, "facilitators": null, "client_libraries": null, "pay_flow": { "value": [ "Discover products through catalog search and lookup.", "Build a cart.", "Link identity with OAuth 2.0. The site shows a /.well-known/oauth-authorization-server document as the account-linking pattern.", "Complete checkout. The site says payment uses AP2.", "Track the order after purchase." ], "source": "https://ucp.dev/", "verified_at": "2026-10-20" }, "notes": { "value": "The site says transports are REST and JSON-RPC, and that AP2, A2A, and MCP support is built in. It does not name an HTTP payment header, status code, CAIP-2 id, or asset contract. The specification repository is https://github.com/universal-commerce-protocol/ucp.", "source": "https://ucp.dev/", "verified_at": "2026-10-20" } }, { "id": "mcp", "name": "MCP", "featured": false, "spec_url": { "value": "https://modelcontextprotocol.io/specification/2026-07-28", "source": "https://modelcontextprotocol.io/specification/2026-07-28", "verified_at": "2026-10-28" }, "http_status_codes": null, "http_headers": null, "payment_rail": null, "networks": null, "facilitators": null, "client_libraries": null, "pay_flow": null, "notes": { "value": "SEP-3398 does not state HTTP status codes, headers, a payment rail, networks, facilitators, client libraries, or a pay flow, so those fields are null. It says it introduces no protocol messages, schema changes, version-negotiation changes, or new requirements for deployed clients and servers. 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. Those offsets are planning targets. The published release calendar defines the exact dates.", "source": "https://github.com/modelcontextprotocol/modelcontextprotocol/pull/3398", "verified_at": "2026-10-28" }, "release_cadence": { "value": "semiannual: generally the last Tuesday of March and September. Release managers confirm the exact date in each cycle's published calendar.", "source": "https://github.com/modelcontextprotocol/modelcontextprotocol/pull/3398", "verified_at": "2026-10-28" }, "next_release_target": { "value": "2027-03-30 (last Tuesday of March 2027; the December 2026 target moves here, subject to confirmation in the transition calendar)", "source": "https://github.com/modelcontextprotocol/modelcontextprotocol/pull/3398", "verified_at": "2026-10-28" }, "extension_stages": { "value": { "lifecycle": "An extension starts as Experimental, may advance to Beta, and then either becomes Stable as an extension or is promoted into the core specification.", "marker": "The stage is the directory specification/experimental, specification/beta, or specification/stable. The repository name does not show the stage. An earlier draft used experimental-ext-, beta-ext-, and ext- prefixes.", "at_final": [ { "repositories": [ "ext-apps", "ext-auth" ], "stage": "stable", "directory": "specification/stable/" }, { "repositories": [ "ext-skills", "ext-tasks", "ext-server-card" ], "stage": "beta", "directory": "specification/beta/" }, { "repositories": [ "experimental-ext-interceptors", "experimental-ext-variants", "experimental-ext-triggers-events", "experimental-ext-tool-annotations" ], "stage": "experimental", "directory": null } ] }, "source": "https://github.com/modelcontextprotocol/modelcontextprotocol/pull/3392", "verified_at": "2026-10-31" }, "mcp_sdk_tiers": { "value": { "tier_1": [ "TypeScript", "Python", "C#", "Go", "Rust", "Ruby" ], "note": "The 2026-10-30 post says the official Ruby SDK is now Tier 1 and joins the TypeScript, Python, C#, Go, and Rust SDKs. The post does not use the word sixth, and this page was not a separate tier registry." }, "source": "https://blog.modelcontextprotocol.io/posts/ruby-sdk-tier-1/", "verified_at": "2026-11-04" } }, { "id": "a2a", "name": "A2A", "featured": false, "spec_url": { "value": "https://a2a-protocol.org/latest/specification/", "source": "https://a2a-protocol.org/latest/specification/", "verified_at": "2026-11-03" }, "http_status_codes": null, "http_headers": null, "payment_rail": null, "networks": null, "facilitators": null, "client_libraries": null, "pay_flow": null, "notes": { "value": "This record cites the version tags only. The GitHub releases list fetched on 2026-11-03 has v1.0.1 as the newest release, published 2026-05-28, and it is not a prerelease. Tag v1.1.0-rc is not in that releases list. It points at commit 78e1d6a1f7f118c8e9bc830b04a8579c1119cb78, dated 2026-10-29T12:05:26Z. Payment fields are null because those pages were not read for payment facts.", "source": "https://github.com/a2aproject/A2A/releases/tag/v1.0.1", "verified_at": "2026-11-03" }, "version": { "value": "1.0.1", "source": "https://github.com/a2aproject/A2A/releases/tag/v1.0.1", "verified_at": "2026-11-03" }, "next_version": { "value": "1.1.0-rc", "source": "https://github.com/a2aproject/A2A/tree/v1.1.0-rc", "verified_at": "2026-11-03" } } ] }