Tools for AI agents at capcli.com

CAP CLI

CAP CLI helps AI agents use real tools without guessing commands or exposing secrets. Describe the job, see what the tool needs, approve the important steps, and let the agent run it in a controlled local setup.

Try CAP CLI See An Example Read the Docs View Tool List Example tool: lightningnode/voltage-sandbox
cap resolve 
$ cap resolve "set up a new lightning testnet node" --json
{
  "rank": 1,
  "package": "lightningnode/voltage-sandbox",
  "best_for": "create a Voltage MutinyNet Lightning node",
  "review": {
    "tier": "verified-runtime",
    "risk": "medium"
  },
  "policy_profile": "balanced",
  "try": "allowed",
  "install": "requires-approval",
  "safeTrials": [
    "voltage-sandbox brief --json",
    "voltage-sandbox doctor --json"
  ]
}
Ask in plain English Tell the agent the result you want, not the tool name to use.
Know what will happen CAP shows who made the tool, what it can access, and what it will try first.
Stay in control Safe checks can run first. Installs and live actions ask before they continue.

Start With Your Favorite AI Agent

Paste these prompts into a local coding agent that can run terminal commands, such as Codex, Claude Code, Cursor, or Windsurf. The first prompt installs CAP CLI. The second is a real task you can run after CAP is connected.

1. Install CAP CLI 
Install CAP CLI from https://capcli.com/. Make sure the cap command works in this terminal. Then connect CAP to this agent: use cap setup codex for Codex, or cap setup claude for Claude Code. If the installer prints a NEXT command, run that exact command before continuing.
2. Ask for a Lightning sandbox 
Use CAP to help me create a new MutinyNet Lightning node on Voltage. Do not ask me to paste API keys, passwords, macaroons, or seed phrases into chat. Use the local voltage-sandbox credential prompts, and ask me before creating the node, adding funds, or running payment tests.

Run CAP CLI Yourself

Use these commands if you prefer to see each step yourself. The installer places the CAP command in ~/.cap/bin.

1. Install CAP and load it in this terminal 
curl -fsSL https://capcli.com/install.sh | sh && export PATH="$HOME/.cap/bin:$PATH" && cap doctor
2. Set up Codex integration 
cap setup codex
3. Set up Claude Code integration 
cap setup claude
4. Find the Lightning sandbox tool 
cap resolve "set up a new lightning testnet node" --json
5. See safety details 
cap info lightningnode/voltage-sandbox --json
Find CAP looks for the best tool for the job you described.
Try CAP can run declared safe checks before the tool is installed permanently.
Install CAP asks before pinning the tool or running actions that change real state.

Example: Set Up a Lightning Sandbox

After you paste the Lightning sandbox prompt above, CAP gives the agent a safer path through the task. It resolves the request to lightningnode/voltage-sandbox, shows the review record, runs safe checks first, and asks before setup changes anything live.

cap resolve "set up a new lightning testnet node" --json
cap info lightningnode/voltage-sandbox --json
cap try lightningnode/voltage-sandbox --json
cap add lightningnode/voltage-sandbox
cap run lightningnode/voltage-sandbox -- brief --json
cap run lightningnode/voltage-sandbox -- doctor --json
cap run lightningnode/voltage-sandbox -- credentials --gui
cap run lightningnode/voltage-sandbox -- report --json

From request to tool

You describe the goal. CAP matches it to the Voltage sandbox tool before the agent installs anything.

Try safe checks first

The agent can run read-only checks like brief and doctor before taking bigger steps.

You approve live actions

Creating a node, adding funds, and running payment tests only happen after local prompts or your approval.

How CAP Works

CAP gives agents a predictable path from a plain-English request to a real tool run. The agent can discover the right package, try low-risk checks, install after approval, and then run through local policy.

01 Ask plain request Describe the outcome you want, not the package or command.
02 Find cap resolve CAP matches the request to reviewed package candidates.
03 Try cap try Safe smoke checks run in a temporary environment.
04 Install cap add The package is pinned only after policy and approval checks.
05 Run cap run The agent executes through CAP with local prompts for live changes.

Trial checkpoint

Why cap try sits before install

cap try is the low-commitment safety and fit check between inspection and install. It lets an agent prove that a candidate package can install in a temporary environment and run its declared safe path before CAP pins it to your project or global tool store.

Temporary by design Trials run in an isolated CAP home instead of becoming a real project install.
Declared safe commands only Packages choose smoke tests such as --help, doctor --json, brief --json, or dry-run commands.
Secrets stay out CAP strips common host secrets from the trial environment and avoids credential-entry commands.
Built for scale When the registry has millions of packages, agents need a standard smoke-test step before installing one.
Typical path 
cap resolve "set up a new lightning testnet node" --json
cap info lightningnode/voltage-sandbox --json
cap try lightningnode/voltage-sandbox --json
cap add lightningnode/voltage-sandbox --yes
No node created No funds moved No secrets entered No package pinned

For voltage-sandbox, the try step can run brief --json, doctor --json, and credentials --check --json.

Safety Model

How CAP Keeps You In Control

CAP keeps agent tool use understandable: inspect the package, try only the safe path it declares, and stop before anything persistent or live happens.

Package facts Before a tool runs, CAP shows who published it, what it is for, and what commands it exposes.
Temporary trials cap try runs declared smoke checks in a temporary CAP home, without pinning the package.
Approval stops Installs, credential entry, resource creation, funding, and payment tests stop before they change real state.
Secrets stay local API keys, passwords, macaroons, and seed phrases go through local prompts instead of chat.

The Rule Is Simple

CAP separates low-risk discovery from actions that change your machine, secrets, or live accounts.

Find and explain The agent can search the registry and show what a package is for before anything is installed.
Try without commitment Declared safe checks run in a temporary environment. They do not install the package or ask for secrets.
Pause for real changes Installing tools, entering credentials, creating resources, funding accounts, and payment tests stop for local approval.
Lightning sandbox example

CAP can run brief and doctor first. Creating the node, entering Voltage credentials, adding funds, or running a payment test stops for you.

Developer Resources

Start with the registry for package discovery, then use the HTTP endpoints for integrations and the docs for command behavior.

Registry

Package Index

Static JSON for clients that want the full package catalog.

GET/registry/packages.json
Open registry JSON
Discovery API

Search Packages

Query packages by task, name, keyword, or capability text.

GET/api/search?q=voltage
Try search
Packages API

List Packages

Fetch the normalized package list exposed by the hosted API.

GET/api/packages
Open package list
Packages API

Package Detail

Fetch one package record with review, policy, and install metadata.

GET/api/package?id=lightningnode/voltage-sandbox
Open package detail
Documentation

Command Reference

Review commands, options, recipes, and project files.

DOCS/docs.html
Read command guide
Publisher Docs

Publisher Workflow

Create a manifest, run preflight checks, and publish into a local registry.

DOCS/publisher-workflow.html
Read publisher guide
Package Docs

Voltage Sandbox

Read the package runbook for the Lightning sandbox workflow.

DOCS/docs/voltage-sandbox-cli.md
Open package docs
CLI

Public Runtime

Download the browser-served CLI bundle used by the installer.

GET/cli/cap.js
View CLI bundle

Uninstall

Remove CAP from this machine, including its local files, shell setup, and agent connections.

cap uninstall