Media and assets API for uploads, transforms, and delivery URLs

ChefSphere media and assets APIs cover uploads, transforms, private and public assets, and delivery URLs so images and files are not an afterthought duct-taped to object storage. Listings, social posts, publishing covers, and live thumbnails all need a coherent asset pipeline with access control your product can explain. This module is about durable media handling—not live session lifecycle and not social graph semantics, even when those features consume assets.

Keeping media intent distinct helps teams avoid inventing a second CDN strategy for every feature squad racing toward the same launch date. It also clarifies prepaid planning: media uploads sit above simple catalog reads on the token-weight table because storage and transforms cost real money. One shared balance still funds media alongside commerce and AI, which is the point of prepaid packs starting at $29 for 200,000 tokens.

Uploads need clear ownership, size limits, and virus or abuse posture that matches your moderation policy before public discovery is enabled. Transforms should produce the derivatives your clients actually render—thumbnails, cover crops, and delivery-friendly formats—without inventing a custom image factory per screen. Private versus public assets matter for recipes behind paywalls, KYC documents, and household plans that must not leak via a guessable URL.

Media upload weight is published on the pricing page so you can model creator-heavy apps honestly instead of pretending every photo is free infrastructure. If your feed is image-first, budget media alongside social writes rather than discovering burn after a launch campaign floods uploads. Growth and Scale packs exist when media coincides with live recordings, AI vision inputs, or marketplace listing photography at volume.

Pair media with social and publishing when UGC or covers dominate, and pair with seller KYC when documents must stay private with strict access rules. Pair with AI vision when uploads become model inputs, remembering vision turns burn more tokens than the upload itself on the published table. Early access onboarding is where we align which asset classes are public on day one of your pilot.

Authenticate with an X-API-Key in the Firebase-style model and burn prepaid tokens per call on one ledger across nineteen modules. Unused tokens remain on your balance when upload volume dips between campaigns, which is normal for seasonal food products. request access and we contact you when onboarding opens.

Illustrative OpenAPI samples help you plan upload flows and delivery URL usage without treating fictional sample paths as production contracts forever. Production environments arrive with access so clients integrate against the real surface for private and public assets. Enterprise from $300 per month is available for dedicated limits when media-heavy workloads need custom weight conversations.

Decide aspect ratios, max sizes, and retention rules before marketers promise unlimited 4K uploads your prepaid budget and support team cannot absorb. Those constraints are product decisions, not afterthoughts for the week after app store screenshots go live with polished photography. A clear asset policy prevents the classic failure where every squad invents a slightly different upload path and none of them delete orphans.

Related guides on social feed, digital publishing, and AI vision show how media plugs into engagement, commerce of content, and vision turns. Request early access with expected monthly upload volume and whether private assets are required for KYC or paid content. We will email when keys and packs are available for your use case.