OpenAny
Add OpenAny to Grok BotGet API key

Happyhorse 1.0 r2v

happyhorse-1.0-r2v

Use the HappyHorse 1.0 R2V API for reference-to-video generation. Provide supported reference media to guide the generated clip. Create a new shot that follows a visual reference. Compare the available provider routes, request examples, and usage prices on OpenAny.

Published price
From $0.124 / second
Billing unit
/ second
Context / Max output
— / —
Listed routes
2
Base URL
https://api.openany.si/v1
POST
/v1/videos
GET
/v1/videos/{task_id}
Authentication
Authorization: Bearer $OPENANY_API_KEY

Provider

Call method
Published price $0.124 / second

Request parameters

ParameterType / rangeDefault valueRequiredDescription
durationnumber—Noduration
input_referencestring—Noinput_reference
modelstring—Nomodel
promptstring—Noprompt
ratiostring—Noratio

No required parameters returned.

Request example

curl 'https://api.openany.si/v1/videos' \
  -H "Authorization: Bearer $OPENANY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "model": "happyhorse-1.0-r2v"
}'

Response example

Configured response example · not a live result

JSON
{
  "status": "succeeded",
  "created": 1789393017,
  "openany_cost": 0
}

Error handling

400Check the model ID and request fields.
429Retry with exponential backoff.
5xxRetry only temporary provider failures.

JSON Schema

{
  "type": "object",
  "properties": {
    "model": {
      "type": "string"
    },
    "ratio": {
      "type": "string"
    },
    "prompt": {
      "type": "string"
    },
    "duration": {
      "type": "number"
    },
    "input_reference": {
      "type": "string"
    }
  }
}

Model API questions

How do I call Happyhorse 1.0 r2v through OpenAny?

Use model ID happyhorse-1.0-r2v with an OpenAny key and the operation published in this model's API tab. The model API base is https://api.openany.si/v1. Confirm the protocol and request schema; model availability does not imply every OpenAI API operation is supported.

How is Happyhorse 1.0 r2v billed?

Compare the published rate and billing unit of the selected provider route. Input, output and cache token rates may differ. Image, audio and video models can use other units. Recorded usage determines the charge under that route's billing contract.

Are Community and Verified routes the same as an official publisher API?

No. Inspect the provider name and supply classification for the specific route. A marketplace listing or a supply label is not a claim of publisher endorsement, identical service or measured uptime. Different route prices may reflect different supply and conditions.

Where do these prices come from, and when were they updated?

Rates come from the provider routes in OpenAny's public model catalog, not an independent quote from the model publisher. The catalog does not supply a price update timestamp. A page or catalog snapshot date is not a price revision date. Compare supply, billing units, tiers and conditions; a lower listed rate alone does not establish equivalent service or explain the price difference.

Use Happyhorse 1.0 r2v with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.