Add Orshot as a provider: render images, PDFs and videos from templates (new "Creative" category)

[rishimohan]

What problem does this solve?

Treg covers the whole marketing loop except the step that makes the creative. An agent can pull trending topics from TikTok, enrich a lead with Hunter and publish through Postiz, but nothing in the catalog produces the image, PDF or video it publishes.

Orshot (https://orshot.com) fills that gap: templates designed once in a browser editor, rendered via API with dynamic modifications (text, images, colors, data) as PNG/JPG/WebP, multi-page PDF, MP4 or GIF. Used by marketing and sales teams for social posts, OG images, one-pagers, certificates, ad creatives and short videos.

Fit with treg's model:

API key provider, Authorization: Bearer <key> header.

Free probe: GET https://api.orshot.com/v1/workspace returns 401 on a bad key, 200 with account + plan on a good one.

Simple meter: 1 credit = 1 image, 1 PDF page or 1 video second. Cheapest public tier $39/1500 credits ($0.026/credit), overage $24-36 per 1k. Fits currency: credit with a credit_rates_usd entry.

URL-mode responses (response.type: "url"), so example responses stay small. Async mode with job polling for video.

OpenAPI at https://orshot.com/openapi.json (40+ routes) for the extended tier; llms.txt at https://orshot.com/llms.txt.

Library of ready templates works on any key, so test_request is cheap and reproducible.

Proposed solution

New platform design (category "Creative") in capabilities.yaml with capabilities: design.template.list, design.template.modifications, design.image.render, design.pdf.render, design.video.render, design.render.job.get.

Registry entry OAuthProvider(auth_kind="key", service="orshot", ...) with probe_path="/workspace", token_header="Authorization", token_format="Bearer {secret}".

Core tier orshot.yaml with ~8 curated endpoints (list templates, get modifications, render image / PDF / video, async job get, library templates), each with input, a cheap test_request against a library template, cost block and verified example response. Extended tier generated from the OpenAPI spec.

Cost blocks: image per_call 1 credit; PDF per_result 1 credit per page; video/GIF per_result 1 credit per second. credit_rates_usd.orshot = 0.026 from the cheapest public tier.

Bring-your-own-key first. Happy to provide a funded key later if you want it platform-eligible on treg's own account.

I'm on the Orshot side and can write the registry entry, YAML, lettermark logo and tests, and answer any questions on billing edge cases. Fine to proceed with a PR?

Alternatives considered

No response

[rishimohan]

One refinement after drafting the files: Orshot is really two shelves, so I'd propose two new categories rather than one, and I've drafted it that way.

Creative, platform design: template list, modifications, image / PDF / video render, and the ready-made library. This is where the provider card would sit.

Automation, platform automation: background render jobs (start / get / list), signed URLs that render on demand when fetched (drop one in an email, a sheet cell or an img tag), and webhook ingress that turns any JSON payload (Shopify product, CRM event, Zapier) into a render. Same engine, unattended. Nothing in the catalog covers "run this without an agent in the loop" today, and I think that shelf will grow beyond Orshot (schedulers, queues, form-to-anything tools).

Left out on purpose: Orshot's Workflows API (triggers to render to destinations) is Enterprise-gated for API-key callers right now, so a bring-your-own-key user would 403. It can join the automation platform once it opens up.

Draft passes catalog_validate.py clean (13 endpoints, both categories, second added as a billing unit for per-second video). Happy to collapse to a single category if you'd rather keep the tab count down. Which way do you want it?