CODEX API / OPTIONAL

API setup is a different decision.

A theme changes appearance. An API provider changes where model requests go and how usage is billed. DreamSkin Studio keeps those actions separate on purpose.

VERIFIED FIELD GUIDE
macOS · arm64 · build 5307
Reviewed against the pinned upstream build
2026-07-16

Disclosure

DreamSkin Studio is supported by HiAPI.

HiAPI is an optional third-party API service. Using DreamSkin does not require HiAPI, and installing or restoring a theme never changes your provider settings.

01

Two independent workflows

Complete and verify theming before considering any provider configuration. Never approve an install prompt that mixes the two.

Theme workflow

Reviews the upstream theme engine, verifies artwork SHA-256, applies appearance parameters, verifies the renderer, and keeps a Restore path.

API workflow

Reviews a provider's identity, endpoint, pricing, data handling, credentials, supported models, and a reversible configuration change.

02

Before choosing an API provider

Treat provider configuration as a security and billing decision, not as a cosmetic setup step.

Verify the destination

Confirm the exact Base URL, provider ownership, documentation, supported models, and status page.

Protect credentials

Create a dedicated key where possible, keep it out of screenshots and messages, and know how to revoke it.

Understand cost and data handling

Review pricing, retention, privacy, rate limits, refunds, and any regional or account constraints.

Test reversibly

Save the prior provider configuration, make one explicit change, run a small test request, and verify billing before broader use.

03

About the HiAPI link

The link below is a clearly labeled sponsored referral with UTM attribution. It does not install software or change local settings. You may ignore it and use DreamSkin normally.