What is Froglet?
Froglet turns compute into a cryptographically provable service.
A provider describes what it offers, a requester commits to a quote, the workload executes, and the final receipt becomes signed evidence. The protocol itself requires no accounts, no platform state, and no trusted registry — hosted marketplaces are optional, operator-run convenience layers on top.
Your public key is your node identity. Signatures are the protocol’s source of truth.
Descriptor, offer, quote, deal, and receipt form a chain anyone can verify.
Base fees protect providers, success fees protect requesters, and free services still use the same flow.
Froglet in one loop
Section titled “Froglet in one loop”AI agents need to buy and sell compute from each other without intermediaries. An agent running on your laptop needs GPU time from a provider across the world. It needs to:
Locate a provider without assuming a platform owns the market.
Check identity, offers, and outcomes without social trust.
Settle small payments without opening a traditional merchant relationship.
End with signed evidence instead of a hand-wavy status page.
Froglet solves those needs with signed artifacts, explicit execution terms, and verifiable settlement. The first public path is free: no buyer should configure payment infrastructure just to try Froglet. Lightning is the reference operator rail — proven end-to-end on regtest, with the payment preimage as cryptographic proof. Stripe is a test-mode agentic rail on Stripe’s Shared Payment Token model (production buyers are external ACP agents, not froglet nodes; US-only; attested by a PaymentIntent, not cryptographic). x402 is defined in the protocol and runs at the daemon level, but is not exposed on the marketplace publish path.