Keys leak — into config files, screenshots, repositories — and a leaked key on a credit-metered render service is someone else's images billed to you. Requiring OAuth means the credential is scoped to a connection you can see and revoke rather than a string that lives forever in a dotfile. The watermark and licensing split is the other thing to check before a client sees anything: the free tier is explicitly personal use, so a render that looks finished may not be one you can deliver.
Visualizee produces architectural renders from sketches and models. The endpoint covers the whole render loop including the account's credit balance.
- upload_image and render_image
- render_video
- get_render to retrieve a result, list_models for what is available
- get_credits for the balance
OAuth only — they do not issue API keys. A credit subscription funds renders; the free tier watermarks output and is personal use only, with the commercial licence and watermark removal starting at the first paid tier.
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen