Agencies, CRMs, Zapier
REST API
Async jobs for virtual staging, interior design, listing tools, batches, and MLS workflow templates. Webhooks with HMAC verification.
API referenceFor builders & autonomous agents
StagePro APIs built for AI agents
Virtual staging, 25+ listing photo tools, batch MLS workflows, and a conversational design agent — exposed for your CRM, your SaaS, or your Cursor/Claude assistant.
25+
Listing photo tools via API
3
Integration surfaces
0
IP allowlists required
Three ways to integrate
REST is the foundation. MCP and the Agent API sit on top for different client types.
Cursor, Claude Desktop
MCP server
Fifteen tools out of the box — create jobs, run batches, chat with the design agent, and poll results. No custom HTTP client code.
Setup guideConversational workflows
Design Agent API
Multi-turn room analysis and design advice (free). Optional render when readyToRender is true. auto_render defaults to false.
Agent endpointsExample: single job
Create a job, poll GET /api/v1/jobs/{id}, or pass webhook_endpoint_id for push delivery.
curl -X POST https://www.stageproai.com/api/v1/jobs \
-H "Authorization: Bearer sk_live_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{
"type": "virtual-stage",
"input": {
"image_url": "https://example.com/living-room.jpg",
"style": "modern",
"room_type": "living-room"
},
"metadata": { "listing_id": "MLS-8842" }
}'Example: Cursor MCP
Build packages/stagepro-mcp, then add to your MCP config. See packages/stagepro-mcp/mcp.example.json.
{
"mcpServers": {
"stagepro": {
"command": "node",
"args": ["./packages/stagepro-mcp/dist/index.js"],
"env": {
"STAGEPRO_API_KEY": "sk_live_YOUR_KEY"
}
}
}
}What agents automate
MLS listing pipeline
Upload 20 photos → batch declutter or virtual stage → webhook on batch.completed → push URLs back to your CRM.
AI assistant in your product
Embed the Design Agent API so users chat about their room, then explicitly confirm a render — credits only when they choose.
Cursor / Claude workflows
Connect the MCP server and ask your agent to stage a listing, enhance twilight exteriors, or run mls-virtual-stage on a folder of images.
Your launch checklist
Complete these once before going live with the developer platform.
- 1
Run database migrations
Apply 016_api_platform.sql → 017_api_jobs.sql → 018_api_batches.sql → 019_api_agent_sessions.sql in Supabase (in order).
- 2
Set server environment variables
PROMPT_LOG_ENCRYPTION_KEY (32-byte base64), CRON_SECRET, OPENROUTER_API_KEY + ARCHITECT_CHAT_MODEL for the agent API. Existing image keys (FAL, etc.) must already work.
- 3
Schedule cron routes
Point Vercel cron (or similar) at /api/cron/purge-prompt-logs and /api/cron/recover-api-jobs with Authorization: Bearer CRON_SECRET.
- 4
Create an API key
Active paid subscription → /developers/console → create sk_live_ key. Use sk_test_ for mock responses without spending credits.
- 5
Optional: MCP locally
cd packages/stagepro-mcp && npm install && npm run build. Add mcp.example.json to Cursor with STAGEPRO_API_KEY.
Platform highlights
Async jobs + batches
2–20 parallel jobs by plan
Verified webhooks
HMAC X-StagePro-Signature
Design agent
Chat free; render on demand
15 MCP tools
Jobs, workflows, agent sessions
Ready to wire up your agent?
Subscribe to any paid plan, create a key in the developer console, and hit the API or MCP server.