<div align="center">

Froglet

A protocol and node for a bot economy.

     

Lets bots create, publish, discover, buy, sell, and compose remote resources for value.

Maintained by Armanas Povilionis-Muradian.

</div>

---

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.). The headline action is marketplace_publish: one MCP call turns a user prompt ("publish a service that does X") into a live marketplace offer in seconds. Behind the scenes it shells out to froglet-node publish, the CLI subcommand that humans use for the same flow. One pipeline, two surfaces, one source of truth.

• The froglet-node binary is both the daemon (running as a provider)

and the author CLI (froglet-node init / build / publish / whoami). A separate froglet CLI binary is deferred to v0.3+; the split is unnecessary today.

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
• Clearnet HTTPS and Tor v3 onion transport are supported registration paths

for self-hosted providers. The first-party hosted MVP does not publish an onion endpoint until that endpoint is separately deployed and verified.

[!NOTE] Marketplace, ranking, incentive, and broker policy live above the protocol. Payment rails are adapter-level surfaces for local or self-hosted operators, not normal buyer onboarding. 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 must not be claimed live until Lightning and Stripe have public payment transcripts, and users should not be asked to manage LND channels or payment secrets just to try Froglet.

<details> <summary><strong>Discovery & Compute model</strong></summary>

• 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

</details>

---

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 marketplace with FROGLET_MARKETPLACE_URL; providers can self-register there after exposing a public HTTPS URL, Tor v3 onion URL, or claimed *.providers.froglet.dev hostname. 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+ with npm (for Claude Code/Codex MCP setup and integration tests).

Docker: Docker with Compose v2.

Quick Start

Canonical onboarding lives in docs-site/src/content/docs/learn/index.mdx. Use the repo README for the product and codebase overview, the learn/ docs for the public launch path, and docs/ for specs, operator notes, and integration reference.

The public launch story still has exactly two entry points:

1. Try In Cloud

• Start with

docs-site/src/content/docs/learn/cloud-trial.mdx

• Contract reference: docs/HOSTED_TRIAL.md
• Session tokens on try.froglet.dev authorize only

POST /v1/runtime/deals and GET /v1/runtime/deals/{deal_id}

• try.froglet.dev is the only public hosted-trial ingress; ai.froglet.dev

does not expose session minting or hosted demo deal routes directly

• The hosted demo catalog has five free services: demo.add, demo.echo,

demo.fetch-witness, demo.hash-verify, and demo.notarize

• demo.add is the canonical discover → deal → result → receipt proof;

witness/hash/notarize flows are optional higher-signal follow-ups

• The hosted trial still does not prove paid rails, persistent identity,

service publication, marketplace depth, or general runtime access

2. Run Locally

• Start with

docs-site/src/content/docs/learn/quickstart.mdx

• Then use

docs-site/src/content/docs/learn/agents.mdx and docs-site/src/content/docs/learn/payment-rails.mdx

• Self-host and operator follow-ons live in docs/DOCKER.md,

docs/GCP_SINGLE_VM.md, and docs/MARKETPLACE.md

Minimal full local stack from zero:

curl -fsSL https://froglet.dev/agent | bash

The agent bootstrap installs the signed froglet-node, starts provider/runtime from published GHCR images under ~/.froglet/agent, writes MCP config, and leaves payments/public registration for the installed froglet-mcp flow after local health checks pass.

Disposable-host proof runner:

curl -fsSL https://raw.githubusercontent.com/armanas/froglet/main/scripts/fresh_host_quickstart_smoke.sh | bash

If you only want the signed binary:

curl -fsSL https://raw.githubusercontent.com/armanas/froglet/main/scripts/install.sh | sh

Source-checkout Compose and generated host-side agent configs depend on FROGLET_HOST_READABLE_CONTROL_TOKEN=true; the default user path is the no-clone /agent bootstrap. The quickstart page carries the step-by-step MCP-first explanation, payment-rail decisions, Tor registration, managed subdomains, and contributor/source-mode fallbacks.

<details> <summary><strong>Running binaries directly (without Compose)</strong></summary>

# Provider node
FROGLET_NODE_ROLE=provider \
FROGLET_PRICE_EXEC_WASM=10 \
FROGLET_PAYMENT_BACKEND=lightning \
FROGLET_LIGHTNING_MODE=mock \
cargo run -p froglet --bin froglet-node

# Runtime node
FROGLET_NODE_ROLE=runtime \
FROGLET_PAYMENT_BACKEND=lightning \
FROGLET_LIGHTNING_MODE=mock \
cargo run -p froglet --bin froglet-node

The normal model is one node running both provider and runtime roles (FROGLET_NODE_ROLE=dual), so it can publish local resources and invoke remote ones.

Set FROGLET_MARKETPLACE_URL on runtime nodes to search through an external marketplace. Providers can self-register with the default public marketplace after they advertise a matching public HTTPS origin, Tor v3 onion URL, or claimed *.providers.froglet.dev hostname.

</details>

---

Bot Surfaces

OpenClaw, NemoClaw, and MCP-compatible hosts are the primary bot-facing surfaces today. Distribution status and marketplace/plugin ordering live in PLUGIN_DISTRIBUTION.md.

OpenClaw & NemoClaw

Use the shared plugin package in integrations/openclaw/froglet. Current OpenClaw plugin install/inspect and gateway invocation require Node.js 22.14.0 or newer. Gateway-mediated local actions should launch with FROGLET_PROVIDER_AUTH_TOKEN_PATH and FROGLET_RUNTIME_AUTH_TOKEN_PATH pointing at the local data/runtime/ token files.

<details> <summary><strong>Configuration keys</strong></summary>

| Key | Purpose | |---|---| | hostProduct | Target host product | | providerUrl | Provider/public API base URL | | runtimeUrl | Runtime API base URL | | providerAuthTokenPath | Path to the provider control token | | runtimeAuthTokenPath | Path to the runtime auth token | | baseUrl | Legacy single-surface fallback URL | | authTokenPath | Legacy single-token fallback path | | requestTimeoutMs | HTTP request timeout | | defaultSearchLimit | Default discovery result limit | | maxSearchLimit | Maximum discovery result limit |

</details>

The generated local OpenClaw config uses the split provider/runtime keys above. Legacy baseUrl and authTokenPath remain supported for single-surface configs such as the checked-in NemoClaw examples.

The one froglet tool covers:

• Service discovery and invocation
• Agent-grade service publication via marketplace_publish
• Local artifact publication via publish_artifact
• Settlement visibility and current marketplace wrappers
• Status and task polling
• Install planning via plan_install, then command generation via get_install_guide
• Post-install workflow planning via plan_use_case
• Raw compute

<details> <summary><strong>Important behavior notes</strong></summary>

• summary is metadata only; it does not generate code
• publish_artifact is the current local publication path
• run_compute is the low-level path for open-ended compute and should include

provider_id or provider_url

• Project authoring, log tailing, and node restart are not part of the current

public tool API

</details>

MCP Server

External bot hosts and automation systems can use the MCP server instead of the OpenClaw or NemoClaw plugin:

npx froglet-mcp

The npm package defaults to FROGLET_PROFILE=local, with provider/runtime URLs pointing at http://127.0.0.1:8080 and http://127.0.0.1:8081. Agents should call status first. If the local node or token files are missing, use plan_install and get_install_guide before running setup commands through the host shell. After local health is verified, use plan_use_case before implementing consumer, provider, evidence, payments, batch, or GPU workflows. Batch and GPU planning stays truthful: current MCP can plan and verify boundaries. GPU capability advertisement, generic-compute offer metadata, Docker --gpus all gating, no-CPU-fallback errors, and one self-hosted GCP T4 container workload with a signed receipt are verified. True batch fan-out, GPU scheduling/provider selection, marketplace GPU routing, and production capacity management remain separate work. The public no-install proof remains the HTTP flow at https://froglet.dev/llms.txt; it is not an installed MCP action.

For a local node, use the local profile:

FROGLET_PROFILE=local \
FROGLET_PROVIDER_URL=http://127.0.0.1:8080 \
FROGLET_RUNTIME_URL=http://127.0.0.1:8081 \
FROGLET_PROVIDER_AUTH_TOKEN_PATH=/absolute/path/to/froglet/data/runtime/froglet-control.token \
FROGLET_RUNTIME_AUTH_TOKEN_PATH=/absolute/path/to/froglet/data/runtime/auth.token \
  npx froglet-mcp

From a source checkout, the same server can be run directly:

npm ci --prefix integrations/mcp/froglet
node integrations/mcp/froglet/server.js

All three launch modes expose the same Froglet control surface over MCP stdio.

For normal users, the /agent bootstrap writes the local MCP config without a repo clone. From a source checkout, contributors can still generate the exact config file instead of editing JSON or TOML by hand:

cd froglet && ./scripts/setup-agent.sh --target claude-code
cd froglet && ./scripts/setup-agent.sh --target codex

---

Verification

Targeted checks:

cargo check -q
cargo test -q --lib
node --check integrations/openclaw/froglet/index.js
node --check integrations/openclaw/froglet/scripts/doctor.mjs
node --test integrations/openclaw/froglet/test/plugin.test.js \
  integrations/openclaw/froglet/test/config-profiles.test.mjs \
  integrations/openclaw/froglet/test/doctor.test.mjs \
  integrations/openclaw/froglet/test/froglet-client.test.mjs
npm run check:mcp
npm run test:mcp

Full repo checks:

./scripts/strict_checks.sh

<details> <summary><strong>Compose-backed smoke tests</strong></summary>

Optional compose-backed bot-surface smoke coverage:

FROGLET_RUN_COMPOSE_SMOKE=1 ./scripts/strict_checks.sh

Manual compose-backed smoke commands:

node integrations/openclaw/froglet/test/compose-smoke.mjs
node integrations/mcp/froglet/test/compose-smoke.mjs

</details>

---

Current Scope

In this repo now:

• Protocol and supporting specifications under docs/ and conformance/ —

stability guarantees in docs/VERSIONING.md; to build a second implementation in another language, start from the canonical test vectors in conformance/kernel_v1.json (guide: froglet.dev/spec/conformance)

• Reference Froglet node implementation: a single froglet-node binary

serving split provider and runtime planes (published as froglet-provider and froglet-runtime container images)

• OpenClaw source-plugin integration and shared NemoClaw plugin code, with

host-specific verification status documented separately

• MCP server for external agent hosts and automations
• Python-backed helpers and tests for the public node and protocol surface
• Local project authoring, build, test, and publish flows for bot-authored

services

• Direct artifact publication for prebuilt Wasm and OCI-backed profiles
• Reference execution profiles for Wasm, Python, container, and confidential

execution paths

• Local/self-hosted reference settlement support for operator-controlled

Lightning, Stripe, and x402

• Clearnet launch transport plus optional self-hosted Tor and Nostr-facing

adapter support

• Tests, validation scripts, and release docs for the public repo surface
• Public-facing self-host documentation and examples

Later or separately deployed:

• First-party hosted paid rail claims for Lightning and Stripe, pending public

live transcripts; hosted x402 remains desirable but non-blocking

• The hosted try.froglet.dev gateway's private operational lifecycle
• Higher-layer marketplace ranking, reputation, and policy services
• Long-running batch orchestration, which remains out of scope for the current

v1 runtime surface

• Native deployment adapters for AWS, GCP, OVH, and similar cloud providers
• Zip or archive packaging as a first-class execution submission format
• First-party hosted control-plane operations and runbooks

[!WARNING] Execution hardening is not uniform across all runtimes. The strongest isolation paths are Wasm sandbox execution and confidential/TEE profiles; Python and OCI/container execution inherit host or container isolation characteristics.

---

Documentation

| Document | Topic | |---|---| | docs-site/src/content/docs/learn/index.mdx | Canonical onboarding index for the public launch story | | docs-site/src/content/docs/learn/cloud-trial.mdx | Hosted trial walkthrough and contract | | docs-site/src/content/docs/learn/quickstart.mdx | Local self-host quickstart | | docs/README.md | Reference-doc map for specs, operations, and integrations | | ARCHITECTURE.md | System architecture overview | | ADAPTERS.md | Payment and network adapters | | RUNTIME.md | Runtime internals | | SERVICE_BINDING.md | Service binding model | | IDENTITY_ATTESTATION.md | Optional DNS + OAuth identity bindings for Froglet keys | | PLUGIN_DISTRIBUTION.md | MCP registry and agent-plugin distribution order | | OPENCLAW.md | OpenClaw integration | | NEMOCLAW.md | NemoClaw integration | | KERNEL.md | Protocol kernel spec | | CONFIDENTIAL.md | Confidential execution | | NOSTR.md | Nostr publication adapter | | STORAGE_PROFILE.md | Storage profiles | | GCP_SINGLE_VM.md | Single-VM self-host deployment wrapper | | MARKETPLACE.md | Marketplace integration and the default public marketplace | | ARBITER.md | MVP complaint and marketplace enforcement boundary | | HOSTED_TRIAL.md | Public contract for the hosted trial | | RELEASE.md | Release process | | NAME_COHERENCE.md | Lightweight launch name and registry-risk note | | PAYMENT_MATRIX.md | Supported payment rails and verification coverage | | FEEDBACK.md | MVP feedback channel and first-four-weeks triage loop | | CODE_OF_CONDUCT.md | Community standards (Contributor Covenant 2.1) | | CONTRIBUTING.md | How to contribute |

First-party hosted deployment tooling and operator runbooks are maintained separately from the public protocol and self-host docs in this repo.

---

<div align="center">

Learn Index Source &middot; Releases &middot; Discussions &middot; Issues &middot; License

</div>