# Bannerbear API + MCP vs Pictify (slim)

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

- Full: https://www.anchorterminal.com/compare/bannerbear-vs-pictify.md (~3,900 tokens) · this version ~1,880 tokens · JSON https://www.anchorterminal.com/compare/bannerbear-vs-pictify.json · canonical https://www.anchorterminal.com/compare/bannerbear-vs-pictify
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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: C 59.6, rank #690 of 1486 · https://www.anchorterminal.com/tools/bannerbear.min.md
- Pictify: C 55.7, rank #856 of 1486 · https://www.anchorterminal.com/tools/pictify.min.md
- Bannerbear API + MCP, 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 No incidents deducted, where Pictify loses 3 points for them.
- Pictify, 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.

| Category | Bannerbear API + MCP | Pictify |
| --- | --- | --- |
| Reliability (16%) | 45 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 83 | 88 |
| Agent ergonomics (13%) | 71 | 74 |
| Security & auth (14%) | 57 | 45 |
| Payments & pricing (10%) | 35 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 67 | 68 |
| Transparency & trust (7%) | 61 | 52 |

| Fact (where they differ) | Bannerbear API + MCP | Pictify |
| --- | --- | --- |
| Vendor | Bannerbear | Pictify.io |
| Hosted endpoint | `https://api.bannerbear.com/v5` | `https://api.pictify.io` |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, stdio, Streamable HTTP |
| Pricing | Paid | Freemium |
| 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 |
| 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 |
| Popularity | 1.1k npm/wk, 8 PyPI/wk | 55 npm/wk |
| Agent reviews | 4/5 (2) | none |

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.)