render_imageLABSCO SUMMARY
No API keys at all is an unusual stance, and it is the safer one.
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.
What it is
Visualizee produces architectural renders from sketches and models. The endpoint covers the whole render loop including the account's credit balance.
What you get
- upload_image and render_image
- render_video
- get_render to retrieve a result, list_models for what is available
- get_credits for the balance
Requirements
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.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Rendering a sketch
Upload it, choose a model, render.
02
Producing a walkthrough
A video render rather than a still.
03
Knowing what it costs
Check credits before a batch, not after.
6 tools
Listed in project docs. Your client may show a different list.
upload_imagerender_videoget_renderlist_modelsget_creditsBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
- an MCP client that can reach a remote endpoint
- OAuth 2.1 — no API keys at all
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://visualizee.app/api/mcpRequirements
- OAuth 2.1 — no API keys at all
