canonical: https://jentic.com/apis/metadata.jwplatform.com/jw-platform-metadata # Metadata Jwplatform Media Metadata API The JW Platform Media Metadata API stores extracted metadata about media that has been ingested into the JW Platform. The surface is intentionally narrow: a GET endpoint returns the metadata for a media item and a POST endpoint creates a metadata record. It is designed to sit alongside JW Player's broader ingestion pipeline as a dedicated metadata store, so agents can write extracted attributes once and read them back when serving or analysing the media. ## For AI agents Read and create extracted metadata records for media stored on JW Platform via two REST endpoints. ## Scope Does not handle media upload, transcoding, playback, or analytics - use for reading and writing extracted media metadata records only. ## Capabilities - Read the stored metadata record for a media item ingested into JW Platform - Persist newly extracted metadata for a media item via a POST request - Centralise extracted media attributes alongside the JW Platform ingestion pipeline - Feed downstream players or recommenders with structured metadata for ingested videos ## Use cases ### Centralised Media Metadata Store After a video is ingested into JW Platform and processed by an extraction pipeline (titles, transcripts, thumbnails, technical attributes), the agent persists the extracted attributes via POST /metadata. Downstream players, recommenders, and search indexes then read the same attributes via GET /metadata to keep their views in sync. This gives JW Platform a single source of truth for derived media data. Example prompt: POST /metadata with the extracted attributes for a freshly ingested video and confirm with a follow-up GET /metadata that the record is present ### Pre-Playback Metadata Lookup Before serving a media item to a player, the agent fetches its metadata to drive UI elements like title, description, runtime, and language. Centralising this in the metadata store means the player does not have to re-derive attributes per session, keeping start-up latency low. This is especially relevant for OTT and educational platforms with large back catalogues. Example prompt: GET /metadata for the media ID before constructing the player payload and use the response to populate the UI ### AI Agent Integration via Jentic An AI agent uses Jentic to discover the Media Metadata API by intent search ('store media metadata'). Jentic returns the GET and POST operations with their schemas, so the agent persists or fetches a metadata record without browsing JW Platform docs. Any auth required by your JW Platform account is handled inside your Jentic One instance. Example prompt: Use Jentic to search 'store media metadata', load the POST /metadata schema, and execute it to record the extracted attributes for a new ingestion ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/metadata` | Show media metadata | | POST | `/metadata` | Create media metadata | ## Key resources - **Metadata** — Extracted metadata records associated with ingested media items - read and write ## Why Jentic - **Setup:** Wiring the Media Metadata API by hand means reading and writing metadata records against the JW Platform host and handling request formatting yourself, even though the public spec declares no security scheme. Through Jentic you install once, import the Media Metadata API from the API Directory, store any credential it needs once, and your agent calls it. - **Permission scoping:** This API exposes GET and POST on /metadata, with no resource id in the URL path, so limit the agent to the operations it needs, such as reading metadata records. You choose which operations it may call, so writing new records with a POST is not included unless you add it. - **Credential handling:** Any JW Platform credential required in practice is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'store media metadata' or 'read a metadata record', and Jentic returns the matching GET or POST /metadata operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Mux** — Video infrastructure platform with full ingest, encoding, and metadata APIs - **Cloudinary Upload API** — Media upload and transformation API with rich metadata extraction - **Bunny** — CDN and video stream provider that pairs with metadata stores for delivery ## FAQ ### What authentication does the Media Metadata API use? The OpenAPI spec sourced from SwaggerHub does not declare a security scheme on the operations, but a JW Platform account is required in practice to call the live service. Through Jentic, any required credentials are stored in your Jentic One instance and injected into the request when present. ### Can I read the metadata for a media item I've ingested? Yes. GET /metadata returns the stored metadata record for an ingested media item. Use this to populate player UIs or downstream search and recommendation indexes. ### How do I store extracted metadata for a new video? POST /metadata with the extracted attributes (title, description, runtime, language, and any custom fields) once your ingestion or extraction pipeline has produced them. The record then becomes available to GET on subsequent requests. ### How do I save metadata through Jentic? Search Jentic for `store media metadata`, load the POST /metadata operation, and execute it with the extracted attribute payload. Jentic returns the structured response from the metadata store. ### Is this the same as the JW Player Management API? No. The Media Metadata API is a focused metadata store tied to ingested media. JW Player exposes broader management APIs for media items, channels, and analytics, which are typically used together with this metadata surface. ### Are there published rate limits? The OpenAPI spec does not declare quantitative rate limits. Coordinate with JW Platform support to confirm the limits applied to your account before high-volume ingestion. ### Can I limit what my agent is allowed to do with the JW Platform Media Metadata API? Yes. This API exposes only GET /metadata and POST /metadata, and because you run Jentic One self-hosted, your own rules decide which of those operations the agent may call. You can allow it to read metadata records with GET /metadata while withholding POST /metadata, so it cannot create or overwrite records unless you grant that. Any JW Platform credential the calls need is stored by your own instance and supplied only when an operation you have permitted runs.