# Get Media by ID

> Get Media by ID is a paid API for AI agents from agents.vimmerse.net, paid per call via MPP, price unknown, status unknown (last checked 2026-10-31).

Retrieves a single media object by its unique ID, optionally filtered to specific fields.

## Facts

- Endpoint: GET https://agents.vimmerse.net/v2/media/{media_id}?utm_source=zero.xyz
- Price: price unknown
- Payment: MPP
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Provider: agents.vimmerse.net
- Website: https://agents.vimmerse.net
- Canonical page: https://www.zero.xyz/c/agents-vimmerse-net-get-media-by-id-5d9b0ec8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__QN0Bmmh69xdHLxNza9iy

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability agents-vimmerse-net-get-media-by-id-5d9b0ec8
```

Example prompt: Check the current processing status and progress percentage of my Vimmerse media job with ID abc123-def456-ghi789.

## When to prefer this

Use this endpoint when you need to check the status or details of a previously submitted media job on Vimmerse — especially for polling async jobs (video, audio, story, workflow) to see if they have completed. Prefer it over listing endpoints when you already have the media_id and want targeted, lightweight lookups using the `fields` parameter.

## Known failure modes

- Invalid or unknown media_id returns a 404 not found error
- Requesting an invalid field name in `fields` may return an error or be silently ignored
- Authentication or payment failure returns 402 or 401
- Network timeout if the service is under load
- Empty response if media was deleted or expired

## How this service works

Retrieves a single media object by ID. Response is **application/json** with the same fields shown in the example above.

Use the optional `fields` query parameter to request only specific keys (allowed keys are those in the media response body). When omitted, the full media object is returned.

## Output

A JSON object representing the media record, including fields such as title, description, processing_status, progress_percentage, and result URLs. When the `fields` parameter is specified, only the requested subset of keys is returned; otherwise the full media object is returned.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "media_id"
 ],
 "properties": {
  "fields": {
   "type": "string",
   "title": "Field Selection",
   "default": "",
   "description": "Comma-separated list of specific fields to retrieve from the media object. Example: 'title,description,processing_status,progress_percentage'. If not provided, all fields are returned. Useful for reducing response size when only specific information is needed."
  },
  "media_id": {
   "type": "string",
   "title": "Media ID",
   "examples": [
    "abc123-def456-ghi789"
   ],
   "description": "Unique identifier of the media"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agents-vimmerse-net-get-media-by-id-5d9b0ec8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agents.vimmerse.net](https://www.zero.xyz/host/agents.vimmerse.net/llms.txt)