Authentication

Binboi authenticates CLI and API requests with a Personal Access Token (PAT). The dashboard uses a separate browser session — PATs are only used outside the dashboard.

Token format

binboi_pat_<8 hex>_<36 hex>

A token is exactly 56 characters: the binboi_pat_ prefix (11 chars), an 8-character hex prefix, an underscore, and a 36-character hex secret. The prefix makes tokens easy to scan for in logs and CI secrets.

Example shape:

binboi_pat_7337cc8b_95cc41b4131fad19a68964de9dccdf81ff06

Create a token

1. Sign in at binboi.com.
2. Go to /dashboard/access-tokens.
3. Click Create token, give it a label, and confirm.
4. Copy the token from the modal. It is shown once. Use the Copy button to grab it — there is no way to view the value again.

If you lose a token, revoke it and issue a new one.

Token quotas

PATs count against your plan's active token cap. Revoking a token immediately frees its slot.

| Plan | Active PATs | Reserved tunnels | |---|---|---| | Free | 2 | — | | Pro | 25 | 10 | | Max | 100 | 50 |

The dashboard's Active Credentials card shows current usage. The refresh icon occasionally fails to repaint immediately — reload the page if the number looks stale (known minor UI bug, the backend numbers are correct).

Use a token

CLI

binboi login --token binboi_pat_xxxxxxxx_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

The token is written to ~/.binboi/config.json and used by every subsequent CLI command.

HTTP API

Pass the token in the Authorization header on every request to api.binboi.com:

Authorization: Bearer binboi_pat_xxxxxxxx_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Example:

curl https://api.binboi.com/api/v1/tunnels \
  -H "Authorization: Bearer $BINBOI_AUTH_TOKEN"

Revoke a token

Open /dashboard/access-tokens, find the token, and click Revoke. Revocation is immediate — any CLI or API client using that token will start receiving 401 responses.

A revoked token cannot be reactivated, and its slot stays consumed against your lifetime token quota.