paybondpaybond
Sign in

Paybond CLI

Safe agent spend from the terminal.

One CLI for login, guardrail scaffolding, MCP setup, diagnostics, and automation. TypeScript and Python share the same command tree, JSON envelopes, and release contract.

Coding-agent setupCLI contract

Terminal-first workflow

Login, scaffold guardrails, wire MCP, and automate with JSON — the same path agents and humans follow in sandbox.

  • Paybond CLI terminal workflow showing login, init guardrail, MCP install, and doctor
    From sandbox login to MCP install in four commands.
  • Paybond CLI command tree with setup, discovery, workflows, and support groups
    One shared command tree across TypeScript and Python.
  • Paybond CLI JSON automation output with structured envelopes for agents
    JSON envelopes for scripts, CI, and agent automation.

Built for agents and operators

The CLI keeps spend guardrails, MCP policy, and diagnostics in one surface — before your workflow calls a paid tool.

  • Sandbox login

    Authenticate once with tenant-scoped credentials before any guardrail or MCP command runs.

  • One-command guardrails

    Scaffold paid-tool guardrails with paybond-init presets that match your framework and output path.

  • MCP install and verify

    Generate host config, verify policy, and keep stdio MCP launch aligned with the coding-agent setup guide.

  • Doctor and diagnostics

    Run doctor-agent and support diagnostics to catch config drift before agents hit production spend paths.

  • JSON automation

    Every command supports machine-readable output with stable envelopes for scripts and CI pipelines.

  • TS and Python parity

    The CLI contract, help text, and exit codes stay synchronized across both Kit packages.

Install once, run anywhere

Use npx for a zero-install path on Node, or install the Python wheel when your runtime is already pip-based.

  • TypeScript (npx)

    npx -p @paybond/kit paybond --help

  • Python

    pip install paybond-kit && paybond --help

CLI FAQ

Runtime choice, command reference, and how the CLI connects to MCP.

Do I need both TypeScript and Python?

No. Pick the runtime your agent or app already uses. Both packages expose the same paybond command tree and JSON contract.

Where is the full command reference?

See the CLI contract doc for flags, subcommands, JSON envelopes, and parity guarantees between TypeScript and Python.

How does this relate to paybond-mcp-server?

The CLI installs and verifies MCP host configuration. The MCP server itself is still launched via npx or your host's stdio config after login.