# Pictify

> Pictify renders HTML, URLs and saved templates into PNG, JPG or WebP images, PDFs, GIFs and MP4 video through a REST API, official SDKs in four languages and an MCP server.

- Canonical: https://www.anchorterminal.com/tools/pictify
- Pricing: https://www.anchorterminal.com/tools/pictify#pricing
- Reviews: https://www.anchorterminal.com/tools/pictify#reviews
- Markdown: https://www.anchorterminal.com/tools/pictify.md (~6,900 tokens)
- Slim: https://www.anchorterminal.com/tools/pictify.min.md (~1,530 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/tools/pictify.json (this page as data, same URL with Accept: application/json)
- 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 pictify.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

## Overview

**Grade C · 55.7/100 · rank #856 of 1486 · #7 in Programmatic asset production · not agent-ready · confidence medium**


## Assessment

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.

## Facts

| Field | Value |
| --- | --- |
| Vendor | Pictify.io (https://pictify.io) |
| Kind | HTTP API |
| Category | Programmatic asset production (https://www.anchorterminal.com/categories/design-assets) |
| Transport | HTTP, stdio, Streamable HTTP |
| Endpoint | `https://api.pictify.io` |
| Auth | OAuth or key · API keys (`pic_live_` plus 64 hex characters since September 2026) created in the dashboard and sent as `Authorization: Bearer`. Keys can be rotated (a replacement is made, then the old key revoked) or revoked at once. No scopes. The local MCP server reads `PICTIFY_API_KEY`; a hosted MCP endpoint at mcp.pictify.io advertises OAuth with an `mcp:tools` scope, which the docs don't describe. |
| Pricing | Freemium (Freemium) · Free $0 with 50 renders a month, 3 saved templates and no card. Basic $19 a month ($15 yearly) with 1,000 renders and $0.02 per extra render, Pro $49 ($39) with 10,000 and $0.01, Business $249 ($199) with 40,000 and $0.005. One render pool covers images, PDF pages, GIFs and video. Failed requests aren't billed. |
| x402 | No · Subscriptions with overage billing. No x402, MPP or L402 in the OpenAPI, the docs, llms.txt or pricing.md (checked 2026-11-06). Exhausted credits return 429 or 402 with `quota_exceeded` and no payment requirements. |
| Licence | MIT for the MCP server. The Pictify API is a closed service under terms last updated 18 July 2024 |
| Tools exposed | 25 |
| Packages | npm: `@pictify/mcp-server` |
| MCP registry name | `io.github.pictify-io/mcp` |
| Source | https://github.com/pictify-io/mcp |
| Docs | https://docs.pictify.io |
| llms.txt | https://docs.pictify.io/llms.txt |
| Last release | 2026-09-20 |
| npm downloads / week | 55 |
| Surface listed | The REST API at api.pictify.io and the @pictify/mcp-server package (2.0.0), read from docs.pictify.io, its OpenAPI file, pictify.io's llms.txt, pricing.md, terms and privacy policy, a shallow clone of github.com/pictify-io/mcp, npm and the MCP registry on 6 November 2026. No account was made and the package was not run |
| Which site | pictify.io, served through Cloudflare, with docs on Mintlify at docs.pictify.io and the API at api.pictify.io. The npm package, the registry entry and the GitHub organisation pictify-io all point to pictify.io |
| MCP tools | 25 in the 2.0.0 source, for images, templates, batch renders, renders and video templates. The canvas and GIF-creation tools were removed on 19 September 2026 |
| Outputs | PNG, JPG, WebP, single and multi-page PDF, GIF and MP4, hosted on a CDN |
| MCP analytics | PostHog at us.i.posthog.com, on by default. Records tool name, arguments, result, timing, errors, client and, when a key resolves, email and plan. Off with `PICTIFY_ANALYTICS_DISABLED=1`, per the README |
| Operator | The terms and privacy policy name only Pictify.io, under United States law. The npm maintainer and the MCP repository's committer is Suyash Thakur |
| Capabilities | design.render, design.templates, pdf.generate, video.generate |
| Tags | hosted, openapi, llms-txt, mcp, stdio, mcp-registry, api-key, freemium, free-tier, no-card, webhooks, telemetry |
| JSON | https://www.anchorterminal.com/api/v1/tools/pictify.json |

## Score breakdown (methodology v0.7, October 2026 research run)

Assessed 2026-11-06 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points.

| Category | Weight | This run | Score (0–100) | Points |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 20 | 45 | 9.0 |
| Performance | 10% | pending | pending | n/a |
| Schema & documentation | 13% | 16.2 | 88 | 14.3 |
| Agent ergonomics | 13% | 16.2 | 74 | 12.0 |
| Security & auth | 14% | 17.5 | 45 | 7.9 |
| Payments & pricing | 10% | 12.5 | 40 | 5.0 |
| Task success | 10% | pending | pending | n/a |
| Maintenance & community | 7% | 8.8 | 68 | 6.0 |
| Transparency & trust (editorial 39, provenance 64) | 7% | 8.8 | 52 | 4.5 |
| Negative events | up to −15 | up to −15 | Workflows (CSV or webhook runs with per-recipient email delivery) were retired in September 2026 per the changelog (https://docs.pictify.io/resources/changelog.md), while pictify.io's llms.txt still calls the Render-to-Recipient workflow Pictify's core pattern and pricing.md (last updated 9 August 2026) still says per-recipient email delivery is included on paid workflow runs (https://pictify.io/llms.txt, https://pictify.io/pricing.md), read 6 November 2026. A retired feature still advertised, -3.  | -3 |
| **Total** | | | | **55.7 → C** |

### Why each score

- Reliability 45 (checked 2026-11-06): Hosted lines, for the REST API. The home page links a status page at status.pictify.io, but its robots.txt disallows every path, so its components and history weren't read. Half for a page that exists (10 of 20) and no readable history (5). Monthly render quotas are published per plan, and the docs say a few endpoints carry fixed per-minute limits without giving the numbers (5 of 15). Retry guidance is explicit. A 429 is told apart by `code`, rate-limit 429s send `x-ratelimit-*` and `retry-after`, a 5xx can be retried once, and generation is idempotent from the caller's side with failed requests unbilled (15). No SLA found (0). The API isn't labelled beta (10). 10 + 5 + 5 + 15 + 0 + 10 = 45.
- Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes.
- Schema & documentation 88 (checked 2026-11-06): 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.
- Agent ergonomics 74 (checked 2026-11-06): 25 MCP tools in the 2.0.0 source (15 for 11 to 30), with no toolsets or read-only subset (15). List endpoints page with `page` and `limit` (16 of 20). Error bodies carry `code` slugs such as `quota_exceeded`, `template_limit_reached` and `invalid_variable`, and the docs say which are retryable (18 of 20). Generation is safe to retry and failed calls bill nothing, but the MCP source sets no readOnlyHint or destructiveHint, and the delete tools for templates and video templates run without a confirmation step (10 of 20). Official SDKs for Node.js, Python, Go and Ruby, sensible defaults such as 1200 x 630 PNG (15). 15 + 16 + 18 + 10 + 15 = 74.
- Security & auth 45 (checked 2026-11-06): 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.
- Payments & pricing 40 (checked 2026-11-06): 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.
- Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored.
- Maintenance & community 68 (checked 2026-11-06): @pictify/mcp-server 2.0.0 published on 20 September 2026, 47 days before this check, with the changelog's newest entry dated September 2026 (20). Since 8 August, MCP versions 1.5.0 (8 August), 1.5.1 (11 August) and 2.0.0 (20 September), and changelog entries for August and September (20). GitHub issues weren't read, and the repository has one committer (5 of 25, unchecked). io.github.pictify-io/mcp is in the official MCP registry under the GitHub-verified namespace at 2.0.0, and official SDKs exist in four languages (15). CI builds and runs tests on push and pull requests (8 of 10). 20 + 20 + 5 + 15 + 8 = 68.
- Transparency & trust 52 (checked 2026-11-06): 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.

Fix list, everything this grade says the listing lacks, the biggest gain first (19 items). What it covers is at https://www.anchorterminal.com/fixes/pictify.md (JSON https://www.anchorterminal.com/fixes/pictify.json). The whole list for a coding agent comes from `POST https://www.anchorterminal.com/api/v1/fix-list` with `{"listing": "pictify", "plan": "read"}`, free while the beta runs

### What we couldn't check

- unchecked: the status page's components and incident history, because status.pictify.io's robots.txt disallows every path.
- unchecked: GitHub issues and response times on pictify-io/mcp.
- The per-minute rate limits on public rendering and previews have no published numbers.
- Who operates Pictify: the terms name only Pictify.io; the npm maintainer is Suyash Thakur.
- The hosted MCP endpoint at mcp.pictify.io (OAuth, `mcp:tools`) is in the registry entry's remotes but not in the docs.
- Disclosure: two requests reached status.pictify.io before its robots.txt (which disallows every path) was read. What they returned is not used.

### Sources

- OpenAPI 3.1: <https://docs.pictify.io/openapi/v1.yaml> (seen 2026-11-06)
- docs llms.txt: <https://docs.pictify.io/llms.txt> (seen 2026-11-06)
- site llms.txt: <https://pictify.io/llms.txt> (seen 2026-11-06)
- pricing (machine-readable): <https://pictify.io/pricing.md> (seen 2026-11-06)
- errors and retry guidance: <https://docs.pictify.io/api-reference/errors.md> (seen 2026-11-06)
- API overview, rate limits and credits: <https://docs.pictify.io/api-reference/overview.md> (seen 2026-11-06)
- API keys in the dashboard: <https://docs.pictify.io/dashboard/api-keys.md> (seen 2026-11-06)
- MCP server docs page: <https://docs.pictify.io/agent-integration/mcp-server.md> (seen 2026-11-06)
- changelog: <https://docs.pictify.io/resources/changelog.md> (seen 2026-11-06)
- MCP server source and README (shallow clone): <https://github.com/pictify-io/mcp> (seen 2026-11-06)
- npm package times: <https://registry.npmjs.org/@pictify%2fmcp-server> (seen 2026-11-06)
- official MCP registry entries: <https://registry.modelcontextprotocol.io/v0/servers?search=pictify> (seen 2026-11-06)
- terms: <https://pictify.io/terms> (seen 2026-11-06)
- privacy policy: <https://pictify.io/privacy> (seen 2026-11-06)
- hosted MCP protected-resource metadata: <https://mcp.pictify.io/.well-known/oauth-protected-resource> (seen 2026-11-06)

## Score history

Every move of a score since the listing was graded, newest first, with its cause. A score can't move without an entry here. JSON: https://www.anchorterminal.com/api/v1/tools/pictify/history.json

- 2026-11-06: graded 55.7 C (methodology 0.7)

## Who's behind it (provenance 64/100, checked 2026-11-06)

| Check | Finding | Points |
| --- | --- | --- |
| Legal entity named | not found | 0/20 |
| Domain age | pictify.io, registered 2024-02-18 (2 years) | 7/15 |
| Endpoint on the vendor's domain | api.pictify.io | 15/15 |
| Terms of service | read, states 6 of the 7 things a reader expects | 9.1/10 |
| Privacy policy | read, states 5 of the 8 things a reader expects | 7.8/10 |
| Status page | status.pictify.io | 10/10 |
| Changelog | published | 10/10 |
| security.txt | not found | 0/10 |
| People named | 1 named with their role, 1 with a public profile | 10/10 |
| Support route | a support address, help pages, a community | 5/5 |

The terms and privacy policy, both last updated 18 July 2024, name only Pictify.io and choose United States law. No company form or address is given. The npm package's maintainer is Suyash Thakur.

The terms forbid unauthorised collection of information from the Service. Public pages were read as data.

pictify.io/robots.txt allows all but the dashboard, login, signup, workspace, canvas, invite and /api/ paths, with Content-Signal search=yes, ai-input=yes, ai-train=yes. docs.pictify.io allows the docs. status.pictify.io/robots.txt disallows every path, so the status page's content wasn't used (one request reached it before its robots.txt was read, and what it returned was discarded).

RDAP gives pictify.io a registration date of 18 February 2024.

/.well-known/security.txt returns 404.

### Terms and privacy, as read

A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.

**Terms of service** (https://pictify.io/terms), read 2026-11-06, dated 2024-07-18, states 6 of the 7 things a reader expects.

- Gives the date it was last updated. Last updated 2024-07-18.
- Names the governing law or courts. The law of the United States.
- States a limit on its liability. Rules out indirect and consequential losses, with no cap named in this sentence.
- Says how changes to the terms are announced. Gives 30 days of notice before a change.
- Not found in the text. Refers to a service level or uptime commitment.

**Privacy policy** (https://pictify.io/privacy), read 2026-11-06, dated 2024-07-18, states 5 of the 8 things a reader expects.

- Gives the date it was last updated. Last updated 2024-07-18.
- Says how long data is kept. For as long as needed, with no period named.
- Not found in the text. Says whether personal data is sold or shared for advertising.
- Not found in the text. Says what rights people have over their data.
- Gives a privacy contact. Gives an email address, hidden from our reader by the page.
- Not found in the text. Says where data is transferred or stored.

## Humans behind the project (researched 2026-11-06 from public pages, not part of the grade)

### Key people

- Suyash Thakur, Maintainer of the Pictify MCP server and author of the Pictify blog. GitHub: https://github.com/suyash-thakur
- Note: The terms and privacy policy (18 July 2024) name the operator only as Pictify.io, with no company form, address or person. The npm package @pictify/mcp-server has the single maintainer suyash-thakur, every commit in github.com/pictify-io/mcp is by Suyash Thakur, his GitHub profile links pictify.io and he signs the Pictify blog posts, so he is listed as the server's maintainer; no first-hand page calls him a founder, so he isn't marked as one. Investors were looked for on the site, its sitemap, llms.txt, the legal pages, the repository and a web search on 6 November 2026; none is named.
- Pictify.io: GitHub https://github.com/pictify-io

### Getting support

- Support email: support@pictify.io
- Help: https://docs.pictify.io/resources/troubleshooting
- Help: https://status.pictify.io
- Community (MCP server issues): https://github.com/pictify-io/mcp/issues
- Sources: https://pictify.io/terms, https://pictify.io/privacy, https://registry.npmjs.org/@pictify%2fmcp-server, https://github.com/pictify-io/mcp, https://github.com/suyash-thakur, https://pictify.io/blogs, https://github.com/pictify-io

## Live (updated 2026-11-07 18:20 UTC)

- Right now: up, HTTP 404, 260 ms, checked 2026-11-07 18:20 UTC (get on `https://api.pictify.io`)
- Uptime 24h 100.0% (200 probes) · 30 days 100.0% (200 probes) · p50 247 ms · p95 416 ms
- Vendor status page: not read, no machine-readable status found
- mcp-registry `io.github.pictify-io/mcp` 2.0.0
- npm `@pictify/mcp-server` 2.0.0
- security.txt: none
- Watching changelog <https://docs.pictify.io/resources/changelog>
- Watching privacy <https://pictify.io/privacy>
- Watching terms <https://pictify.io/terms>
- Always current: https://www.anchorterminal.com/api/v1/live/pictify.json

## Probe metrics

Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.

## Prices

| Item | Price | Unit | Note |
| --- | --- | --- | --- |
| Extra render on Basic | $0.02 | per image | Basic $19 a month includes 1,000 renders; one pool for images, PDF pages, GIFs and video |
| Extra render on Pro | $0.01 | per image | Pro $49 a month includes 10,000 renders |
| Extra render on Business | $0.005 | per image | Business $249 a month includes 40,000 renders |

Across all listings: https://www.anchorterminal.com/prices/index.md

## Strengths

- Public OpenAPI 3.1, llms.txt and Markdown docs, with official SDKs in Node.js, Python, Go and Ruby
- Overage prices per render published without login, from $0.02 down to $0.005
- Free plan of 50 renders a month with no card and no watermark
- Error codes separate monthly quota from rate limits, and failed requests aren't billed
- MCP server in the official registry under the pictify-io GitHub namespace, latest 2.0.0

## Weaknesses

- The MCP server sends tool arguments, results and the account email to PostHog unless turned off
- Privacy policy and terms date from 18 July 2024 and name no company or processors
- Workflows were retired in September 2026 but llms.txt and pricing.md still describe them
- The MCP docs page lists 26 tools, some of them removed on 19 September 2026
- No key scopes or read-only key, and no security.txt or disclosure policy



## Before you call it (notes for agents)

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

## Connect

Install:

```bash
npx -y @pictify/mcp-server
```

Claude Code:

```bash
claude mcp add pictify -- npx -y @pictify/mcp-server
```

MCP client configuration:

```json
{
  "mcpServers": {
    "pictify": {
      "args": [
        "-y",
        "@pictify/mcp-server"
      ],
      "command": "npx",
      "env": {
        "PICTIFY_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}
```

Through letme: https://letme.dev/pictify. letme answers with the pick and how to call it direct. How it works: https://www.anchorterminal.com/letme/index.md

## Similar tools

Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.

| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |
| --- | --- | --- | --- | --- | --- | --- |
| Abyssale | B | 65.6 | 411 | design.render, design.templates, pdf.generate, video.generate | no | https://www.anchorterminal.com/tools/abyssale.md |
| Robolly | D | 48.4 | 1115 | design.templates, design.render, pdf.generate, video.generate | no | https://www.anchorterminal.com/tools/robolly.md |
| Shotstack | B | 67.3 | 333 | design.templates, design.render, video.generate | no | https://www.anchorterminal.com/tools/shotstack.md |
| Layerre | C | 57.6 | 785 | design.templates, design.render, pdf.generate | no | https://www.anchorterminal.com/tools/layerre.md |
| DynaPictures | E | 43.2 | 1239 | design.templates, design.render, pdf.generate | no | https://www.anchorterminal.com/tools/dynapictures.md |
| Pixelixe | F | 37.3 | 1355 | design.templates, design.render, pdf.generate | no | https://www.anchorterminal.com/tools/pixelixe.md |

## Panel reviews (0)

Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .

Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md

## Notable

- OpenAPI 3.1 with 20 paths for images, GIFs, PDFs, templates, batch renders, webhooks and data bindings (source: <https://docs.pictify.io/openapi/v1.yaml>)
- Errors carry stable codes such as `quota_exceeded`, and the docs say to check the code before retrying a 429, since a monthly quota never refills on retry (source: <https://docs.pictify.io/api-reference/errors.md>)
- Generation endpoints are idempotent from the caller's side and a failed request bills nothing, per the error docs (source: <https://docs.pictify.io/api-reference/errors.md>)
- The MCP server sends each tool call's name, arguments, result, client and, when the key resolves, the account email and plan to PostHog by default; `PICTIFY_ANALYTICS_DISABLED=1` turns it off (source: <https://github.com/pictify-io/mcp>)
- Workflows, the CSV and webhook runs with per-recipient email delivery, were retired in September 2026, while llms.txt still leads with that workflow (source: <https://docs.pictify.io/resources/changelog.md>)
- Official SDKs for Node.js, Python, Go and Ruby (source: <https://docs.pictify.io/llms.txt>)

- #7 of 18 in 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

## Compare

- [APITemplate.io vs Pictify](https://www.anchorterminal.com/compare/apitemplate-io-vs-pictify.md): F 30.1 vs C 55.7
- [Bannerbear API + MCP vs Pictify](https://www.anchorterminal.com/compare/bannerbear-vs-pictify.md): C 59.6 vs C 55.7
- [Canva REST APIs + MCP vs Pictify](https://www.anchorterminal.com/compare/canva-vs-pictify.md): B 67.3 vs C 55.7
- [Contentdrips API and MCP vs Pictify](https://www.anchorterminal.com/compare/contentdrips-vs-pictify.md): F 36.3 vs C 55.7
- [Creatomate vs Pictify](https://www.anchorterminal.com/compare/creatomate-vs-pictify.md): D 49.6 vs C 55.7
- [DynaPictures vs Pictify](https://www.anchorterminal.com/compare/dynapictures-vs-pictify.md): E 43.2 vs C 55.7
- [Layerre vs Pictify](https://www.anchorterminal.com/compare/layerre-vs-pictify.md): C 57.6 vs C 55.7
- [Photoroom API vs Pictify](https://www.anchorterminal.com/compare/photoroom-vs-pictify.md): D 53.5 vs C 55.7
- [Abyssale vs Pictify](https://www.anchorterminal.com/compare/abyssale-vs-pictify.md): B 65.6 vs C 55.7
- [Adobe Photoshop API vs Pictify](https://www.anchorterminal.com/compare/adobe-photoshop-api-vs-pictify.md): E 44 vs C 55.7
- [Osmo CLI vs Pictify](https://www.anchorterminal.com/compare/osmo-cli-vs-pictify.md): F 35.2 vs C 55.7
- [Pictify vs Pixelixe](https://www.anchorterminal.com/compare/pictify-vs-pixelixe.md): C 55.7 vs F 37.3
- [Pictify vs Placid API + MCP](https://www.anchorterminal.com/compare/pictify-vs-placid.md): C 55.7 vs E 43
- [Pictify vs PostNitro](https://www.anchorterminal.com/compare/pictify-vs-postnitro.md): C 55.7 vs D 52.6
- [Pictify vs Robolly](https://www.anchorterminal.com/compare/pictify-vs-robolly.md): C 55.7 vs D 48.4
- [Pictify vs Shotstack](https://www.anchorterminal.com/compare/pictify-vs-shotstack.md): C 55.7 vs B 67.3
- [Pictify vs Templated API + MCP](https://www.anchorterminal.com/compare/pictify-vs-templated.md): C 55.7 vs C 58.8

## Verify this listing

For the vendor. The badge or a plain link to this page verifies the listing, from a page on pictify.io or one of its subdomains, or the README at the root of github.com/pictify-io/mcp. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "pictify", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify

HTML badge:

```html
<a href="https://www.anchorterminal.com/tools/pictify"><img src="https://www.anchorterminal.com/badges/pictify.svg" alt="Pictify on Anchor Terminal" height="20"></a>
```

Markdown badge, for a README:

```markdown
[![Pictify on Anchor Terminal](https://www.anchorterminal.com/badges/pictify.svg)](https://www.anchorterminal.com/tools/pictify)
```

Plain link:

```html
<a href="https://www.anchorterminal.com/tools/pictify">Pictify on Anchor Terminal</a>
```

## Share this listing

For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Pictify is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.

- Dark: https://www.anchorterminal.com/assets/share/pictify-dark.png
- Light: https://www.anchorterminal.com/assets/share/pictify-light.png

---

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