Head to head · Design templates · October 2026 research run

Robolly vs Shotstack

Shotstack scores 67.3 (B) on agent readiness against Robolly's 48.4 (D), and leads in 6 of 7 scored categories. Robolly leads on agent ergonomics. Both do design templates.

Best programmatic image and design asset APIs for AI agents · All 153 assets comparisons

Which one, for what

Robolly D

Best for Template-driven images, PDFs and short videos for marketers and developers who want a hosted editor and simple synchronous calls.

Ahead on

  • Agent ergonomics, 75 against 63

Also in its favour

  • Free to start without a card
  • No incidents deducted, where Shotstack loses 3 points for them

Watch for

No OpenAPI or other machine-readable contract found

Shotstack B

Best for Teams that render video, images or audio from JSON or templates at volume and want an agent to draft edits that a person reviews in Studio.

Ahead on

  • Reliability, 95 against 48
  • Schema & documentation, 88 against 57
  • Payments & pricing, 45 against 35
  • Maintenance & community, 73 against 5
  • Transparency & trust, 73 against 49

Watch for

API keys have no scopes. One production key and one sandbox key reach the Edit, Serve and Ingest APIs, and key rotation was not found in the docs

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Shotstack +68

Robolly 5

No changelog, release notes or dated API change was found. The sitemap marks every docs page as modified on 4 November 2026, which reads as a site rebuild rather than a change, so it isn't counted (0). No dated changes since 8 August (0). Support by email, with chat on higher plans; not tested (5 of 15). Not in the official MCP registry and no SDKs (0). No public package or repository (0). 0 + 0 + 5 + 0 + 0 = 5.

Shotstack 73

API definition 1.23.3 (@shotstack/schemas) tagged on 27 October 2026, six days before the check, after 1.23.0 on 15 October added a source file on generation assets (30). 21 definition tags and 13 CLI tags (0.8.x to 0.15.2, the last on 22 October) since 4 August 2026, and the skill repository synced from CLI 0.16.0 to 0.17.0 between 25 and 30 October (20). Dated changelog for the definition in its repository, in-app support on every plan and a GitHub issue template for the CLI. Issue threads were not read (8). @shotstack/cli and @shotstack/schemas are current, while npm shotstack-sdk 0.2.9 dates from July 2024 per the 8 October check; the PyPI release date came from a path pypi.org's robots.txt disallows and is struck, and pypi.org didn't resolve on 2 November. The MCP registry entry was not checked (7). The definition repository runs build, smoke and example tests on pull requests. Since 25 October the CLI repository holds only the agent skill and says the CLI's source isn't published there, so its release tests can no longer be read (8). 30 + 20 + 8 + 7 + 8 = 73.

Reliability Shotstack +47

Robolly 48

Hosted lines. The footer links an UptimeRobot status page, but it loads its figures from /api/, which stats.uptimerobot.com's robots.txt disallows, so the page showed no monitors or history (10 of 20 for a page that exists) and no history was read (5). A hard limit of 3 renders a second is published (15). The rate-limit error code and advice to send renders one at a time, and identical renders are cached for 45 days at no cost, which makes a retry safe; there's no Retry-After or backoff interval (8 of 15). No SLA found (0). The API isn't labelled beta (10). 10 + 5 + 15 + 8 + 0 + 10 = 48.

Shotstack 95

Hosted lines. Public status page at status.shotstack.io with monitors, the Edit API in production among them (20). Its feed and incident pages hold no incident in the 90 days from 4 August 2026. The newest incident, number 8 (range parameters in render payloads causing failures, 21 July 2026), left the window on 20 October, /incidents/9 answers 404, and the window holds only two completed maintenance windows (11 August, rendering stayed available; 4 and 5 September, billing, with the API fully available). A readable page that posts incidents, none in the window, is a clean record (30, was 20). Rate limits per API key in a fixed 60-second window, 300 for Edit, 600 for Serve and 300 for Ingest in production (15). A 429 returns rate_limit_error with advice to wait for the window and retry with exponential backoff, and POST /generate takes an Idempotency-Key, but POST /render has none and no Retry-After is documented for rate limits (10). Schedule 2 of the terms is an SLA of 99.9 per cent with a 10 per cent credit, free plans excluded (10). The Edit API is v1 and neither the MCP server nor the CLI carries a beta label (10). 20 + 30 + 15 + 10 + 10 + 10 = 95.

Schema & documentation Shotstack +31

Robolly 57

No OpenAPI or other machine-readable contract found for the REST API, and the MCP server is closed. The MCP page lists all nine tools and get_template_modifications returns each template's keys, constraints and examples at run time (8 of 25, on that partial evidence). llms.txt indexes the docs (10). The MCP page says what each tool does, which tools change templates or spend credits, and that there is no delete tool (14 of 20). Modification keys follow {element-name}.{modification-key} with constraints from the template rather than a fixed schema (7 of 15). Request examples throughout and an error code table with eight codes (13 of 15). /v1 paths with no changelog (5 of 15). 8 + 10 + 14 + 7 + 13 + 5 = 57.

Shotstack 88

Public OpenAPI 3.0.1 definition of the Edit API with 14 operations and 122 schemas. The MCP tool schemas need a signed-in account and were not read (25). llms.txt, llms-full.txt and a Markdown twin of every guide page (10). The conventions guide and MCP page say when to use studio or render_video and name the five commonest mistakes (17). 84 enums and required fields across the schemas, with per-model generation options published as JSON Schema by GET /models (13). 367 examples in the definition. Error responses are documented for the generation endpoints, while render and template operations document only the success response (10). v1 and stage in the path and a dated changelog for the definition, less 2 because release 1.22.0 removed a response field in a minor version (13).

Transparency & trust Shotstack +24

Robolly 49

Closed service under terms effective 8 April 2026 from Avantis Innovations LLC in Wyoming. The terms can change without notice (15). The privacy policy of the same date covers Google sign-in and Sheets data, says spreadsheet rows aren't kept beyond a render and account data is deleted with the account, and otherwise names no periods (10 of 30). No deprecation policy or notices (0). Hosting is described only as third-party vendors, with no processors or locations named, while the footer says Made in EU (2 of 20). 15 + 10 + 0 + 2 = 27.

Shotstack 73

Closed service under published terms, with the schemas and SDKs under MIT. The CLI was Apache-2.0 in its last public source (0.15.2, 22 October 2026); since 25 October its source isn't published and the repository keeps only the agent skill (15). A DPA and sub-processor list updated 6 October 2026, and terms that say customer data is not used to train AI models. The privacy policy is dated 21 December 2021 and says ingested media is deleted after rendering, while the Ingest guide says sources are stored until deleted, and the DPA gives 24 hours for outputs while the hosting guide calls CDN hosting permanent by default (18). The terms promise reasonable notice before a feature is retired and 30 days before material changes to the terms, and deprecated asset types keep working, but no dated deprecation policy was found (8). Five sub-processors named with purposes and locations, AWS in Sydney and the United States, with seven days' notice of additions (20).

Agent ergonomics Robolly +12

Robolly 75

Nine MCP tools (25). The renders list pages with a cursor, and templates are found by name (14 of 20). Errors carry errorCode and developerMessage with eight documented codes (17 of 20). Identical renders are cached for 45 days, so repeats are free and safe, the MCP server has no delete tool, and annotations couldn't be read on the closed server (12 of 20). Renders return the file synchronously by default, but there's no SDK (7 of 15). 25 + 14 + 17 + 12 + 7 = 75.

Shotstack 63

15 MCP tools by the vendor's list, with the authoring guide loaded on demand through get_shotstack_guide and skill references read only when relevant (18). No pagination, limit or filter on the template or source lists in the definition. The CLI prints JSON with --output json (6). Errors carry status, title and detail, confirmed on a 401, generation errors carry a code, the CLI validates offline and exits 0, 1 or 2 for success, permanent and retryable failures (17). Idempotency-Key and a result cache on generation and a free quote, but no idempotency on renders, and MCP annotations were not readable (12). Smart clip lengths and a default v1 environment keep requests short. Five official SDK repositories exist, but the npm and PyPI packages date from July 2024 (10).

Payments & pricing Shotstack +10

Robolly 35

No x402, MPP or L402 (0). Plan prices are public and a table gives the credit cost of each format and size (15 of 20). 7-day trial with no card (20). A person signs up, then copies the key or approves OAuth (0). 0 + 15 + 20 + 0 = 35.

Shotstack 45

No x402, MPP or L402 (0). Public per-minute prices, 20 cents on pay as you go down to 5 cents on Volume, with AI generation priced per model through a quote endpoint and four examples on the pricing page (20). 10 credits for 30 days with no card, and a free watermarked sandbox (20). Checking an edit and opening a Studio preview need no key, but any render needs a key from a browser signup (5).

Score by category

CategoryWeight this runRobollyShotstackEdge
Reliability16%204895Shotstack +47
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25788Shotstack +31
Agent ergonomics13%16.27563Robolly +12
Security & auth14%17.54748Shotstack +1
Payments & pricing10%12.53545Shotstack +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8573Shotstack +68
Transparency & trust7%8.84973Shotstack +24
Negative events≤150-3
TotalD 48.4/100B 67.3/100

Facts side by side

FactRobollyShotstack
KindHTTP APIHTTP API
VendorAvantis Innovations LLC (Robolly)ShotStack Pty Ltd
Hosted endpointhttps://api.robolly.com/v1https://api.shotstack.io/edit/v1
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidPay per use
x402nono
LicenceClosed service under the Robolly terms of use (effective 8 April 2026)Proprietary service under Shotstack's Terms and Conditions. The schemas package and SDKs are MIT and the Studio SDK is under PolyForm Shield 1.0.0. The CLI was Apache-2.0 up to its last public source (0.15.2, 22 October 2026); since 25 October 2026 its source isn't published and the shotstack-cli repository holds only the agent skill
Tools exposed915
Read-only variant documentednono
llms.txtyesyes
Last releasenone2026-10-27
Terms last updated2026-04-08no date given
Privacy policy last updated2026-04-08no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularitynone0 stars, 1.2k npm/wk, 326 PyPI/wk
Agent reviewsnone3.5/5 (4)

How the scores have moved

Robolly

No score change since it was listed.

Shotstack

Verdicts

Robolly

Robolly's nine MCP tools, synchronous renders, typed error codes and free cached re-renders keep template rendering cheap and predictable for an agent, and OAuth connections can be revoked per client. There is no OpenAPI file, changelog or dated release, and API access starts at $39 a month after a 7-day trial.

Shotstack

A public OpenAPI definition, Markdown docs, a hosted MCP server with OAuth and a free watermarked sandbox let an agent draft, check and render video with little setup. API keys have no scopes, webhooks are unsigned, no security contact or certification of Shotstack's own was found, and the npm Node SDK dates from July 2024.

Before you call either

Robolly

  1. Call get_template_modifications before render to learn the keys a template accepts
  2. Send renders one at a time; the API refuses more than 3 a second with rate-limit
  3. Repeat an identical render freely; it is cached for 45 days and costs nothing
  4. Poll get_render after render_video, since video renders are queued
  5. Stop on render-limit-exhausted and tell the user the monthly credits are spent

Shotstack

  1. Fetch https://shotstack.io/docs/api/api.edit.json and the conventions guide before writing an edit. Track order is reversed, so the first track renders on top
  2. Render in stage first. It is free and watermarked, but AI generation there is charged from the production credit balance
  3. Call POST /generate/quote before POST /generate, and send an Idempotency-Key header on generation. POST /render has no idempotency key, so do not resubmit blindly
  4. Do not store the url from the render status response. It expires after 24 hours. Use the CDN address built from owner and the render id
  5. On a 429, wait for the 60-second window to reset and retry with backoff. Limits are per API key, 300 a minute on the Edit API in production

Questions

Which is better for AI agents, Robolly or Shotstack?

Shotstack scores 67.3 (B) on agent readiness against Robolly's 48.4 (D), and leads in 6 of 7 scored categories. Robolly leads on agent ergonomics.

Do Robolly and Shotstack need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Robolly and Shotstack without installing anything?

Yes. Robolly has a hosted endpoint at https://api.robolly.com/v1 and Shotstack at https://api.shotstack.io/edit/v1.

Other comparisons with Robolly or Shotstack

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.