Use the public SaveMedia endpoints to preview supported media, request download links, and proxy file downloads. The API reference below documents the wrapper routes your clients should depend on, while backend processing stays private behind the scenes.
These endpoints are the stable SaveMedia contract. Clients should integrate with SaveMedia routes and not depend on private backend implementation details.
The public wrapper routes currently do not require client auth. Private service-to-service credentials are handled on the backend when needed.
The web app and media processing service can run as separate Cloud Run services so UI traffic and heavier processing workloads scale independently.