looot
v1.0.0
Published
looot CLI: connect an AI agent to the looot catalog (discover, inspect, run, and get billed for external capabilities) from the command line.
Maintainers
Readme
looot
One CLI (and MCP server) that connects your AI agent to the looot catalog: discover a capability, inspect its exact input/output schema and price, run it, and get billed only for what actually completed. One balance, no per-provider subscriptions or separate API keys to manage.
Install
npm install -g loootTry it without an account
looot search "find a work email" # browse the public catalog, prices included
looot inspect <endpoint-id>Sign in and connect your agent
looot loginPrints a link and a short code and opens your browser. On looot.ai, check that the code matches,
choose what the token may do and how long it lasts, and approve. The CLI picks up the token by
itself: you never copy a secret. It is saved to ~/.config/looot/config.json (only you can read
it) and listed in Settings, Agent tokens, where you can revoke it. looot logout revokes it and
deletes the file.
looot initDetects Claude Code, Cursor, or Codex on your machine and offers to add the looot MCP server,
referencing $LOOOT_TOKEN instead of writing the secret into their config.
looot init --dry-run shows what it would write. looot mcp install --client <name> prints just
the MCP config.
Everyday commands
looot search "verify an email address" # find endpoints by what you want to do
looot inspect <endpoint-id> # exact input/output schema and price before you run it
looot run <endpoint-id> --input '{"...": "..."}' --wait
looot balance # what's left in your workspace
looot runs list # recent runs, status, cost
looot doctor # is everything set up correctlyEvery command supports --format json|human|jsonl. Piped or redirected output is JSON by
default; on a terminal you get a short human-readable summary.
Full reference
looot help --allSecurity
Your token is never passed as a command-line flag (it would land in shell history). Set it via
looot login, or the LOOOT_TOKEN environment variable. Human-formatted
output redacts secret-looking fields.
