01Run it
Replace the <placeholders> with your own values, or use the builder below.
p202 user get <id>02What 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 user get 1 roles: [{"role_id":1,"role_name":"Super user"}] user_active: 1 user_deleted: 0 user_email: [email protected] user_fname: user_id: 1 user_lname: user_name: demo user_time_register: 1791538968 user_timezone: America/New_York
$ p202 user get 1 --json { "data": { "roles": [ { "role_id": 1, "role_name": "Super user" } ], "user_active": 1, "user_deleted": 0, "user_email": "[email protected]", "user_fname": null, "user_id": 1, "user_lname": null, "user_name": "demo", "user_time_register": 1791538968, "user_timezone": "America/New_York" } }
03Build your command
Pick values and the command line writes itself, quoted and ready to paste.
p202 user getSet flags below; the command updates as you type.
04For agents
Running this from an agent
- Read the same facts as JSON:
p202 commands user get --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 user get",
"use": "get <id>",
"short": "Get a user with roles",
"runnable": true
}