01Run it
Straight from the command's own help.
p202 system isp-lookup show --json02What you get
Captured from the real binary, run against a demo store with 30 days of traffic. Switch tabs to see the same run as JSON, the shape scripts and agents parse.
$ p202 system isp-lookup show database_dir: /var/www/prosper202/202-config/geo database_file: enabled: false takes_effect: within five minutes on live traffic
$ p202 system isp-lookup show --json { "data": { "database_dir": "/var/www/prosper202/202-config/geo", "database_file": null, "enabled": false, "takes_effect": "within five minutes on live traffic" } }
03Build your command
Pick values and the command line writes itself, quoted and ready to paste.
p202 system isp-lookup showSet flags below; the command updates as you type.
04For agents
Running this from an agent
- Read the same facts as JSON:
p202 commands system isp-lookup show --json. - With
AI_AGENT,CLAUDECODEor another agent variable set, output is compact JSON and errors arrive on stderr as a JSON envelope with ahint. - Exit codes: 0 ok, 1 bad input, 2 auth, 3 network, 4 server error, 5 partial failure.
{
"path": "p202 system isp-lookup show",
"use": "show",
"short": "Whether ISP lookup is on, and whether the ISP database it needs is in place",
"runnable": true,
"example": "p202 system isp-lookup show --json"
}