beauty-generation-api

This one is refreshingly explicit about its constraints: it is free, it authenticates with a single BEAUTY_API_KEY, it declares curl as its only binary dependency, and it exposes daily quota management as part of the design rather than hiding it. Generation is fast, in the low single-digit seconds. The narrower fit is that the presets are oriented toward portraits, headshots and character visualisation across nationalities, so it is a poor choice for arbitrary scene generation. The built-in content safety layer also means some prompts will be declined without a retry path, so treat refusals as final.

Use case: Fast, no-cost portrait and character generation where a daily quota is acceptable.

# Using the portrait generation service This skill fronts a hosted portrait generator over a simple request interface. Four things in its contract shape how you should call it: generation is fast, output is filtered by content safety rules, access is key-authenticated, and there is a daily quota attached to the key. ## Design around the quota, not against it The quota is daily, so a batch that exhausts it mid-run leaves you with a partial set and no way to finish until the window rolls over. Because the safety filter can refuse a prompt outright, a refusal should not consume the rest of your batch either: handle per-request failures and continue. ## Parameterise nationality and style The generator advertises a very wide range of nationalities alongside many styles, plus headshot and character-design presets. That breadth is the point for representation work, so treat nationality and style as explicit parameters carried in your own data rather than baked into prompt text, which makes the set reproducible. ```bash # one request per parameter tuple, with the key from the environment curl -sS -X POST "$BEAUTY_BASE/generate" \ -H "Authorization: Bearer $BEAUTY_API_KEY" \ -H "Content-Type: application/json" \ -d '{"nationality":"example","style":"studio-headshot"}' \ -o out.png ``` ## Tips - Track quota consumption per run in your own log; the service will not warn you before the daily cap. - Keep nationality and style as separate fields so a set can be regenerated exactly. - gotcha: a content-safety refusal is a normal response for some prompts, so treat it as a per-item failure and continue the batch rather than aborting. - gotcha: the key is read from the environment; a missing key looks like an authentication error, not a configuration error, so check the variable before debugging the request shape. - Batch slowly enough that a refusal does not cascade into lost work.