License · Customer documentation

What you prepare

The app whose access you want to license; payment integration is separate.

Steps in the workspace

1. 01Create a license project.
2. 02Issue keys and deliver them securely.
3. 03POST to the validation endpoint from the app.

Example request / integration

Give a desktop app buyer a key and POST it to validation at startup to check revocation/expiry.

# Create a project, then issue a key in the workspace.
curl -X POST "$VALIDATION_URL" \
  -H 'Content-Type: application/json' \
  --data '{"key":"PASTE_ISSUED_LICENSE_KEY"}'
# Inspect valid: true/false, reason, and expiration.

Examples use placeholders: replace $BASE_URL, $SESSION_TOKEN and issued URLs with real values. Never publish session tokens or API keys in a webpage or repository.

Management API entry point

POST /api/picosvc/license/projects

Project name and key labels/expiration.

Keys, a validation URL, and valid:true/false responses.

What it does not do

Does not process payments, enforce machine binding, or provide full offline licensing.

Feature comparison and sources

License identification：Simple key validation with revocation and expiry.

Keygen：Documents validation workflows including optional machine fingerprints.