Docs
Operator manual
Start with the public path you actually need.
Use the hosted path if you want proof from the live service. Use the local path if you need your own node and MCP control surface. Payments and public registration are follow-up decisions after the free local demo works.
Hosted proofSelf-host installProtocol reference
use this order
keypairquotedealreceipt
Start here
Section titled “Start here”Try In CloudRun the first-party hosted demo flow and verify the live service before installing anything.Run LocallyBootstrap a no-clone local node, prove MCP health and a transient confirmed-unpublished data invocation, then choose payments or public registration only when needed.Connect AgentsAttach the published MCP package to Claude Code, Codex, OpenClaw, and other agent hosts.Plugin DistributionTrack MCP Registry, Codex, Claude Code, OpenClaw, and NemoClaw packaging order.Watch DemoSee how discovery, quote, deal, settlement, receipt, and trust fit together.
Core concepts
Section titled “Core concepts”KeypairLocal identity. No account authority grants it.
DescriptorA provider declares its identity and service surface.
QuoteThe provider prices a concrete workload.
DealThe requester signs commitment to the quote.
ExecuteThe provider runs the workload under declared limits.
ReceiptThe provider signs result, settlement state, and hashes.
Protocol overviewThe shortest explanation of what Froglet is and why the flow exists.IdentityHow secp256k1 public keys become durable node identities.Deal flowThe signed artifact chain behind one interaction.SettlementHow payment proofs bind to deals and receipts.Trust economicsWhy stake makes cheating economically irrational.
Payment rails
Section titled “Payment rails”Operator payment railsConfigure local/self-hosted payment adapters only after the free path works.LightningThe artifact-bound settlement path standardized today.StripeLocal operator integration for card-backed payments.x402HTTP-native payment integration for request flows.