Hy4 preview

hy4-previewhunyuan

Hy4 preview is served through QVeris by hunyuan. Compare its current input formats, context limits and usage price below to evaluate it for your application.

Input format: text → text
Usage pricing: Request-based pricing
Context tokens: 1,048,576
Maximum output tokens: 64,000

Overview

ChatJSONReasoningStreamingTool calling

What to evaluate

These evaluation ideas follow the capabilities enabled here. Test representative tasks before choosing a model.

Tool-assisted agents and multi-step automation
Reasoning and analytical problem solving
Long documents and codebase context

API

Call this model with your QVeris API key. The examples below use this model’s public ID and the API endpoint for this site.

Base URL: https://aigateway.qveris.ai/v1
Model ID: hy4-preview

1. Create an API key

Keep your API key on the server in the QVERIS_API_KEY environment variable. Do not expose it in browser code. Get an API key →

2. Send a request

Endpoint

curl -sS 'https://aigateway.qveris.ai/v1/chat/completions' \
  -H "Authorization: Bearer $QVERIS_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
  "model": "hy4-preview",
  "messages": [
    {
      "role": "user",
      "content": "Hello!"
    }
  ],
  "max_tokens": 64
}'

Run these examples on your server. JavaScript uses Node.js 18+; Python uses the standard library.

For streaming chat, set stream to true. Read SSE data until [DONE]; the qveris.billing event contains settlement details.

Successful requests are billed in Credits at the prices shown below. Save the X-QVeris-Call-ID response header for billing and support.

API integration

Usage pricing

Prices are the Credits charged by QVeris. Credits purchased in different packages may have different monetary costs.

Price depends on request parameters or billing meters. Check the API billing rules before submitting a request.

Final charges follow actual usage and the price effective when the request starts. Cached-input rates apply only to cache hits.

Credits and top-up pricing

Capabilities and limits

Context tokens: 1,048,576
Maximum output tokens: 64,000
Input modalities: text
Output modalities: text
Supported API operations: chat.completions messages responses

Integration notes

Only the capabilities listed above are advertised by this serving route. Optional provider parameters and agent features may require additional validation.

The context window includes input and generated output. Keep room for the response; tokenization and reasoning usage can differ by model.

Performance depends on the serving route and request. No gateway latency or uptime measurements are published here yet.

Model information and sources

A model-specific source has not been added yet. The capability and price information above is supplied by QVeris.