Build
CLI
bound-near verify, cert and mcp: options, output and exit codes.
bound-near ships with @bound/near. Run it with npx @bound/near, or install the package and call bound-near. It needs no key.
Usage
bound-near verify <agent.testnet> [--json] deal or refuse, coverage, confinement
bound-near cert <id> [--json] read one certificate
bound-near mcp MCP server over stdio
Options
--contract <id> Bound contract (default bound-v3.boundproto-nh26.testnet)
--rpc <url> RPC endpoint, repeatable (default https://test.rpc.fastnear.com, https://rpc.testnet.fastnear.com)
--json machine-readable output
-h, --help this help
-v, --version print the version
Exit codes: 0 deal / found, 2 refuse / not found, 1 error.verify
npx @bound/near verify bound-agent2-mwfnc6q8.testnetbound-agent2-mwfnc6q8.testnet: cert 1 Verified | ... | coverage 130 | spent 1 float 9/10 | ...
coverage 130 USDC = reserve 30 + auditor allocation 100 (...)
confinement: confined (1 key(s), no contract code, no global contract)
decision: deal (Verified)It reads the agent's current certificate, prints it on one line, then the coverage split, the confinement check, the settlement if there is one, and the decision. The decision follows the contract's verdict (Verified, not halted, float above 0); confinement is printed beside it for you to weigh.
With --json it prints the whole AgentVerdict from verifyAgent, with bigints as strings.
cert
npx @bound/near cert 0Reads get_cert, prints the one-line summary, coverage, halted and the settlement. --json prints the raw view (or null).
mcp
npx -y @bound/near mcpStarts the MCP server on stdio. stdout carries JSON-RPC only. It runs until stdin closes. See MCP server.
Exit codes
| Code | verify | cert |
|---|---|---|
0 | deal | found |
2 | refuse (no certificate, not Verified, halted or no float) | no such certificate |
1 | error (bad arguments, RPC failure) | error (non-numeric id, RPC failure) |
if npx -y @bound/near verify "$AGENT" > /dev/null; then
echo "serve on credit"
else
echo "refuse or prepay"
fiOptions
--contract <id>points at another Bound deployment, for example a private copy made withpnpm near:demo --fresh.--rpc <url>can repeat (or take a comma-separated list); URLs are tried in order.- Set
BOUND_NEAR_DEBUG=1to see the RPC retry stack traces the CLI hides by default.
From a clone of the repository, pnpm --silent near:verify <agent> runs the same check from source.