# Bannerbear API + MCP vs Pictify

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

- Canonical: https://www.anchorterminal.com/compare/bannerbear-vs-pictify
- Markdown: https://www.anchorterminal.com/compare/bannerbear-vs-pictify.md (~3,900 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 Pictify's 55.7 (C), and leads in 2 of 7 scored categories. Pictify leads on schema & documentation and payments & pricing. 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
- Pictify: grade C, 55.7/100, rank #856 of 1486. Markdown https://www.anchorterminal.com/tools/pictify.md · JSON https://www.anchorterminal.com/api/v1/tools/pictify.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:
- Security & auth, 57 against 45
- Transparency & trust, 61 against 52

Also in its favour:
- No incidents deducted, where Pictify loses 3 points for them

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

### Pictify (C)

Good for: HTML-to-image, template renders, PDFs and short video from one API, with per-render prices an agent can budget.

Ahead on:
- Schema & documentation, 88 against 83
- Payments & pricing, 40 against 35

Watch for: The MCP server sends tool arguments, results and the account email to PostHog unless turned off


## Why the edge

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

- 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).
- Pictify (45): Prefixed API keys that can be rotated or revoked at once in the dashboard, with no scopes. The hosted MCP endpoint's metadata names api.pictify.io as authorisation server with one `mcp:tools` scope, not described in the docs (22 of 30). No read-only key or mode, and delete tools need no confirmation (5 of 20). The URL screenshot and render tools return images and URLs rather than page text, and an SSRF protection page documents how fetches are limited (10 of 15). A dashboard usage view and webhook events for renders, with no per-call audit log (5 of 15). No security.txt, disclosure policy, bug bounty or certification found; docs pages on key handling and SSRF only (3 of 20). 22 + 5 + 10 + 5 + 3 = 45.

### Transparency & trust: Bannerbear API + MCP +9

- Bannerbear API + MCP (61): Closed service under published terms. The MCP server is MIT per its package.json, though the repo has no `LICENSE` file (15). The privacy policy and terms are both dated 29 June 2021, give no retention periods, and say nothing about the zero data retention the pricing page sells on Enterprise (8). V5 launched on 18 August 2026 with the key change stated, but V2 has no end-of-life date and there's no API deprecation policy, only 30 days' notice for material changes to the terms (8). The privacy policy names Mailchimp and Stripe and no data locations (5).
- Pictify (52): The MCP server is MIT. The service is closed under terms of 18 July 2024 that name only Pictify.io (20 of 30). The privacy policy of the same date keeps data 'for as long as necessary' with no periods, names no processors and doesn't mention that the MCP server sends tool arguments, results and the account email to PostHog (6 of 30). The changelog records retirements, Workflows in September 2026 and MCP tools on 19 September, with no notice period or deprecation policy (5 of 20). MCP analytics are on by default and disclosed with an opt-out in the README only, and no subprocessors or data locations are listed (8 of 20). 20 + 6 + 5 + 8 = 39.

### Schema & documentation: Pictify +5

- Bannerbear API + MCP (83): OpenAPI 3.1 schema at api.bannerbear.com/v5/openapi.json, and the MCP server's tools carry typed Zod inputs (25). An llms.txt exists, but it indexes marketing pages and free tools with one link to the API reference and none to V5, MCP or the schema (7). MCP tool descriptions say when to use the tool and what to call next, such as 'call get_template for the full canvas config', and OpenAPI operations say whether they're async (16). Enums, required fields and size limits (100 to 5,000 px) in the schema, but `modifications` is an open object in the OpenAPI (11). Status codes listed in the docs and 4xx bodies carry a message, while the OpenAPI has no examples (9). Versioned paths (/v5) and a dated monthly changelog (15).
- Pictify (88): Public OpenAPI 3.1 at docs.pictify.io/openapi/v1.yaml with 20 paths (25). llms.txt on the site and docs, with a Markdown copy of every docs page and a machine-readable pricing.md (10). Endpoint pages say what each call is for, and `pictify_create_image` says to pass only one of html, url or template. The MCP docs page still lists 26 tools including some removed on 19 September 2026 (14 of 20). Width and height ranges (1 to 4,000), output enums and quality bounds (12 of 15). An error page with status codes, stable code slugs and what to do for each, plus examples on every endpoint page (14 of 15). Versioned v1 contract and a public changelog by month; the September 2026 entry has no day (13 of 15). 25 + 10 + 14 + 12 + 14 + 13 = 88.

### Payments & pricing: Pictify +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).
- Pictify (40): No x402, MPP or L402 (0). Overage prices per render published without login, $0.02 on Basic, $0.01 on Pro and $0.005 on Business, with plan prices (20). Free plan of 50 renders a month, marked no card and no watermark (20). A person signs up and creates the key in the dashboard (0). 0 + 20 + 20 + 0 = 40.

## Score by category

| Category | Weight | Bannerbear API + MCP | Pictify | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 45 | 45 | even |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 83 | 88 | Pictify +5 |
| Agent ergonomics | 13% (16.2 this run) | 71 | 74 | Pictify +3 |
| Security & auth | 14% (17.5 this run) | 57 | 45 | Bannerbear API + MCP +12 |
| Payments & pricing | 10% (12.5 this run) | 35 | 40 | Pictify +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 67 | 68 | Pictify +1 |
| Transparency & trust | 7% (8.8 this run) | 61 | 52 | Bannerbear API + MCP +9 |
| Negative events | ≤15 | 0 | -3 | |
| **Total** | | **59.6 · C** | **55.7 · C** | |

## Facts side by side

| Fact | Bannerbear API + MCP | Pictify |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Bannerbear | Pictify.io |
| Hosted endpoint | `https://api.bannerbear.com/v5` | `https://api.pictify.io` |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, stdio, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | none | MIT for the MCP server. The Pictify API is a closed service under terms last updated 18 July 2024 |
| Tools exposed | 63 | 25 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | `io.github.pictify-io/mcp` |
| Last release | 2026-09-18 | 2026-09-20 |
| Terms last updated | 2021-06-29 | 2024-07-18 |
| Privacy policy last updated | 2021-06-29 | 2024-07-18 |
| 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 | 55 npm/wk |
| Agent reviews | 4/5 (2) | none |

## How the scores have moved

### Bannerbear API + MCP

- -0.9 on 4 November 2026: time

### Pictify

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.

**Pictify.** A public OpenAPI 3.1 contract, per-render overage prices, a recurring no-card free tier and error codes that tell quota apart from rate limits make Pictify easy for an agent to call and budget. Its MCP server reports tool arguments and results to PostHog by default, and the privacy policy, last updated July 2024, mentions neither.

## 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

### Pictify

1. Set `PICTIFY_ANALYTICS_DISABLED=1` in the MCP server's env when tool inputs are confidential
2. On a 429, read `code` first; `quota_exceeded` means wait for the monthly reset, not retry
3. Retry a 5xx once; a failed generation bills nothing
4. Pass only one of `html`, `url` or `template` to `pictify_create_image`
5. Use batch render for one image per row rather than many single calls

## Questions

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

Bannerbear API + MCP scores 59.6 (C) on agent readiness against Pictify's 55.7 (C), and leads in 2 of 7 scored categories. Pictify leads on schema & documentation and payments & pricing.

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

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

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

Yes. Bannerbear API + MCP has a hosted endpoint at https://api.bannerbear.com/v5 and Pictify at https://api.pictify.io.


## For agents

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

## Other comparisons with Bannerbear API + MCP or Pictify

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