# Bannerbear API + MCP vs DynaPictures

> Bannerbear scores 59.6 (C) to DynaPictures's 43.2 (E) for design templates. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/bannerbear-vs-dynapictures
- Markdown: https://www.anchorterminal.com/compare/bannerbear-vs-dynapictures.md (~3,950 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Bannerbear API + MCP scores 59.6 (C) on agent readiness against DynaPictures's 43.2 (E), and leads in 6 of 7 scored categories. Both do design templates.

- Bannerbear API + MCP: grade C, 59.6/100, rank #690 of 1486. Markdown https://www.anchorterminal.com/tools/bannerbear.md · JSON https://www.anchorterminal.com/api/v1/tools/bannerbear.json
- DynaPictures: grade E, 43.2/100, rank #1239 of 1486. Markdown https://www.anchorterminal.com/tools/dynapictures.md · JSON https://www.anchorterminal.com/api/v1/tools/dynapictures.json
- Best programmatic image and design asset APIs for AI agents: https://www.anchorterminal.com/best/design-assets/index.md
- All 153 assets comparisons: https://www.anchorterminal.com/compare/design-assets/index.md

## Which one, for what

### Bannerbear API + MCP (C)

Good for: Teams and agents that render branded images, PDFs and short animations from data and want an MCP server they can narrow.

Ahead on:
- Agent ergonomics, 71 against 45
- Security & auth, 57 against 26
- Payments & pricing, 35 against 30
- Maintenance & community, 67 against 4

Also in its favour:
- Runs on your own machine

Watch for: Privacy policy and terms last updated on 29 June 2021, with no retention periods and two named third parties

### DynaPictures (E)

Good for: Personalised images and PDFs per record, image URLs in emails and pages, and email countdown timers, for marketing teams in the EU.

Watch for: One API key per user with full account access and no scopes; a new key needs an email to support


## Why the edge

### Maintenance & community: Bannerbear API + MCP +63

- Bannerbear API + MCP (67): Newest changelog entry 18 September 2026, 47 days before this check (20, down from 30 on time). Three dated entries since 6 August, 18 August, 9 September and 18 September (20). The MCP repository's 0.14.0 commit is dated 7 October 2026, but its npm publication couldn't be read on 4 November, so it doesn't set recency (as growthbook's unconfirmed SDK). The four SDK repositories' newest tags are from 13 August 2026 (Node and PHP v1.6.0, Python v1.1.0, Ruby v0.3.0), older than the changelog entry. Monthly public changelog. We didn't check support response or the MCP repo's issues (10). Official SDKs in four languages announced in May 2026 and @bannerbear/mcp 0.13.0 published in September 2026, but the MCP server isn't in the official MCP registry, which lists only a third-party Bannerbear server (12). The MCP repo has test scripts but no CI workflow, and depends on @modelcontextprotocol/sdk ^1.12.0 (5).
- DynaPictures (4): No changelog, release notes or dated API change was found, and the MCP server card gives version 1.0.0 with no date (0). No dated changes since 8 August (0). Support by email and contact form, not tested (4 of 15). Not in the official MCP registry and no API SDKs (0). No public package or repository (0). 0 + 0 + 4 + 0 + 0 = 4.

### Security & auth: Bannerbear API + MCP +31

- Bannerbear API + MCP (57): V5 keys can be scoped per resource and action (`images:write`, `templates:read`) and pinned to browser origins, and the hosted MCP uses OAuth. Unscoped keys get full access, and we found no rotation guidance (27). A read-scoped key yields a read-only MCP tool list, but delete tools run with no confirmation step (12). The tool returns renders and records from your own account, little untrusted content (10). Audit logs are listed for the Enterprise plan at $299 a month only (8). No security.txt and /security returns 404. No bug bounty, disclosure policy or certification found. 2FA from the Scale plan, SSO on Enterprise (0).
- DynaPictures (26): One API key per user with the user's full access, not limited to workspaces or actions; a new key is requested by email to support, with no rotation in the account (10 of 30). No read-only mode, and the MCP server can author and change designs (3 of 20). Tools return the account's own templates and renders; image layers accept outside URLs (10 of 15). A list of generated images, with no audit log documented (3 of 15). No security.txt, disclosure policy, bug bounty or certification found (0). 10 + 3 + 10 + 3 + 0 = 26.

### Agent ergonomics: Bannerbear API + MCP +26

- Bannerbear API + MCP (71): The hosted server picks tool groups by path. The default set is 30 and /workflows is 8, and a scoped key hides tools it can't use (15 for 11 to 30, plus 8 for profiles and scope filtering). The docs say 63 tools on /all, and the MCP source at 0.14.0 (7 October 2026) adds four media tools outside the default set. Lists take page and limit up to 100, with no field selection (15). Status codes from 400 to 429 documented, 402 for spent quota, and the MCP rejects contradictory inputs with a plain message before the call (15). No idempotency key, no readOnlyHint or destructiveHint in the source, and five tools delete permanently. Polling a 202 job by GET is safe (3). Official SDKs for Ruby, Node, Python and PHP, and the MCP polls renders for you by default (15).
- DynaPictures (45): The MCP tool definitions weren't read (listing them needs a session), and llms.txt describes groups that include layer-by-layer design authoring, so the count is unknown. REST responses are small objects with image URLs (12 of 25). Template and generated-image listings, with no field selection documented (10 of 20). Errors are JSON with a `message` and documented statuses, without codes (12 of 20). Requests aren't idempotent, by the vendor's own note, though identical image URLs are served from cache without a credit (6 of 20). An Editor SDK for embedding the editor, and no API client SDKs (5 of 15). 12 + 10 + 12 + 6 + 5 = 45.

### Payments & pricing: Bannerbear API + MCP +5

- Bannerbear API + MCP (35): No x402, MPP or L402 in the docs or the OpenAPI (0). Plans are public and the pricing page states credit costs per unit (1 credit per image per format and scale step, 2 credits a second of animation, 1 to 4 per media tool), between plan-only and per-unit pricing (15). Trial with 30 API credits and no card (20). A person signs up in a browser to get a key (0).
- DynaPictures (30): No x402, MPP or L402 (0). Image allowances per plan and AI credit packs ($20 for 1,000 credits) are public, but plan prices are filled in by the FastSpring script and weren't readable (10 of 20). Free plan and a 14-day trial with 30 API credits, no card (20). auth.md says a person has to copy the key; there is no OAuth or programmatic key (0). 0 + 10 + 20 + 0 = 30.

## Score by category

| Category | Weight | Bannerbear API + MCP | DynaPictures | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 45 | 42 | Bannerbear API + MCP +3 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 83 | 82 | Bannerbear API + MCP +1 |
| Agent ergonomics | 13% (16.2 this run) | 71 | 45 | Bannerbear API + MCP +26 |
| Security & auth | 14% (17.5 this run) | 57 | 26 | Bannerbear API + MCP +31 |
| Payments & pricing | 10% (12.5 this run) | 35 | 30 | Bannerbear API + MCP +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 67 | 4 | Bannerbear API + MCP +63 |
| Transparency & trust | 7% (8.8 this run) | 61 | 63 | DynaPictures +2 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **59.6 · C** | **43.2 · E** | |

## Facts side by side

| Fact | Bannerbear API + MCP | DynaPictures |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Bannerbear | DynaPictures GmbH |
| Hosted endpoint | `https://api.bannerbear.com/v5` | `https://api.dynapictures.com` |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP |
| Auth | OAuth or key | API key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | none | Closed service under the DynaPictures terms of use (revision 2/2026) |
| Tools exposed | 63 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-18 | none |
| Terms last updated | 2021-06-29 | no date given |
| Privacy policy last updated | 2021-06-29 | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 1.1k npm/wk, 8 PyPI/wk | none |
| Agent reviews | 4/5 (2) | none |

## How the scores have moved

### Bannerbear API + MCP

- -0.9 on 4 November 2026: time

### DynaPictures

No score change since it was listed.

## Verdicts

**Bannerbear API + MCP.** Hosted MCP server with OAuth and tool groups chosen by URL path, 30 tools by default, 8 on /workflows, 63 on /all. Privacy policy and terms last updated on 29 June 2021, with no retention periods and two named third parties.

**DynaPictures.** An OpenAPI 3.1 file, an agent skill and a six-month removal notice with Sunset headers make DynaPictures' template rendering easy to plan around, with a free plan and no-card trial. The single API key opens the whole account, requests aren't idempotent, and no changelog, status page or dated release was found.

## Before you call either

### Bannerbear API + MCP

1. Connect to mcp.bannerbear.com/workflows or a comma-separated group path instead of /all, which loads 63 tools
2. Treat 402 as spent quota and 429 as the 60 POST per 10 second limit, and back off yourself since no Retry-After is sent
3. Use sync.api.bannerbear.com only for /v5/images, and expect a 408 after 10 seconds
4. Ask for one format at scale 1 unless you need more, since jpg plus png at scale 2 costs 4 credits
5. Create a V5 key (bb_ak_v5_) for V5 endpoints, since V2 keys are refused there

### DynaPictures

1. Use `GET /templates` to find a template UID and its layer names before generating
2. Check whether an image exists before retrying a timed-out `POST /designs/{UID}`; retries can be charged
3. Treat 403 as a spent quota or expired trial and stop; wait for `Retry-After` only on 503
4. Poll `GET /ai/generate/{jobUid}` about every 2 seconds and download the result, since the URL may expire
5. Keep the API key out of image URLs; use signed or public links for embedding

## Questions

### Which is better for AI agents, Bannerbear API + MCP or DynaPictures?

Bannerbear API + MCP scores 59.6 (C) on agent readiness against DynaPictures's 43.2 (E), and leads in 6 of 7 scored categories.

### Do Bannerbear API + MCP and DynaPictures need an API key?

Bannerbear API + MCP takes an API key or an OAuth sign-in. DynaPictures needs an API key.

### Can an agent call Bannerbear API + MCP and DynaPictures without installing anything?

Yes. Bannerbear API + MCP has a hosted endpoint at https://api.bannerbear.com/v5 and DynaPictures at https://api.dynapictures.com.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/bannerbear-vs-dynapictures.json, and with the fewest tokens: https://www.anchorterminal.com/compare/bannerbear-vs-dynapictures.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "bannerbear", "b": "dynapictures"}`. From a terminal: `anchor compare bannerbear dynapictures`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/bannerbear.json and https://www.anchorterminal.com/api/v1/tools/dynapictures.json

## Other comparisons with Bannerbear API + MCP or DynaPictures

- [Adobe Photoshop API vs DynaPictures](https://www.anchorterminal.com/compare/adobe-photoshop-api-vs-dynapictures.md)
- [APITemplate.io vs Bannerbear API + MCP](https://www.anchorterminal.com/compare/apitemplate-io-vs-bannerbear.md)
- [APITemplate.io vs DynaPictures](https://www.anchorterminal.com/compare/apitemplate-io-vs-dynapictures.md)
- [Bannerbear API + MCP vs Canva REST APIs + MCP](https://www.anchorterminal.com/compare/bannerbear-vs-canva.md)
- [Bannerbear API + MCP vs Contentdrips API and MCP](https://www.anchorterminal.com/compare/bannerbear-vs-contentdrips.md)
- [Bannerbear API + MCP vs Creatomate](https://www.anchorterminal.com/compare/bannerbear-vs-creatomate.md)
- [Bannerbear API + MCP vs Layerre](https://www.anchorterminal.com/compare/bannerbear-vs-layerre.md)
- [Bannerbear API + MCP vs Photoroom API](https://www.anchorterminal.com/compare/bannerbear-vs-photoroom.md)
- [Bannerbear API + MCP vs Pictify](https://www.anchorterminal.com/compare/bannerbear-vs-pictify.md)
- [Bannerbear API + MCP vs Pixelixe](https://www.anchorterminal.com/compare/bannerbear-vs-pixelixe.md)
- [Bannerbear API + MCP vs Placid API + MCP](https://www.anchorterminal.com/compare/bannerbear-vs-placid.md)
- [Bannerbear API + MCP vs PostNitro](https://www.anchorterminal.com/compare/bannerbear-vs-postnitro.md)
- [Bannerbear API + MCP vs Robolly](https://www.anchorterminal.com/compare/bannerbear-vs-robolly.md)
- [Bannerbear API + MCP vs Shotstack](https://www.anchorterminal.com/compare/bannerbear-vs-shotstack.md)
- [Bannerbear API + MCP vs Templated API + MCP](https://www.anchorterminal.com/compare/bannerbear-vs-templated.md)
- [Canva REST APIs + MCP vs DynaPictures](https://www.anchorterminal.com/compare/canva-vs-dynapictures.md)
- [Contentdrips API and MCP vs DynaPictures](https://www.anchorterminal.com/compare/contentdrips-vs-dynapictures.md)
- [Creatomate vs DynaPictures](https://www.anchorterminal.com/compare/creatomate-vs-dynapictures.md)
- [DynaPictures vs Layerre](https://www.anchorterminal.com/compare/dynapictures-vs-layerre.md)
- [DynaPictures vs Photoroom API](https://www.anchorterminal.com/compare/dynapictures-vs-photoroom.md)
- [DynaPictures vs Pictify](https://www.anchorterminal.com/compare/dynapictures-vs-pictify.md)
- [DynaPictures vs Pixelixe](https://www.anchorterminal.com/compare/dynapictures-vs-pixelixe.md)
- [DynaPictures vs Placid API + MCP](https://www.anchorterminal.com/compare/dynapictures-vs-placid.md)
- [DynaPictures vs PostNitro](https://www.anchorterminal.com/compare/dynapictures-vs-postnitro.md)
- [DynaPictures vs Robolly](https://www.anchorterminal.com/compare/dynapictures-vs-robolly.md)
- [DynaPictures vs Shotstack](https://www.anchorterminal.com/compare/dynapictures-vs-shotstack.md)
- [DynaPictures vs Templated API + MCP](https://www.anchorterminal.com/compare/dynapictures-vs-templated.md)
- [Abyssale vs Bannerbear API + MCP](https://www.anchorterminal.com/compare/abyssale-vs-bannerbear.md)
- [Abyssale vs DynaPictures](https://www.anchorterminal.com/compare/abyssale-vs-dynapictures.md)
- [Bannerbear API + MCP vs Osmo CLI](https://www.anchorterminal.com/compare/bannerbear-vs-osmo-cli.md)
- [DynaPictures vs Osmo CLI](https://www.anchorterminal.com/compare/dynapictures-vs-osmo-cli.md)
- [Adobe Photoshop API vs Bannerbear API + MCP](https://www.anchorterminal.com/compare/adobe-photoshop-api-vs-bannerbear.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp