Autonomous AI research platform for verifiable trend intelligence on 0G.

Langclaw is a wallet-authenticated agent platform: chat, memory, API keys, prepaid usage billing, scheduled automation, and an OpenAI-compatible proxy to 0G Compute Router. Enter one topic and Langclaw turns it into live X, GitHub, Docs, and HackQuest signals through coordinated agents, stores evidence on 0G Storage, and anchors brief hashes on 0G Chain.

Two on-chain contracts on 0G mainnet: LangclawUsageVault (prepaid deposits) and LangclawRegistry (research proof; Solidity artifact: SignalGraphRegistry).

Organization: Langclaw-AI

This workspace can be a monorepo with frontend/, backend/, and contracts/ as sibling folders, or three separate clones from the org above.

Fastest path (no local backend): open the deployed app if your team shared a URL, connect an EVM wallet on 0G mainnet (chain ID 16661), sign the Langclaw login message, open Chat in agent/research mode, and run a short topic (e.g. 0G decentralized storage trends). Watch for 0G Compute, 0G Storage, and 0G Chain badges in the agent trace when those envs are enabled on the server.

5-minute local smoke test

1. curl http://localhost:3001/health → {"ok":true,"service":"signalgraph-backend"} (legacy service name in JSON)
2. Open http://localhost:3000 → connect wallet → sign in
3. Chat or POST /api/discover with a one-line topic (wallet session or Authorization: Bearer lck_live_...)
4. Optional billing: send native 0G to the vault below → POST /api/usage/deposit/verify

Deployed contracts (0G mainnet, chain ID 16661)

Getting 0G tokens

• Native 0G (gas + vault deposits): buy on CEX and withdraw to 0G mainnet, bridge via XSwap, or swap on 0G Hub. See How to get 0G.
• Compute Router billing: create an API key and fund usage at pc.0g.ai (OG_COMPUTE_API_KEY in backend .env).

Minimum vs full local setup

Video walkthrough: DEMO_SCRIPT.md.

Docs: 0G overview · Compute Router · Storage · 0G Chain · Mainnet

Option A — monorepo (this layout)

# 1. Backend
cd backend && cp .env.example .env
# Set SUPABASE_*, LANGCLAW_API_KEY_PEPPER, OG_COMPUTE_API_KEY at minimum
# Optional: LANGCLAW_USAGE_VAULT_ADDRESS=0xd6a6773d653049bc4076aac820f98bd48308596a
npm install
# Apply Supabase migrations (see backend/supabase/migrations)
npm run dev

# 2. Frontend (new terminal)
cd frontend && cp .env.example .env.local
pnpm install && pnpm dev

Option B — three org repos (sibling folders)

git clone https://github.com/Langclaw-AI/backend.git
git clone https://github.com/Langclaw-AI/frontend.git
git clone https://github.com/Langclaw-AI/contracts.git

Then follow the same backend / frontend steps as above.

curl http://localhost:3001/health
# {"ok":true,"service":"signalgraph-backend"}

Open http://localhost:3000. Connect a wallet and sign the Langclaw login message.

User → Frontend (:3000) → Backend API (:3001)
                              ├─ Supabase (sessions, memory, keys, usage ledger)
                              ├─ OpenClaw CLI (Planner, Trend, Evidence, Verifier, Conclusion)
                              ├─ Providers (X/Brave, GitHub, Tavily, HackQuest)
                              ├─ 0G Compute Router (/v1/*)
                              ├─ 0G Storage (evidence bundles)
                              ├─ LangclawRegistry (brief hash)
                              └─ LangclawUsageVault (prepaid 0G deposits)

Entry: runSignalGraphWorkflow(topic) (internal name) → POST /api/discover or /api/discover/stream (NDJSON).

OpenClaw skills: backend/openclaw/skills. Install: OpenClaw docs.

Wallet session — sign:

Login to Langclaw
Address: 0x...
Time: 2026-05-16T12:00:00.000Z

Required for API key management, deposits, withdrawals.

API key — Authorization: Bearer lck_live_... for runtime APIs. Cannot manage keys or withdraw.

Full spec: API_REFERENCE.md.

Deployed (mainnet)

• LangclawUsageVault: 0xd6a6773d653049bc4076aac820f98bd48308596a — ChainScan

Billing flow: user deposits 0G to vault → POST /api/usage/deposit/verify credits off-chain neuron balance → usage charges deduct ledger. Router (OG_COMPUTE_API_KEY) is funded separately on pc.0g.ai.

Withdrawal: backend calls authorizeWithdrawal on vault (TBD: full automation); user calls withdraw(amount).

Deploy vault (if not using the address above):

git clone https://github.com/Langclaw-AI/contracts.git && cd contracts
export LANGCLAW_USAGE_VAULT_OWNER=0x...
export LANGCLAW_USAGE_VAULT_WITHDRAWAL_AUTHORITY=0x...
forge script script/DeployLangclawUsageVault.s.sol:DeployLangclawUsageVaultScript \
  --rpc-url https://evmrpc.0g.ai --broadcast

Deploy registry (in the backend repo):

git clone https://github.com/Langclaw-AI/backend.git && cd backend
npm run deploy:registry

Set LANGCLAW_USAGE_VAULT_ADDRESS and SIGNALGRAPH_REGISTRY_ADDRESS in backend .env.

Smoke tests after deploy

1. GET /health
2. GET /v1/models with API key
3. Wallet connect + chat stream
4. POST /api/discover with short topic
5. Deposit to vault + POST /api/usage/deposit/verify

See env templates: backend, frontend, contracts (see deploy section in contracts README).

• Provider keys, Supabase service role, pepper, and OG_*_PRIVATE_KEY stay on the server only.
• API keys stored as HMAC hashes (LANGCLAW_API_KEY_PEPPER).
• Vault withdrawalAuthority is a hot wallet — use multisig for owner in production.
• Never commit .env files.

Spec for vault requirements: SMART_CONTRACT_TEAM_NOTES.md.

• Node.js 20+, pnpm (frontend), npm (backend)
• Supabase project + applied migrations
• Optional: OpenClaw CLI, Foundry, 0G API keys and funded wallets

• GitHub: https://github.com/Langclaw-AI
• 0G docs: https://docs.0g.ai/
• 0G Compute Router: https://docs.0g.ai/developer-hub/building-on-0g/compute-network/router/overview
• 0G APAC Hackathon: https://www.hackquest.io/hackathons/0G-APAC-Hackathon

TBD