Hermes Agent,
render the shot.
Drop PayPerQ Video Generation into your Hermes Agent flow as a single async skill. Prompts and images go in, cinematic 1080p Kling 2.1 Pro MP4s come back, billed per generation. The submit-and-poll shape matches Hermes Agent's contract for long-running skills — declare it once, then forget it.
Real Hermes flows that render their own video.
Each pattern below is a single Hermes Agent flow with PayPerQ Video Generation registered as one async skill. The math works because the flow only spends when it actually produces a usable clip.
Brief to b-roll, autonomously.
A user hands Hermes Agent a marketing brief. The flow drafts shot descriptions, fires off generations in parallel, polls each job, and assembles the finished clips into a deliverable. No human-managed Kling or Runway account anywhere in the chain — and no per-seat charge for a flow that runs once a week.
Catalog photos into motion at scale.
A scheduled Hermes flow walks new SKUs in the catalog, calls the skill with each product photo, and produces a turntable or lifestyle clip per item. Image-to-video with first-frame conditioning keeps the product faithful; per-call billing keeps the cost line aligned with catalog growth.
Daily reels, generated on a cron.
Hermes watches a content brief, picks the day's angle, generates a 6-second clip, captions it, and posts. Days you don't post cost zero; days you post a lot scale linearly. No flat-rate seat math eating margin on quiet weeks.
Variations on demand for human review.
A Hermes flow generates dozens of takes from a single brief — different camera angles, lighting, talent — and presents them ranked for human review before approval. Cheap exploration, expensive only when humans actually pick a winner.
Stop wrapping video subscriptions into your flows.
Register one async skill, connect a wallet, and your Hermes Agent flow gets cinematic 1080p video on every relevant call. Idle runs cost zero. Tool migrations later cost zero. That's the entire deal.
- Single Hermes skill
- Async submit-and-poll
- Kling 2.1 Pro under the hood
- Flow caps honored
Hermes Agent specific questions.
If something below doesn't cover your case, ping us — we work directly with Hermes Agent builders, no SDR funnel.
How does this register as a Hermes Agent skill?
+
It's an async POST endpoint with a typed body and a polling endpoint for status. You register both in Hermes the same way you'd register any long-running HTTP skill — endpoint, schema, per-call price. Hermes Agent handles the polling loop and surfaces the resulting video URL back into the flow's state.
Does Hermes Agent need a long-lived API key?
+
No. The endpoint accepts x402-signed requests, so Hermes can pay per call from a wallet you connect. There's no shared secret to rotate or leak in flow logs.
What happens when a Hermes flow hits its budget cap?
+
The skill returns whatever generations have already completed and Hermes stops issuing new submissions. The flow can decide whether to ask the user for more budget or hand off the partial deliverable.
Can Hermes run many generations in parallel?
+
Yes. Each submission is independent — Hermes can fire off N generations and poll them concurrently. Per-key rate limits apply with concurrency-fair queueing so a noisy flow never starves another flow on the same key.
How is this different from giving Hermes a Kling or Runway seat?
+
Subscriptions don't fit Hermes Agent's skill model. The skill can't report a true per-call cost, so Hermes can't do real budget planning. PayPerQ Video Generation reports an honest per-call cost up front, which is what Hermes was designed to consume.
What about content rights?
+
Generated outputs follow Kling 2.1 Pro's commercial-use terms. Don't generate content that infringes third-party rights or violates the model's safety policy; the endpoint enforces standard content filters before returning a video.