OpenClaw-only documentation
The OpenClaw skill page for using Pop-cam the right way
This page is written only for OpenClaw. It explains exactly how the OpenClaw skill should guide the user through Pop-cam sign-up, sign-in, token creation, and authenticated usage.
This page is only for OpenClaw users.
OpenClaw users must create a Pop-cam account before using the skill.
After sign-in, create a Pop-cam API token and use it in OpenClaw.
OpenClaw Flow
Watch the handoff step by step
Auto-playing walkthrough
1
Step
Sign Up For Pop-cam
OpenClaw cannot use the Pop-cam skill until the user has a Pop-cam account. The first instruction should always be to create an account if the user does not already have one.
Open https://www.pop-cam.com/sign-up.
Create the account with the user’s preferred email sign-up flow.
Finish any required verification step before moving on.
2
Step
Sign In Before Using The Skill
If the user is not signed in, OpenClaw should stop and prompt them to sign in. Pop-cam token creation and account-linked usage depend on an authenticated session.
Open https://www.pop-cam.com/sign-in.
Wait until the user is signed in successfully.
Do not continue to token creation until sign-in is complete.
3
Step
Generate Your API Token
Once signed in, OpenClaw should direct the user to the Developer Settings page to create a Pop-cam API token. The token is shown once, so the user should save it immediately.
Open https://www.pop-cam.com/developer.
Create a new token with a clear label such as OpenClaw.
Copy the token immediately because the full token is not shown again.
4
Step
Use The Token Inside OpenClaw
The Pop-cam skill should send the user’s token as a Bearer token on authenticated requests. Each authenticated generation uses the user’s Pop-cam credits.
Send Authorization: Bearer pk_... on Pop-cam API requests.
Use the token only for the signed-in user who created it.
If the token fails, ask the user to revoke it and generate a new one.
Skill Instructions
Use these exact instructions inside OpenClaw
If you want OpenClaw to behave correctly with Pop-cam, it should follow this sequence every time. The goal is to keep onboarding obvious and to prevent requests from failing because the user skipped account setup.
1
Tell the user to sign up for Pop-cam first if they do not already have an account.
2
Require the user to sign in before creating or using a Pop-cam token.
3
Send the user to Developer Settings to generate a token named for the OpenClaw workflow.
4
Store and use the returned token as Authorization: Bearer pk_....
5
If OpenClaw is unsure about auth state, call the OpenClaw auth-status endpoint first and follow its message.
Nano Banana Visual Guide
See the OpenClaw workflow as a picture-first walkthrough
These Nano Banana-generated drawings are arranged in the same order OpenClaw should follow. They reinforce the three moments that matter most: sign up, sign in and generate the token, then use that token on authenticated Pop-cam requests.
1. Sign up first
OpenClaw should start by sending the user to Pop-cam sign-up when no account exists yet.
2. Sign in and create a token
After sign-in, OpenClaw should direct the user to Developer Settings and wait for token creation.
3. Use the token for requests
Every authenticated OpenClaw request should use the user’s Pop-cam token as a Bearer token.
Step-By-Step
What the OpenClaw skill should do
Each step below is explicit on purpose. OpenClaw should not skip ahead, should not try to create a token before the user is signed in, and should always treat account creation as the first requirement.
1
Sign Up For Pop-cam
OpenClaw cannot use the Pop-cam skill until the user has a Pop-cam account. The first instruction should always be to create an account if the user does not already have one.
Open https://www.pop-cam.com/sign-up.
Create the account with the user’s preferred email sign-up flow.
Finish any required verification step before moving on.
2
Sign In Before Using The Skill
If the user is not signed in, OpenClaw should stop and prompt them to sign in. Pop-cam token creation and account-linked usage depend on an authenticated session.
Open https://www.pop-cam.com/sign-in.
Wait until the user is signed in successfully.
Do not continue to token creation until sign-in is complete.
3
Generate Your API Token
Once signed in, OpenClaw should direct the user to the Developer Settings page to create a Pop-cam API token. The token is shown once, so the user should save it immediately.
Open https://www.pop-cam.com/developer.
Create a new token with a clear label such as OpenClaw.
Copy the token immediately because the full token is not shown again.
4
Use The Token Inside OpenClaw
The Pop-cam skill should send the user’s token as a Bearer token on authenticated requests. Each authenticated generation uses the user’s Pop-cam credits.
Send Authorization: Bearer pk_... on Pop-cam API requests.
Use the token only for the signed-in user who created it.
If the token fails, ask the user to revoke it and generate a new one.
Sign-In Prompt API
The endpoint OpenClaw should query before moving ahead
OpenClaw can call the auth-status endpoint before asking for token-based actions. If the response says sign-in is required, OpenClaw should stop and show that instruction to the user instead of continuing.
Check whether the user must sign in
bash
curl https://www.pop-cam.com/api/openclaw/auth-statusUse the Pop-cam token from OpenClaw
bash
curl -X POST https://www.pop-cam.com/api/v1/nanobanana \
-H "Authorization: Bearer pk_YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"image": "data:image/png;base64,iVBOR...",
"prompt": "Create a clean Nano Banana illustration"
}'Response when the user still needs to sign in
json
{
"authenticated": false,
"requiresSignIn": true,
"message": "Sign in to your Pop-cam account before using OpenClaw with Pop-cam.",
"signInUrl": "https://www.pop-cam.com/sign-in",
"signUpUrl": "https://www.pop-cam.com/sign-up"
}