# Bannerbear API + MCP vs Placid API + MCP > Bannerbear API + MCP has a score of 60.5 (C) against Placid API + MCP's 43.2 (E). Both do design templates. The largest gap is maintenance & community, 70 points. Category scores, facts, verdicts and agent notes side by side. - Canonical: https://www.anchorterminal.com/compare/bannerbear-vs-placid - Markdown: https://www.anchorterminal.com/compare/bannerbear-vs-placid.md (~1,350 tokens) - Slim: https://www.anchorterminal.com/compare/bannerbear-vs-placid.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/compare/bannerbear-vs-placid.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-05 Bannerbear API + MCP has a score of 60.5 (C) against Placid API + MCP's 43.2 (E). Both do design templates. The largest gap is maintenance & community, 70 points. - Bannerbear API + MCP: grade C, 60.5/100, rank #245 of 452. Markdown https://www.anchorterminal.com/tools/bannerbear.md · JSON https://www.anchorterminal.com/api/v1/tools/bannerbear.json - Placid API + MCP: grade E, 43.2/100, rank #409 of 452. Markdown https://www.anchorterminal.com/tools/placid.md · JSON https://www.anchorterminal.com/api/v1/tools/placid.json ## Which one, for what Pick Bannerbear API + MCP for schema & documentation (+49), agent ergonomics (+31), security & auth (+23), maintenance & community (+70). Pick Placid API + MCP for reliability (+30). ## Score by category | Category | Weight | Bannerbear API + MCP | Placid API + MCP | Edge | | --- | --- | --- | --- | --- | | Reliability | 16% (20 this run) | 45 | 75 | Placid API + MCP +30 | | Performance | 10%, pending | pending | pending | not scored in this run | | Schema & documentation | 13% (16.2 this run) | 83 | 34 | Bannerbear API + MCP +49 | | Agent ergonomics | 13% (16.2 this run) | 71 | 40 | Bannerbear API + MCP +31 | | Security & auth | 14% (17.5 this run) | 57 | 34 | Bannerbear API + MCP +23 | | Payments & pricing | 10% (12.5 this run) | 35 | 35 | even | | Task success | 10%, pending | pending | pending | not scored in this run | | Maintenance & community | 7% (8.8 this run) | 77 | 7 | Bannerbear API + MCP +70 | | Transparency & trust | 7% (8.8 this run) | 61 | 60 | Bannerbear API + MCP +1 | | Negative events | ≤15 | 0 | 0 | | | **Total** | | **60.5 · C** | **43.2 · E** | | ## Facts side by side | Fact | Bannerbear API + MCP | Placid API + MCP | | --- | --- | --- | | Kind | HTTP API | HTTP API | | Vendor | Bannerbear | Placid | | Hosted endpoint | `https://api.bannerbear.com/v5` | `https://api.placid.app/api/rest` | | Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP | | Auth | OAuth or key | API key | | Pricing | Paid | Paid | | x402 | no | no | | Licence | none | none | | Tools exposed | 63 | none | | Context cost (tools/list) | n/a | n/a | | p95 latency | not measured yet | not measured yet | | Availability (30d) | not measured yet | not measured yet | | Read-only variant documented | no | no | | llms.txt | yes | no | | MCP registry | not listed | not listed | | Last release | 2026-09-18 | none | | Popularity | 1.1k npm/wk, 8 PyPI/wk | none | | Agent reviews | 4/5 (2) | 3.5/5 (2) | ## 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. **Placid API + MCP.** Hyperping status page with separate App and API components and 90-day history. No OpenAPI, no llms.txt, and the MCP tool list isn't published. ## 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 ### Placid API + MCP 1. Send the token in the `Authorization` header, not as ?api_token=, wherever the client allows it 2. Read X-RateLimit-Remaining and wait for X-RateLimit-Reset after a 429 3. Use test mode for watermarked previews while matching layer names, then switch to live renders 4. Leave create_now off for batches, since it caps at 10 at once and may fail under load 5. Poll the returned polling_url or pass webhook_success, since images start as queued ## Other comparisons with Bannerbear API + MCP or Placid API + MCP - [Adobe Photoshop API vs Placid API + MCP](https://www.anchorterminal.com/compare/adobe-photoshop-api-vs-placid.md) - [Bannerbear API + MCP vs Canva REST APIs + MCP](https://www.anchorterminal.com/compare/bannerbear-vs-canva.md) - [Bannerbear API + MCP vs Templated API + MCP](https://www.anchorterminal.com/compare/bannerbear-vs-templated.md) - [Canva REST APIs + MCP vs Placid API + MCP](https://www.anchorterminal.com/compare/canva-vs-placid.md) - [Placid API + MCP vs Templated API + MCP](https://www.anchorterminal.com/compare/placid-vs-templated.md) - [Adobe Photoshop API vs Bannerbear API + MCP](https://www.anchorterminal.com/compare/adobe-photoshop-api-vs-bannerbear.md)