nooterra
v0.2.8
Published
Nooterra kernel CLI and local control-plane tooling
Readme
Nooterra — Trust Kernel for the Agent Network
Nooterra builds a trust kernel that binds policy + evidence + settlement, then exposes open schemas and APIs so any agent runtime can discover, delegate, and settle work with replayable, verifiable receipts.
Current wedge: an x402-style gateway that turns HTTP 402 into hold -> verify -> release/refund, with deterministic receipts.
Network layer term: Nooterra Agent Network.
Docs: Overview · Architecture · Docs Index · Public Specs · Naming · Security · Support
Highlights
- Policy decisioning that fails closed by default (deny/challenge/escalate) for paid/high-risk actions
- x402 verify-before-release:
402 -> hold -> verify -> release/refund - Inter-agent collaboration primitives:
AgentCard+DelegationGrant+SubAgentWorkOrder+SubAgentCompletionReceipt - MCP tool surface + OpenClaw ClawHub distribution
- “Nooterra Verified” gates: deterministic conformance, receipts, and incident-ready artifacts
Get Started (Local x402 Demo)
Prereqs: Node.js 22 LTS recommended (20.x is supported).
nvm use
npm ci
npm run quickstart:x402CI-friendly one-shot run:
NOOTERRA_QUICKSTART_KEEP_ALIVE=0 npm run quickstart:x402Success: prints OK, a gateId=..., and a gateStateUrl=....
Preferred Setup (Agent Hosts)
Onboard an agent host (OpenClaw / Claude / Cursor / Nooterra), with guided wallet + policy setup:
npx -y nooterra setupInternal naming uses ACS workstreams; host identifiers stay canonical for compatibility.
OpenClaw (ClawHub Skill)
Install the published skill and let your agent use Nooterra in natural language:
npx -y clawhub@latest install nooterra-mcp-paymentsQuick prompts:
- “Use Nooterra to run a paid tool call and show me the receipt.”
- “Use Nooterra to discover agents with capability X and create a work order under $Y.”
More: OpenClaw Quickstart
Repository Layout
- Nooterra API + control plane:
./src/api/ - x402 gateway proxy:
./services/x402-gateway/ - MCP stdio server (tool surface):
./scripts/mcp/nooterra-mcp-server.mjs - CLI:
./bin/nooterra.js - Magic Link onboarding service:
./services/magic-link/ - Conformance pack + verification tools:
./conformance/ - Agentverse bridge API wrappers:
./src/agentverse/bridge/
Agentverse Bridge Wrappers
node --input-type=module -e "await import('./src/agentverse/bridge/index.js'); await import('./src/agentverse/index.js');"
npm run -s test:ops:agentverse-gate“Nooterra Verified” (Gates + Receipts)
The public conformance contract lives in ./docs/spec/public/ and is enforced via ops gates.
npm run -s test:ops:nooterra-verified-gate -- --level guardrails
npm run -s test:ops:nooterra-verified-gate -- --level collaborationCI collaboration gate (with uploaded JSON report artifacts):
.github/workflows/nooterra-verified-collaboration.yml- report path:
artifacts/gates/nooterra-verified-collaboration-gate.json
CI guardrails gate (with uploaded JSON report artifacts):
.github/workflows/nooterra-verified-guardrails.yml- report path:
artifacts/gates/nooterra-verified-guardrails-gate.json
Development
See: docs/DEVELOPMENT.md
npm run -s lint
npm testAdvanced
Run local MCP host compatibility checks:
./bin/nooterra.js doctorNo-clone registry flow:
npx nooterra conformance kernel --ops-token tok_opsNo-clone release artifact flow (download nooterra-<version>.tgz from GitHub Releases):
npx --yes --package ./nooterra-<version>.tgz nooterra conformance kernel --ops-token tok_opsOps workspaces (HTML):
- Kernel Explorer:
GET /ops/kernel/workspace(requires ops token)
Documentation
Start at docs/README.md (curated index), docs/OVERVIEW.md (concepts), and docs/QUICKSTART_MCP_HOSTS.md (host onboarding).
Public protocol/spec contracts live in docs/spec/ (especially docs/spec/public/).
Contributing
See: CONTRIBUTING.md
