How Froglet compares
Froglet helps people and agents offer a service, agree the terms of a request, run it, and keep signed records. Payment is one part of that process; a free service uses the same offer, quote, deal, and receipt flow.
Payment and commerce protocols overlap with parts of this work. Their open specifications and the requirements of a particular hosted product are separate things.
Different responsibilities
Section titled “Different responsibilities”| Project | Main focus | Read the source |
|---|---|---|
| Froglet | Service offers, per-request commitments, execution limits, and signed outcome records. | Deal flow and kernel |
| A2A | Agent discovery and task communication, including capability and extension negotiation. The agent’s implementation supplies execution. | A2A specification |
| x402 | Payment over HTTP: a server requests payment and a client retries with payment information. | x402 documentation |
| L402 | Paid access to digital resources using a token bound to a Lightning invoice and its payment preimage. | Lightning Labs documentation |
| AP2 | Evidence of authorization for agent payments, using verifiable credentials and mandates. | AP2 specification |
| ACP | Agent commerce, including checkout and merchant fulfillment, with support for different payment processors. | ACP specification |
AP2 is broader than moving money, and ACP is not inherently limited to a Stripe account or a ChatGPT seller application. A particular integration may impose onboarding requirements beyond the protocol itself.
What Froglet’s records establish
Section titled “What Froglet’s records establish”A verifier can check the signatures and hash bindings across the descriptor, offer, quote, deal, and receipt, plus the invoice bundle when the chosen rail requires one. These records identify the signing keys, the agreed terms, and the provider’s reported outcome. A result hash binds a receipt to particular result bytes.
This is evidence of commitments and reported outcomes, not a cryptographic proof that an arbitrary computation was performed correctly. The same care applies to settlement: what can be verified depends on the payment method. See Trust & Economics and Settlement.
What to evaluate before choosing
Section titled “What to evaluate before choosing”- The task: sharing selected data, selling API access, authorizing a purchase, and completing a shopping checkout have different requirements.
- Deployment: assess the actual implementation, hosting, credentials, and payment infrastructure you will operate, as well as the specification.
- Recourse: signatures make claims attributable; they do not automatically provide refunds, chargebacks, or enforce a legal agreement.
- Maturity: Froglet is a public beta. Its supported first-use journey is free sharing. Lightning has recorded regtest evidence, Stripe is test-mode, and x402 is a daemon-level prototype outside the publish path. See the current payment guide.
Possible combinations
Section titled “Possible combinations”MCP connects an assistant to Froglet’s native tool. The optional A2A adapter connects configured requester and provider Nodes using A2A 1.0 HTTP+JSON and a required Froglet extension. The Node supplies the bounded Wasm executor and signed deal lifecycle behind those interfaces. See the working profile and local demo.
A2A plus a payment adapter and a suitable executor could support a similar application. Froglet is a particular implementation of the execution controls and transaction lifecycle; the claim is not that those capabilities are fundamentally unavailable in another stack.
An authorization system could authorize a Froglet request, and a payment adapter could settle it. These are architectural possibilities, not claims that AP2, ACP, or L402 interoperability has been implemented and tested. Froglet’s experimental x402 adapter has its own documented limits.
This comparison describes responsibilities, not adoption rankings. The A2A specification and current Froglet integration were checked on 1 October 2026; the other primary sources were checked on 27 September 2026. Implementation status can change.