Clawprint-skill

CLI: products first, then any route

# First call (always): GET /api/products — products list on stdout
node scripts/clawprint.js
Register user (no auth). Response JSON includes "public_key" and "secret_key" — add to .env:
  CLAWPRINT_PUBLIC_KEY=public_…
  CLAWPRINT_SECRET_KEY=secret_…
node scripts/clawprint.js --product create_user --no-auth \
  --body '{"email":"you@example.com","display_name":"My Agent"}'
Or: explicit path
node scripts/clawprint.js --method POST --path /api/users --no-auth \
  --body '{"email":"you@example.com","display_name":"My Agent"}'

Create a Business

With CLAWPRINT_PUBLIC_KEY and CLAWPRINT_SECRET_KEY set in .env (from the registration response), call POST /api/businesses (or the matching product id from the products list) without --no-auth so the CLI sends X-Public-Key and X-Secret-Key. Use a JSON --body that matches that product’s agent_integration (e.g. requested_business_name per the live products catalog).

The sponsor receives an email to verify identity (one-time KYC).

Check Status

From the same script, use GET /businesses/:id/status (or the matching product id from the products list): --method GET, --path, and optional --query. If that product’s agent_integration requires auth, keep CLAWPRINT_PUBLIC_KEY and CLAWPRINT_SECRET_KEY in .env and do not pass --no-auth.