GitHub publish (optional)

Publish your worlds to a public GitHub repo so you can share them via 360world.yoandev.co/u/<you>.

1. Create a new GitHub repo named 360world-data, set it to Public, and tick "Add a README file" so the repo has an initial commit (otherwise the first publish starts from a blank branch).
2. Generate a Fine-grained PAT — under Repository access pick Only select repositories and choose 360world-data. Under Permissions → Repository, grant Contents: Read and write.
3. Paste your GitHub username and the PAT below, then hit Test & save. The token stays in this browser (IndexedDB) — it never leaves your machine.

Replicate

Routed through a CORS proxy (Netlify function). Get a key at replicate.com/account/api-tokens.

Backup / restore

Your settings live in the browser's IndexedDB, which is scoped to the origin (domain + port). Switching between netlify.app and your custom domain, or visiting a deploy preview, means a different storage. Export a JSON file here to move your keys and GitHub config across browsers, devices or origins.

⚠ The export contains your API keys in clear text. Treat the file like a password — don't commit it, don't email it, don't drop it in a shared folder.