Publish from Codex or Claude Code with an API key

You need Codex or Claude Code on your computer and a Blue account. Start with the installation guide if you have not set up a tool.

This is a Blue deployment key, not an OpenAI or Anthropic API key. Your AI subscription and Blue fees are separate. This workflow does not use AI Build generation credits.

1. Build a small quiz

Already made the quiz in the introductory guide? Use that app and prepare to publish. Otherwise:

Create an empty “blue-quiz-demo” folder in Documents.
Open that folder in Codex, or choose Code → Local → Select folder in Claude Code.
Copy the prompt below, paste it into the AI's message box, and send it.

Build the quiz

Design, implement, and test a three-choice study quiz inside the selected folder.
- Use five general-knowledge questions. Show the correct answer and a short explanation, and prevent answering the same question twice.
- Show the final score. Try again must return to question one with a score of zero.
- Use English, support keyboard operation, and make controls easy to tap on a phone.
- Use a single index.html with HTML, CSS, and JavaScript. No external libraries, login, payments, or network requests.
Ask only necessary questions. Report how to run it, what you tested, and what remains untested. Do not publish it yet.

Open the generated index.html in a browser. Try answering, scoring, and restarting. Check that it also works in a narrow window before preparing to publish.

2. Prepare to publish

Have the AI prepare the files and explain key setup first. You do not need to issue a key yet.

Prepare before publishing

Prepare to publish this app with the Blue API.
Read the specification first: https://blue-dev1.sola.inc/support/ai-ready/ai?lang=en
The only deployment destination is https://blue-dev1.sola.inc. Do not publish yet.
- Upload only index.html. Exclude keys, .env files, project notes, Git, and deployment scripts.
- Let the deployment script read BLUE_DEPLOY_KEY from its environment and send it in the X-API-Key header. Never put the value in source, command arguments, chat, or logs.
- Give exact setup steps for this OS and AI environment that keep the key out of visible output and command history. I will enter the value myself.
- Check that the execution process receives the key without displaying it. Do not obtain keys or expand permissions.
- If outbound access is unavailable, stop and explain. Prepare a review of the destination, app name, visibility, and files before publishing.

BLUE_DEPLOY_KEY is the variable name your local deployment script will read; it is not configured automatically. Review permission requests. If your AI environment cannot make external requests, use manual upload.

3. Set up your Blue API key

Open API Keys in the console. Create a Blue account if needed.
Add a memo such as “Quiz deployment”, select the hash option, then create an API key.
Copy the newly issued key into the private setup location your AI described. Enter it yourself—not in the AI's message box.
Ask the AI to confirm its execution process can use the key without displaying the value.

The default expiry is 30 minutes. Issue the key after preparation and do not make it persistent for this exercise. If it expires, issue a new one when needed.

Do not use “Copy AI Template” for this workflow: that existing button includes the key in its text. Keep the deployment key out of Git, upload bundles, app .env files, and Blue's app-runtime Secrets.

4. Publish, then open the URL

Review the destination, app name, and files shown by your AI. If they are correct, send this prompt. Only the sample quiz should be published.

Publish after reviewing

Publish this quiz as a new Blue app using the details we reviewed.
Destination: https://blue-dev1.sola.inc
Visibility: public (noindex)
Use the configured BLUE_DEPLOY_KEY and send only the reviewed index.html.
Report the app ID, public URL, and results of checking the main actions. Do not output the key or authentication headers.
If the response is uncertain, check whether the app was created. Do not resend in a way that creates a duplicate app.

Open the returned URL and test answering, scoring, and restarting again. A URL alone is not the finish line—a working app is.

Noindex asks search engines not to list the page. Anyone with the URL can still view it. Do not publish personal or internal information.

Update the same app

Try changing just the title. The app ID identifies the app you published. Confirm the previous ID and URL so the update does not create another app.

Request a small update

Change the title of the quiz we just published to "Today's five-question quiz".
Keep answering, scoring, and restarting unchanged, and test them.
Destination: https://blue-dev1.sola.inc
Confirm the previous app ID and public URL, and prepare to update that same app. Preserve its current visibility; do not create a new app.
Show the changes and target, then wait for me to say "Update it" before publishing. Stop and tell me if the key has expired or lacks permission.

Review the target and changes, say “Update it”, then check the same URL. Keep a local copy of the working files before updating.

When finished, disable the key in the console and remove your local configuration. You can issue another key when you need to update the app later.

If something stops

Invalid key: check expiry and permissions in the console. Do not paste the value into chat.
No response: check the console for an existing app before retrying. Do not resend blindly.
The app does not work: tell your AI what you did, what you expected, and what happened. Fix the same files that were published.

See AI Ready for specifications and plans for available features and limits.

Next: save data and share it

Build a shared checklist — save, share across browsers, and update →