What problem does it solve? When building a file-upload feature in your own product (browser or server code), you need to know how to push bytes to Weegloo, receive a temporary Upload resource, and then attach it to a Media or WebHosting entity. This Skill documents that exact two-step REST flow, including authentication, plane selection, and plan-based size limits, so you avoid wiring your app to the wrong endpoint or the wrong MCP tool. ## Core Features & Use Cases - Two-step upload pattern: POST bytes to upload.weegloo.com (multipart or binary), receive an Upload resource with sys.id and sys.expiresAt, then create a Media (CMA or ACMA) or WebHosting referencing that Upload before it expires. - Identity-based plane selection: Weegloo User tokens create Media via the CMA plane; Service User tokens must use the ACMA plane, with the Upload API as the single shared surface. - Plan size-limit handling: Enforced server-side mid-stream with HTTP 429 and error code WGL429004, requiring client-side pre-validation and tailored user messaging (no plan-upgrade wording for Service Users). - Use Case: You are adding an avatar-upload feature to your SaaS app. Your frontend POSTs the image to the multipart endpoint, then your backend creates an ACMA Media referencing the returned Upload.sys.id, waiting for Published status before linking it to Content. ## Quick Start Use the weegloo-upload-api skill to implement a file upload in my app that posts an image to the Weegloo Upload API and creates a Media from the returned upload id.
