froglet

---

Table of Contents

• Overview
• Product Model
• Components
• Quick Start
• Bot Surfaces
• Verification
• Current Scope
• Documentation

---

Overview

Froglet gives one signed economic primitive for three product shapes:

Shape	Description
Named Services	Discoverable, published service endpoints
Data-Backed Services	Services backed by bot-authored data or projects
Open-Ended Compute	Raw compute targeted via provider_id or provider_url

The primary bot-facing integration surfaces are intentionally simple:

• One OpenClaw/NemoClaw plugin id: froglet (at integrations/openclaw/froglet/)
• One MCP server under integrations/mcp/froglet/, published as froglet-mcp for npx froglet-mcp
• Both surfaces register a single agent-facing tool named froglet to the host (Claude Code, Codex, Cursor, Windsurf, etc.). This is the "tool" exposed to the agent, not a standalone CLI binary — the only shipped binary is froglet-node. A standalone froglet-cli wrapper is on the v0.2 backlog.

Bots should be able to create small scriptable services directly, validate them locally, and publish them without starting from OCI images. OCI containers remain a supported packaging and deployment path.

---

Product Model

• Any Froglet node can publish resources and invoke remote resources
• Published resources are execution bindings backed by bot-authored projects, explicit source, or prebuilt artifacts
• Easy bot authoring and local checking of scriptable services is a core product requirement
• Identity is first-class in signed artifacts
• The same signed deals can be served over clearnet HTTPS or Tor onion endpoints

[!NOTE] Marketplace, ranking, incentive, and broker policy live above the protocol. Payment rails are adapter-level surfaces for local or self-hosted nodes. Lightning, Stripe, and x402 are the launch adapters in this repo. Only Lightning currently extends into the standardized signed quote/deal/invoice-bundle flow; Stripe and x402 are local runtime settlement adapters. The first-party hosted try.froglet.dev trial is free-only: it uses demo.add as the canonical proof and exposes optional demo.fetch-witness, demo.hash-verify, and demo.notarize follow-ups for stronger evidence. Hosted paid rails are deferred to v0.2.

Discovery & Compute model

• Named services and data services are discovered through discovery
• Open-ended compute uses the provider's direct compute offer via run_compute, targeted with provider_id or provider_url
• Publication and bootstrap adapters may include Nostr-style publication without making any single relay or network the kernel source of truth

---

Components

Product-wise, Froglet is one node that can both provide and consume. The reference implementation exposes these binaries:

Binary	Purpose	Default Port
froglet-node	Provider and/or runtime node (role configured via env)	8080 / 8081

[!TIP] Marketplace integration is part of the public Froglet surface. Runtimes can point at the default public read marketplace with FROGLET_MARKETPLACE_URL; provider auto-registration requires a write-capable marketplace endpoint. See docs/MARKETPLACE.md.

---

Prerequisites

Binary install (quickest): curl, tar, sha256sum (Linux) or shasum (macOS). Supported: Linux x86_64/arm64, macOS arm64.

Build from source: Rust 1.91+, Python 3.12+ (for tests), Node 18+ (optional, for MCP/OpenClaw integration tests).

Docker: Docker with Compose v2.

Quick Start