Documentation

Install

On Linux and macOS (amd64 or arm64):

curl -fsSL https://127ohoh1.com/install.sh | sh

The script is generated from the current signed release. It picks the build for your machine, downloads it from this site, installs it only if its SHA-256 matches the release manifest, and puts it in /usr/local/bin if that is writable, otherwise in ~/.local/bin (set INSTALL_DIR to choose). Prefer to read it first: https://127ohoh1.com/install.sh.

Manual install, and Windows: the signed manifest at /v1/cli/releases/latest lists every build with its SHA-256 and size; download one from /v1/cli/releases/<version>/<name> (for example 127ohoh1-windows-amd64.exe) and compare its SHA-256 with the manifest. The manifest itself is signed with the release Ed25519 key (key_id, signature).

Quick start

127ohoh1 expose http://127.0.0.1:3000

The first run creates an identity key (mode 0600). Keep it like an SSH key: it is your identity.

Link the CLI to your account

An account is optional. To manage paid names and notifications, run ohohctl link (the product companion to the CLI; it shows a short code), then enter it in the dashboard under Devices. Linking needs a fresh email confirmation and never changes who owns an endpoint.

Paying for a name (HTTP 402 / x402)

Reserving a name without an entitlement returns 402 Payment Required with a machine-readable body. The body carries the exact price, asset, network and an x402-compatible accepts list. Pay the exact USDC amount, then repeat the original request with the same Idempotency-Key. Status is honest: awaiting, confirming, settled; a name is reserved only after final settlement.

API

The control-plane API is described by an OpenAPI document; the product adds customer routes under /v1/customer/.