Automate photogrammetry processing with PIX4Dengine Cloud API
domain: developer.pix4d.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain a PIX4Dengine Cloud license and authentication token to access the API
Create a new project via the REST API and retrieve the temporary AWS S3 credentials it returns
Upload source imagery to the provided S3 location using those temporary credentials
Trigger processing on the project, optionally tagging it (e.g., a 'vegetation' tag for low-texture, flat-terrain pipelines) to select the appropriate processing profile
Poll project/task status until processing completes, then download output products (orthomosaic, point cloud, DSM/DTM) via the API
Known gotchas
Upload credentials are temporary S3 tokens tied to the specific project — they expire and must be refreshed rather than cached long-term
The Cloud API (hosted, S3-based) and the on-premise Pix4Dengine SDK (Python-based) are distinct products with different setup and licensing — instructions for one do not carry over to the other
Selecting the wrong processing tag/profile for the terrain type (e.g., omitting 'vegetation' on low-texture sites) can produce poor reconstructions without an explicit error
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?