# PixVerse 4K Video Upscale

PixVerse 4K Video Upscale sharpens existing footage to crisp 4K resolution, adding clarity and fine detail. Ideal for polishing AI-generated video clips.

## API Information

- **Model Slug:** pixverse-4k-video-upscale
- **Branded URL:** https://www.eachlabs.ai/pixverse/pixverse-features/pixverse-4k-video-upscale
- **Provider:** PixVerse
- **Category:** Video to Video
- **Output Type:** video
- **Status:** active
- **Version:** 0.0.1
- **Base Cost:** PixVerse 4K Video Upscale. Pricing is based on provider-returned Resp.credits because PixVerse does not publish a separate upscale pricing table. $1 = 200 credits.
- **Estimated Processing Time:** 60 seconds
- **Last Updated:** 2026-06-17
- **Interactive Demo:** https://www.eachlabs.ai/ai-models/pixverse-4k-video-upscale

## Pricing

- **Charge Type:** dynamic
- **Pricing Details:** PixVerse 4K Video Upscale. Pricing is based on provider-returned Resp.credits because PixVerse does not publish a separate upscale pricing table. $1 = 200 credits.

### Pricing Rules

| Condition | Pricing |
| --- | --- |
| Rule 1 | PixVerse 4K Video Upscale. Pricing is based on provider-returned Resp.credits because PixVerse does not publish a separate upscale pricing table. $1 = 200 credits. |

## Input Schema

No input parameters documented.

## Example Request

```bash
curl -X POST https://api.eachlabs.ai/v1/prediction/ \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "model": "pixverse-4k-video-upscale",
  "input": {}
}'
```

## Output Schema

Response returned by `GET /v1/prediction/{id}` when the job completes:

```json
{
  "status": "success",
  "predictionID": "string",
  "output": "string (URL of generated video)",
  "metrics": {
    "predict_time": "number (seconds)"
  }
}
```

## Polling

```bash
curl https://api.eachlabs.ai/v1/prediction/{PREDICTION_ID} \
  -H "X-API-Key: YOUR_API_KEY"
```

| Status | Meaning |
|--------|---------|
| `processing` | Still running — poll again |
| `success` | Done — read `output` |
| `error` | Failed — read `message` / `details` |

## Webhook (alternative to polling)

Pass `"webhook_url": "https://your.host/path"` in the create request. Eachlabs POSTs this payload when the job ends:

```json
{
  "exec_id": "prediction-uuid",
  "status": "succeeded",
  "output": "https://...",
  "error": ""
}
```

`status` is `"succeeded"` or `"failed"`. `exec_id` equals the `predictionID` from create. Return 2xx within 30 seconds.

## Errors

Error body: `{ "status": "error", "message": "...", "details": "..." }`

| Code | Meaning |
|------|---------|
| `400` | Invalid input |
| `401` | Missing / invalid `X-API-Key` |
| `404` | Unknown model or prediction id |
| `429` | Rate limit — 100 creates / min, 10 concurrent per key |
| `5xx` | Retry with backoff |

## Overview

**PixVerse 4K Video Upscale Overview**

**PixVerse 4K Video Upscale** is a video-to-video enhancement model from Pixverse designed to convert lower-resolution footage into detailed 4K output. It targets creators who need to improve clarity, sharpness, and perceived production value without re-shooting content. As part of the broader **PixVerse Features** family, it focuses specifically on upscaling existing clips rather than generating entirely new scenes. The primary differentiator of PixVerse 4K Video Upscale is its ability to enhance resolution while preserving the original motion and composition, making it suitable for repurposing social clips, archival material, or screen recordings. Integrated on each::labs, it can be used alone or in a pipeline with other Pixverse video-to-video models for end-to-end AI video workflows.

## Usage Notes

- API Base URL: `https://api.eachlabs.ai/v1`
- Authentication: send `X-API-Key: YOUR_API_KEY`. Generate a key from the Eachlabs dashboard at https://www.eachlabs.ai/dashboard/api-keys.
- File-typed parameters (`*_url`, `image_url`, `video_url`, `audio_url`, etc.) accept publicly-reachable HTTPS URLs only. Upload your asset first (GCS / S3 / your CDN) and pass the resulting URL. Data-URIs and localhost URLs are rejected.
- For structured parameters (arrays / objects) send real JSON values, not stringified payloads.
- Monetary values are reported in USD; per-token / per-megapixel rates may be billed in micro-cents internally.
- Prefer `webhook_url` over polling for long-running predictions — see the Webhook Callback section.