Developers
Hydrilla REST API
Run BlueFox, Hydrilla's 3D model, from your own code. The REST API uses the same AI 3D generation as the Hydrilla AI workspace, for asset pipelines, engines, and internal tools.
curl -X POST https://api.hydrilla.co/v1/3d/text-to-3d \
-H "Authorization: Bearer hyd_live_your_api_key_here" \
-H "Content-Type: application/json" \
-d '{
"prompt": "Futuristic cyberpunk vehicle, high details, game ready prop",
"resolution": 1536
}'{
"id": "job_c18ab44d03e192a40",
"status": "queued",
"resolution": 1536,
"links": {
"poll": "https://api.hydrilla.co/v1/3d/tasks/job_c18ab44d03e192a40"
}
}The API is for teams that want generation to happen where their work already lives: an asset library that fills itself from a request queue, a review tool that creates stand-ins on demand, or a build step that produces placeholder props for a new level.
Submit, poll, download
Submit a job, poll its status, then download the mesh and maps. Each job moves from queued to processing and ends completed or failed, so your pipeline always knows where a request stands and can retry the ones that fail.
Because jobs run asynchronously, a single script can submit a batch, carry on with other work, and collect finished models as they complete. Nothing in your pipeline has to wait on one request.
What you can send and get back
Requests mirror the two ways to start in the workspace, and results come back in the same structure an artist would see in the preview.
You send
- A text prompt describing the asset and its use
- Or a reference image to follow
- Your API key with every request
You get back
- A job ID and its current status
- A mesh in parts, with UVs and texture maps
- Files in any of Hydrilla's export formats
Access and authentication
Create a key in your account and keep it server-side, never in a client app or a public repository. Plan access is listed on pricing, and higher volume runs through Enterprise. Building for an AI agent? Use the MCP server, which calls this API on the agent's behalf.