Agent-native Signup

An AI agent can start integrating Guapocado without waiting for you to create an account or paste an API key into its environment.

Create a claimable workspace

From the project the agent is configuring:

npx guap signup --agent --agent-name codex --name "Acme billing" --json

The command:

1. Creates a provisional Guapocado tenant with a test environment.
2. Stores a restricted bootstrap key in .guapocado/credentials.json.
3. Prints a claim URL, workspace ID, and expiry without printing the key.

The agent can then create and push the billing configuration:

npx guap init
npx guap push --test

Claim the workspace

Open the returned claimUrl, sign in or create an approved Guapocado account, review the workspace, and confirm the claim.

Claiming preserves the existing test TenantCell and configuration. It creates the workspace organization around the same tenant ID and provisions a separate live environment; no test data is copied or reset.

Bootstrap-key restrictions

Before and after claim, the agent bootstrap credential:

• can only use the test environment;
• can push and pull billing configuration;
• cannot create keys;
• cannot access customers, usage, checkout, Stripe, or live mode;
• expires after seven days if the workspace is not claimed.

The owner can later use guap login to authorize normal test and live credentials.

Credential handling

The CLI writes .guapocado/credentials.json with owner-only permissions on POSIX systems. Keep .guapocado/ in .gitignore. The --json response intentionally contains no API key.

If the connection drops after the server creates the workspace, rerun the same command. The CLI keeps a high-entropy retry handle locally so the API returns the same provisional registration instead of creating a duplicate.