Hello,
Yes, for a volume like 120,000 images per month, it would make sense to contact the PixLab team for a custom plan or enterprise pricing, especially if the workload is recurring and fully automated.
For the technical side of the integration, POST multipart/form-data directly from your Python cron job would usually be the preferred option unless you specifically need base64 for an existing pipeline.
A few reasons:
- multipart/form-data is more efficient because you avoid the size overhead of base64 encoding
- it is generally better for large-scale batch uploads
- it keeps the Python workflow simpler when reading files directly from disk
- it is usually easier to debug and monitor in scheduled jobs
Base64 can still be useful if:
- your images are already stored in base64 format
- you are passing image data through JSON-only systems
- your pipeline does not easily handle file uploads
But for a periodic Python cron job processing large volumes, multipart/form-data is typically the cleaner and more scalable approach.
For the white background requirement, that is also a common post-processing workflow after background removal, so it would be good to mention explicitly that you need:
- background removed
- output composited onto a solid white background
- batch volume of 120,000 images/month
That gives support enough context to recommend the right plan and workflow.
You can likely get the fastest answer by contacting them with:
- monthly volume
- average image size
- expected request rate
- whether processing is real-time or batch
- desired output format
- whether you need SLA or dedicated support
Docs: https://pixlab.io/endpoints/background-remove-api
