ACC Site Builder

Optional — for a real/flagship brand. Answer what you can; the Brand step turns it into a bespoke identity (name · slogan · color psychology · logo · voice · type). Skip it for anti-footprint rank-and-rent sites.

Stored server-side for your account, sent over HTTPS, never shown back. 📖 How to get & secure these keys →

BYOK — you bring your own keys and control the spend. Use dedicated, least-privilege keys so the builder can only do what it needs.

1 · OpenRouter — content & keywords (any model, one key)

1. Go to openrouter.ai → sign in → Keys → Create Key. Name it "ACC Site Builder".
2. Add credits and set a monthly limit so spend is capped.
3. Paste it into OpenRouter API key. Pick a model (Claude/GPT/Gemini — your call).

2 · kie.ai — logo & images

1. kie.ai → sign in → API Keys → create one; add credits.
2. Paste it into kie.ai API key.

3 · AWS — deploy to S3 (use a dedicated S3-only key, never root/admin)

1. AWS Console → IAM → Users → Create user (e.g. acc-site-builder).
2. Attach the policy AmazonS3FullAccess (or a single-bucket policy for tighter scope).
3. Open the user → Security credentials → Create access key → "Application running outside AWS".
4. Copy the Access key + Secret (the secret is shown once) → paste both + region (us-east-2).

🔒 Security best practices

• Least privilege: the AWS key should have S3 only — never reuse your root/admin keys.
• Spend caps: set monthly limits on OpenRouter/kie so a runaway can't drain your account.
• Storage: keys are stored server-side for your account, sent over HTTPS, and never shown back in this UI.
• Rotate: rotate keys periodically; if one leaks, revoke it in that service and create a new one.
• Never paste keys into chats, screenshots, or shared docs.
• BYOK isolation: your keys are yours — never shared with other accounts.