SSigillum DocsOpen dashboard

Persona

AI-Native Indie Builder

Use this guide if you want Sigillum from your own computer through the hosted CLI. It is the simplest path for a solo builder who wants proof before merging or deploying risky code.

Before you start

You do not need to run the Sigillum web app locally for this path. You will call the hosted Sigillum service from your own terminal.

  • You need Node.js installed on your computer.
  • You need a git repository with changes you want to inspect.
  • You can request a quote without payment credentials.
  • You need buyer-side x402 payment credentials before running `inspect`.

Step 1: Install the Sigillum CLI

Install the hosted Sigillum CLI in the repository where you want to use it before running the quote and inspect commands below.

Install the CLI
npm i @usesigillum/cli

Step 2: Ask Sigillum for a quote

Open the repository you want to inspect in your terminal. Run the quote command first. This lets you see the price before spending money.

Quote your current git diff
npx @usesigillum/cli quote --git-diff
Quote a saved diff file
npx @usesigillum/cli quote ./my-change.diff

Step 3: Add the payment environment variables

Create a `.env` file in the repository where you are running the CLI, or set these values in your terminal session before calling `inspect`.

Minimum live inspect env
SIGILLUM_BASE_URL=https://usesigillum.vercel.app
X402_BUYER_PRIVATE_KEY=your_buyer_private_key
X402_RPC_URL=https://rpc.testnet.arc.network
X402_NETWORK=arcTestnet

Step 4: Run the paid inspect

Now that you know the quote and have your payment env ready, run `inspect`. Sigillum will go through quote, HTTP 402, x402 payment, inspect, receipt, and decision.

Inspect current git diff
npx @usesigillum/cli inspect --git-diff
Save the receipt to a file too
npx @usesigillum/cli inspect --git-diff --save-receipt ./sigillum-receipt.json

Step 5: Read the result

A successful inspect prints the proof values you care about. Those values tell you whether to continue, pause, or block your next action.

  • receipt_id
  • receipt_url
  • recommendation
  • risk_score
  • agent_decision
  • payment_reference

Common beginner problems

If quote works but inspect fails, the most common cause is that the buyer-side payment setup is incomplete. That usually means the private key is missing, the RPC URL is wrong, or the Gateway balance is not ready yet.

Related

CLI reference