@h1dr4/h3retik-cloud

@h1dr4/h3retik-cloud

Headless CLI for h3retik cloud.

Default API base:

• https://h1dr4.dev/h3retik/api

Install

npm i -g @h1dr4/h3retik-cloud

Core Model

• Humans use receipt-first rental: CLI prints a Base payment address, waits, and stores session access after payment.
• Agents can still use signed payment flow with Base MCP or another approved wallet runtime.
• x402-capable agents can bypass the CLI and call POST /v1/x402/sessions directly. The endpoint returns 402 Payment Required and unlocks a session after facilitator settlement.
• Backend validates onchain payment and unlocks session/job execution.
• Private keys are never sent to the backend.

Cloud runs do not require client-side RPC.

Quick Start

# 1) rent disposable command compute
h3retik-cloud rent --minutes 15 --actions 10 --location auto --asset USDC

# The CLI prints a receipt address. Send the displayed Base USDC/H1DR4 amount.
# It waits until payment is detected and stores session auth locally.

# 2) run any authorized command inside the paid window
h3retik-cloud exec --lane local --cmd "apt-get update -y && apt-get install -y jq"

# 3) run another bounded job or fetch output
h3retik-cloud exec --lane web --cmd "curl -I https://example.com"
h3retik-cloud jobs output --job job_xxx

Tor Lens

Tor Lens is a session-paid plugin for public onion access from disposable H3RETIK compute. It is intentionally lead-driven: bring an onion URL or query a public onion index. H3RETIK does not bundle dark-market link lists.

# Optional plugin hint; billing/session flow is unchanged.
h3retik-cloud rent --plugin tor-lens --minutes 15 --actions 10 --location auto --asset USDC

# Fetch a known public onion URL through Tor.
h3retik-cloud tor fetch "http://example.onion"

# Render a known public onion URL through headless Chromium over Tor.
# The result includes screenshot metadata and screenshot_b64 unless disabled.
h3retik-cloud tor render "http://example.onion" --json

# Crawl bounded public onion links from a seed URL.
h3retik-cloud tor crawl "http://example.onion" --depth 1 --max-pages 8 --json

# Search Ahmia-style public onion indexes for candidate URLs.
# This is index search, not native Tor search; Tor/SOCKS does not provide discovery.
h3retik-cloud tor search-index "wallet scam marketplace alias" --json

Actions:

• fetch: status, title, text preview, body hash, text hash, links, onion links.
• render: fetch result plus Chromium screenshot hash and optional base64 PNG.
• crawl: bounded crawl from a public onion seed URL.
• extract: same Tor access path as fetch, intended for structured extraction.
• search-index: natural-language query against public onion indexes such as Ahmia.

Boundaries:

• Public onion pages only.
• No logins, purchases, CAPTCHA bypass, malware interaction, credential use, or private access.
• Use --no-screenshot-b64 when the caller only needs screenshot hashes/metadata.

H1DR4 Workers

Workers are hosted H3RETIK sessions with a preset objective and an inference reserve. They use the same receipt UX as normal compute: the CLI prints one Base funding address, waits for payment, then stores worker_id, session_id, and bearer auth locally.

Presets:

• dossier: source-backed H1DR4 dossier/tip preparation for an area, clue, or entity.
• redteam: scoped on-chain/off-chain recon with H3RETIK OS tooling.
• bounty: H1DR4 bounty/mission monitoring and completion evidence.
• custom: caller-defined objective, tools, and constraints.

Packages:

• micro: 1 hour / 10 actions / 10 USDC inference reserve.
• day: 24 hours / 50 actions / 25 USDC inference reserve.
• ops: 7 days / 250 actions / 50 USDC inference reserve.
• campaign: 15 days / 500 actions / 100 USDC inference reserve.

# Quote the worker before payment.
h3retik-cloud worker quote \
  --preset dossier \
  --package day \
  --target "Manhattan" \
  --goal "Prepare source-backed dossier updates for street-level incidents"

# Rent with receipt-first UX. The terminal unlocks after Base payment.
h3retik-cloud worker rent \
  --preset dossier \
  --package day \
  --target "Manhattan" \
  --location us \
  --asset USDC \
  --accept-tos

# Run the worker bootstrap/playbook job.
h3retik-cloud worker run

# Optional custom command inside the worker session.
h3retik-cloud worker run --cmd "python3 --version && curl -I https://h1dr4.dev"

# Read state at any time.
h3retik-cloud worker status
h3retik-cloud worker usage

# Custom workers route automatically by default.
h3retik-cloud worker quote --preset custom --goal "Analyze this wallet graph" --model-mode auto

# Or inspect the live Blockrun catalog and pin one model.
h3retik-cloud worker models
h3retik-cloud worker rent --preset custom --goal "Analyze this wallet graph" --model-mode manual --model deepseek/deepseek-chat --accept-tos

# Plugin-style entrypoint, equivalent to worker rent with worker flags.
h3retik-cloud rent --plugin workers --preset bounty --package micro --target "open H1DR4 missions" --accept-tos

The receipt amount is platform_fee_usdc + inference_budget_usdc. H3RETIK tracks the inference reserve on the worker ledger so unused reserve can be reconciled/refunded by policy after expiry.

H1DR4 Sentinel district rights

Sentinel is not a public H3RETIK scan-agent package. H3RETIK remains the disposable compute CLI. Sentinel district rights live in H1DR4/Yard: a receipt-gated district lease can unlock creator/originator flow for qualifying community reports geocoded inside that district.

Use H1DR4/Yard to discover Sentinel district unlocks:

https://h1dr4.dev/yard
h1dr4_list_sentinel_districts

Government/reference/sanctions records remain research-only and are never monetized by Sentinel districts.

Receipt Commands

h3retik-cloud rent --minutes 15 --actions 10 --location auto --asset USDC
h3retik-cloud receipts create --minutes 15 --actions 10 --asset H1DR4 --json
h3retik-cloud receipts wait --receipt rcpt_xxx
h3retik-cloud receipts sync --receipt rcpt_xxx --json
h3retik-cloud exec --cmd "uname -a"

rent is the default human UX. It generates a deterministic receipt vault, prints the address, polls the backend, and stores the returned bearer token when the payment is verified.

Agent / Signed Wallet Flow

run orchestrates: ToS accept -> session quote/rent -> optional setup command -> job create/pay/start -> output. run requires an existing auth token in state (auth challenge + auth verify done first) and explicit tx hashes.

h3retik-cloud run \
  --confirm \
  --wallet 0xYOUR_WALLET \
  --asset USDC \
  --location auto \
  --minutes 10 \
  --actions 3 \
  --target example.com \
  --lane local \
  --pipeline quick \
  --session-tx 0xSESSION_PAYMENT_TX \
  --job-tx 0xJOB_PAYMENT_TX \
  --cmd "curl -I https://example.com" \
  --json

Location can be auto, us, europe, or asia. Use auto unless a job needs a specific proximity lane.

Wallet Helpers

h3retik-cloud wallet init --json
h3retik-cloud wallet init --install-wallet --json
h3retik-cloud wallet init --install-wallet --wallet-source github:nativ3ai/h1dr4-wallet --json
h3retik-cloud wallet address --private-key 0xKEY
h3retik-cloud wallet balance --wallet 0xWALLET --rpc-url https://base-mainnet.g.alchemy.com/v2/YOUR_KEY

wallet init behavior:

• if h1dr4-wallet exists on PATH: reuse
• if missing and --install-wallet: install from source candidates
• you can force source with --wallet-source

Agent-Safe Flags

• --json: machine-readable output
• --dry-run: preview run plan without execution
• --confirm: required execution gate for run
• --job-id: idempotent jobs create retries
• --session, --job: target existing resources
• --asset: USDC or H1DR4
• --location: auto, us, europe, or asia
• --session-tx, --job-tx: explicit invoice payment tx hashes
• --start-retries: retry jobs start when backend returns retryable start responses
• --start-retry-delay-ms: base backoff delay for start retries

Commands

• init
• rent
• worker quote|rent|status|run
• exec
• auth challenge|verify|login
• tos get|accept
• receipts create|get|sync|wait
• sessions quote|rent|extend|get
• tools catalog|available|load
• jobs quote|create|pay|start|get|output|logs
• wallet init|address|balance
• run

Notes

• H1DR4 quote appears only when backend has stable live token price.
• --admin-ip is internal staging/admin only.

Terminal Demo Video

Generate the tutorial videos created in this repo:

npm i -D cli-cinema playwright
npm run video:render

Outputs:

• media/out/h3retik-cloud-startup-main.mp4 (16:9 main cut)
• media/out/h3retik-cloud-startup-vertical.mp4 (9:16 mobile cut)