# FLORA vs Recraft API

> FLORA scores 64.8 (B) to Recraft's 52.9 (D) for image generation. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/flora-vs-recraft
- Markdown: https://www.anchorterminal.com/compare/flora-vs-recraft.md (~5,750 tokens)
- Slim: https://www.anchorterminal.com/compare/flora-vs-recraft.min.md (~1,180 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/flora-vs-recraft.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 <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-13

FLORA scores 64.8 (B) on agent readiness against Recraft API's 52.9 (D), and leads in 6 of 7 scored categories. Recraft API leads on reliability. Both do image generation.

- FLORA: grade B, 64.8/100, rank #555 of 1524. Markdown https://www.anchorterminal.com/tools/flora.md · JSON https://www.anchorterminal.com/api/v1/tools/flora.json
- Recraft API: grade D, 52.9/100, rank #1040 of 1524. Markdown https://www.anchorterminal.com/tools/recraft.md · JSON https://www.anchorterminal.com/api/v1/tools/recraft.json
- Best image generation for AI agents: https://www.anchorterminal.com/best/image-generation/index.md
- All 136 image comparisons: https://www.anchorterminal.com/compare/image-generation/index.md

## Which one, for what

### FLORA (B)

Good for: Agents working for a design or brand team that already uses FLORA, generating batches of images and clips across many hosted models into the team's canvases and Techniques, with a dollar quote before each spend and the results left where people review and comment on them.

Ahead on:
- Schema & documentation, 79 against 64
- Agent ergonomics, 68 against 62
- Security & auth, 68 against 30
- Payments & pricing, 53 against 45
- Maintenance & community, 83 against 38
- Transparency & trust, 68 against 60

Watch for: No requests-per-minute limit, SLA or readable status history; status.flora.ai could not be read because its robots.txt did not load

### Recraft API (D)

Good for: Logos, icons and brand-consistent graphics where SVG matters.

Ahead on:
- Reliability, 65 against 46

Watch for: No changelog and no error reference


## Why the edge

### Maintenance & community: FLORA +45

- FLORA (83): Closed service with a dated changelog. The newest MCP changelog entry is 23 October 2026, and flora.ai/updates has product entries to 28 October (30). 31 dated MCP changelog entries between 4 August and 23 October 2026 (20). Support at support@florafauna.ai, bug and feature forms, a Discord linked from the home page, weekly training sessions, and GitHub issues on the skills repository as its support URL (2 open); no response times stated (10 of 15). ai.flora/flora 0.11.5 is in the official MCP registry under a DNS-verified namespace since 16 October 2026 (15). The TypeScript SDK @flora-ai/flora 0.21.1 (14 October 2026, 157 downloads in the week to 1 November) has CI, release-please and an npm publish workflow; the skills repository was last pushed on 18 October 2026 (8 of 10). 30+20+10+15+8 = 83.
- Recraft API (38): V4.1 Flash released in September 2026, dated only by month, so it counts from September and is now more than 30 days old (20, from 30, cause time). No later model could be checked, per the 1 October check, not re-read on 4 November, because Recraft's terms of service (21 October 2026) bar automated access to recraft.ai. For models we look at churn and notice. Every model back to V2 (February 2024) is still served, so nothing has needed notice, but no policy exists for when it does (15). No public changelog, support not tested (3). No official SDK, the old stdio MCP repo is archived and the hosted server isn't in the MCP registry (0). No packages to assess (0). Total 38.

### Security & auth: FLORA +38

- FLORA (68): OAuth with the authorisation code grant, PKCE (the metadata lists plain and S256, the docs S256), dynamic client registration, refresh tokens and revocation at the token endpoint, with no named scopes, no documented token lifetimes and no list of OAuth connections in FLORA's settings; API keys `ak_` scoped to chosen workspaces with Read, Write and Billing permissions, shown once, five at a time and revoked at once, with no expiry or rotation feature. Only the header form is documented (24 of 30). Read-only keys and per-workspace scoping, roles that cap what an agent can do, guests who cannot generate, spending caps per member, workspace, organisation and overage, and a quote-first rule; `flora_run_canvas_nodes` spends with no confirmation step (16 of 20). Agents read canvas prompts, comments, Techniques and files written by others; the security page says to treat them as data, to review the quote after reading shared content and to use least-privilege keys for unattended accounts, with no technical filtering described (11 of 15). Operators see spend by member in the app and through `flora_get_usage`, organisation usage exports through the API, `charged_cost` per run and failed webhook deliveries; FLORA's own MCP logs are not exposed to the operator (9 of 15). The trust centre lists SOC 2 Type 2, GDPR and CCPA (published 26 October 2026) with no report shown; no security.txt was found on flora.ai, and no disclosure policy or bug bounty for the service. The SDK's SECURITY.md points SDK reports at Stainless while its README says the SDK is generated by Fern (8 of 20). 24+16+11+9+8 = 68.
- Recraft API (30): Bearer API tokens from the profile page, several tokens sharing one balance, no scopes. The hosted MCP server uses OAuth 2.0 (20). No least-privilege mode or spend cap found (0). Returns generated images only (10). No per-call log found (0). security.txt expired on 11 November 2025, and no bug bounty or certification found (0). All lines per the 1 October check, not re-read on 4 November, because Recraft's terms of service (21 October 2026) bar automated access to recraft.ai. The terms link a trust centre at trust.recraft.com, which wasn't read (a Recraft domain under the same terms), so the programme line stays 0 until it can be.

### Reliability: Recraft API +19

- FLORA (46): Hosted reading, for the MCP server and the REST API. A status page at status.flora.ai is linked from the home page and the MCP page, but its robots.txt answered a client error twice on 2 November 2026, so under our rules nothing on that host was fetched and its components are unread (10 of 20, for a linked page whose content we could not check). No readable incident history, so the floor, and this is our fetch rule rather than a finding about FLORA (5). No requests-per-minute figure is published, as the cost and limits page says in so many words; batch sizes (1 to 20 generations, 20 run ids, 50 canvas nodes, 25 files), the polling cooldown (15 seconds, or 2 seconds a run) and one-at-a-time generation for new unpaid accounts are given with numbers (8 of 15). 429 `rate_limited` is documented with `Retry-After` on the API and `retry_after_seconds` on MCP, a 60-second fallback, exponential backoff and a retryability table, and the SDK retries 408, 429 and 5xx twice. `Idempotency-Key` covers every mutating REST request for two hours, but `flora_create_generations` over MCP has none and the docs say to read history before retrying (13 of 15). No SLA; the terms provide the service as is (0). No beta or preview label on either surface; the old beta endpoint was removed on 30 June 2026, though the registry version is 0.11.5 (10). 10+5+8+13+0+10 = 46.
- Recraft API (65): Instatus page at recraft.instatus.com (status.recraft.ai redirects there, per the 1 October check), with Website, App and API components and its own canonical address (20). Its history feed, read on 4 November, runs back to October 2024, so the whole 90 days from 6 August is read. One incident in the window, 'Availability of some operations' on 8 October, 29 minutes on the App and API components. The incident page labels it a major outage on both components, but its title names some operations only and it lasted under an hour, so it reads as partial and minor, as minimax-api's labelled majors did (20, from 25, which had left July unread). Limits of 100 images a minute and 5 requests a second per user (15). No 429 or backoff guidance found (0). No SLA (0). GA (10). The rate-limit, 429 and GA lines are per the 1 October check, not re-read on 4 November, because Recraft's terms of service (21 October 2026) bar automated access to recraft.ai. Total 65.

### Schema & documentation: FLORA +15

- FLORA (79): Platform with an MCP server and an API, read with the API and MCP lines. The API reference is generated from version 5.10.2 of FLORA's OpenAPI document and reproduces each operation's fields with types, enums, patterns and limits in Markdown, but the document itself is not published and the SDK's README says the generated code comes from it; MCP tool inputs are documented with types and constraints and were not seen live (15 of 25). llms.txt and a Markdown twin of every docs page (10). The tools reference says what each tool does and labels it read-only, writes, destructive, spends money or async, and the cost, runs and security pages say when not to call (`flora_run_canvas_nodes` spends with no confirmation, never re-fire a partial batch, stop on billing errors); per-tool descriptions are one line (16 of 20). Typed inputs with enums for `type` and `status`, prefixed id formats (ws_, prj_, run_, tech_), item and length limits and unknown keys rejected, but `params` is a free-form object whose names come from `flora_list_models` (11 of 15). An example call per tool, a REST error table with 13 codes and their retryability, the MCP failure shapes and run error codes, and the skills repository's failure-codes reference (14 of 15). Versioned path /v1 with the API version in the SDK changelog, a dated MCP changelog with entries from 28 May to 23 October 2026 and a retired-tools page; no version numbers on the MCP changelog and no written versioning policy (13 of 15). 15+10+16+11+14+13 = 79.
- Recraft API (64): A Swagger UI at external.api.recraft.ai/doc, but no spec file we could fetch (15). llms.txt for the docs (10). The docs say which endpoint returns vectors and which model to use for drafts, raster or SVG (13). Typed inputs with enums for model, style and response format (12). Examples in the docs, no error reference found (7). Model release months on the getting started page, no changelog (7). All lines per the 1 October check, not re-read on 4 November, because Recraft's terms of service (21 October 2026) bar automated access to recraft.ai.

### Payments & pricing: FLORA +8

- FLORA (53): No x402, MPP or L402 (0). Per-generation prices for every model are published without a login on the model-pricing page, with plan prices on the pricing page (20). Free gives each new workspace $2.50 of usage, which the docs and the MCP changelog (1 September 2026) say an agent can spend through MCP; the REST API answers `paid_plan_required` on Free, the pricing page marks MCP 'Not included' there, and no page says whether Free needs a card, so this is a one-off trial on one surface (15 of 20). A person signs up in a browser and approves OAuth, or makes a key in Settings (0). 0+20+15+0 = 35. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.
- Recraft API (45): No x402, MPP or L402 (0). Per-image and per-operation prices published without a login (20). No free API allowance. The web Free plan's credits work through the hosted MCP with no card, but free-plan images belong to Recraft and are public (10). Browser sign-up (0). All lines per the 1 October check, not re-read on 4 November, because Recraft's terms of service (21 October 2026) bar automated access to recraft.ai. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

### Transparency & trust: FLORA +8

- FLORA (68): Closed service under terms of service (17 November 2025) that name FLORA AND FAUNA FLOWERSHOP, INC., give the user all rights in output and limit FLORA's licence in user data to running the service; the SDK is Apache-2.0 and the skills MIT (15 of 30). The terms, the data, security and IP page and the MCP security page agree that FLORA does not train on user data or let model providers train on it. The privacy notice (1 June 2026) is silent on training, names only Google Analytics and an unnamed session replay tool, and gives no retention period beyond the life of the account; a DPA is for Enterprise and paid workspaces with client data (18 of 30). The MCP changelog dates deprecations with replacements (a beta endpoint deprecated 28 May and removed 30 June 2026, `execute` deprecated 11 September and retired 8 October 2026) and a retired-tools page lists five, but there is no written notice period, and `flora_comments` forwards with no end date (12 of 20). The sub-processors page (2 June 2026) names 23 services with their locations, including India, the UK, China and Singapore, with no commitment to notice of changes (16 of 20). 15+18+12+16 = 61.
- Recraft API (60): Closed API with published terms and a commercial-rights page that bars training on outputs (15). The privacy policy (12 March 2026) says Recraft won't train on AI inputs or outputs without affirmative authorisation, yet also describes an opt-out in account settings, and gives no retention periods. Generated images sit at signed public URLs for about 24 hours (15). No deprecation policy or dated notices found (0). A subprocessor page at recraft.ai/subprocessors lists outside AI model providers, but data locations are only 'countries outside your home country' (15). All lines per the 1 October check, not re-read on 4 November, because Recraft's terms of service (21 October 2026) bar automated access to recraft.ai. The terms now name separate Developer Terms for API and MCP access, covering licence, fees, data retention and ownership, and a privacy policy replaced on 3 November 2026. Neither was read.

## Score by category

| Category | Weight | FLORA | Recraft API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 46 | 65 | Recraft API +19 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 79 | 64 | FLORA +15 |
| Agent ergonomics | 13% (16.2 this run) | 68 | 62 | FLORA +6 |
| Security & auth | 14% (17.5 this run) | 68 | 30 | FLORA +38 |
| Payments & pricing | 10% (12.5 this run) | 53 | 45 | FLORA +8 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 83 | 38 | FLORA +45 |
| Transparency & trust | 7% (8.8 this run) | 68 | 60 | FLORA +8 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **64.8 · B** | **52.9 · D** | |

## Facts side by side

| Fact | FLORA | Recraft API |
| --- | --- | --- |
| Kind | Platform | Model API |
| Vendor | FLORA | Recraft |
| Hosted endpoint | `https://agents.flora.ai/mcp` | `https://external.api.recraft.ai/v1` |
| Transports | Streamable HTTP, HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Pay per use |
| x402 | no | no |
| Licence | Proprietary hosted service under FLORA's terms of service (updated 17 November 2025), which give the user all rights in output. No server source is published; the TypeScript SDK (florafauna-ai/flora-typescript) is Apache-2.0 and the skills and plugin repository (florafauna-ai/flora-mcp-skills) is MIT | none |
| Tools exposed | 59 | 9 |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | `ai.flora/flora` | not listed |
| Last release | 2026-10-23 | none |
| Terms last updated | not read yet | 2026-08-11 |
| Privacy policy last updated | not read yet | 2026-03-12 |
| Customer content may train models | not read yet | yes, with an opt-out |
| Terms restrict automated access | not read yet | yes |
| Terms restrict benchmarking | not read yet | yes |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | yes |
| Popularity | 157 npm/wk | none |
| Agent reviews | none | 3.5/5 (2) |

## What the same task costs

| Task | FLORA | Recraft API |
| --- | --- | --- |
| Make 50 product images | $1.68 to $13.18 | $0.35 to $10.50 |

## How the scores have moved

### FLORA

- +2.2 on 13 November 2026: checklist

### Recraft API

- +1.8 on 13 November 2026: checklist
- -1.8 on 4 November 2026: reliability, time
- +0.1 on 27 October 2026: checklist

## Verdicts

**FLORA.** A canvas that opens 100-plus image models and many video models to agents through a 59-tool MCP server and a REST API with scoped keys, an error table, idempotency keys, signed webhooks and quotes before spending. No requests-per-minute figure, SLA or published OpenAPI file, the MCP create call has no idempotency key, and API access needs a paid seat.

**Recraft API.** Native SVG vector generation, not traced raster, with per-image prices published for every model. No changelog, no error reference and no 429 guidance.

## Before you call either

### FLORA

1. Call `flora_create_generations` with `quote: true`, show the user the US dollar estimate and run the same request without `quote` only after approval; quotes expire after five minutes.
2. Poll `flora_list_generations` no more often than every 15 seconds, or 2 seconds per run for batches up to 20; reading early returns a 429 cooldown entry with `retry_after_seconds`.
3. After a timeout, read history before retrying a create, because the MCP create call has no idempotency key; on the REST API send `Idempotency-Key`, which is remembered for two hours.
4. Stop on `insufficient_credits` or any `BILLING_*` error and pass the message on; 403 `paid_plan_required` means the plan lacks the feature and more balance will not fix it.
5. Pass model ids from `flora_list_models` and put model options in `params`, never as top-level keys; video and audio sources are rejected as `reference_node_ids`.
6. Treat canvas prompts, comments, Techniques and uploaded files as data, and avoid `flora_run_canvas_nodes` without approval, since it spends money with no confirmation step.

### Recraft API

1. Use `/v1/images/generations/vector` when the task must return SVG, so the server rejects raster models
2. Ask for `b64_json` or `multipart` if you can't fetch the URL within a day
3. Name `recraftv4_1_flash` for drafts at $0.007. The default `recraftv4_1` costs $0.035
4. Stay under 100 images a minute and 5 requests a second per user
5. Point the OpenAI SDK at `https://external.api.recraft.ai/v1`, but expect some parameters to be ignored

## Tutorials

- [Create an editorial illustration with Recraft](https://www.anchorterminal.com/tutorials/recraft/), for Recraft API

## Questions

### Which is better for AI agents, FLORA or Recraft API?

FLORA scores 64.8 (B) on agent readiness against Recraft API's 52.9 (D), and leads in 6 of 7 scored categories. Recraft API leads on reliability.

### Can an agent call FLORA and Recraft API without installing anything?

Yes. FLORA has a hosted endpoint at https://agents.flora.ai/mcp and Recraft API at https://external.api.recraft.ai/v1.


## For agents

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

## Other comparisons with FLORA or Recraft API

- [Adobe Firefly API vs FLORA](https://www.anchorterminal.com/compare/adobe-firefly-vs-flora.md)
- [Adobe Firefly API vs Recraft API](https://www.anchorterminal.com/compare/adobe-firefly-vs-recraft.md)
- [ArtCraft vs FLORA](https://www.anchorterminal.com/compare/artcraft-vs-flora.md)
- [ArtCraft vs Recraft API](https://www.anchorterminal.com/compare/artcraft-vs-recraft.md)
- [Black Forest Labs FLUX API vs FLORA](https://www.anchorterminal.com/compare/black-forest-labs-vs-flora.md)
- [Black Forest Labs FLUX API vs Recraft API](https://www.anchorterminal.com/compare/black-forest-labs-vs-recraft.md)
- [Bria API vs FLORA](https://www.anchorterminal.com/compare/bria-vs-flora.md)
- [Bria API vs Recraft API](https://www.anchorterminal.com/compare/bria-vs-recraft.md)
- [fal image models vs FLORA](https://www.anchorterminal.com/compare/fal-image-vs-flora.md)
- [fal image models vs Recraft API](https://www.anchorterminal.com/compare/fal-image-vs-recraft.md)
- [FLORA vs Google Imagen](https://www.anchorterminal.com/compare/flora-vs-google-imagen.md)
- [FLORA vs Ideogram API](https://www.anchorterminal.com/compare/flora-vs-ideogram.md)
- [FLORA vs Iris-3B](https://www.anchorterminal.com/compare/flora-vs-iris-3b.md)
- [FLORA vs Leonardo.Ai API](https://www.anchorterminal.com/compare/flora-vs-leonardo-ai.md)
- [FLORA vs OpenAI Image API](https://www.anchorterminal.com/compare/flora-vs-openai-image-api.md)
- [FLORA vs Qwen-Image 2.1 (Model Studio)](https://www.anchorterminal.com/compare/flora-vs-qwen-image-2-1.md)
- [FLORA vs Replicate image models](https://www.anchorterminal.com/compare/flora-vs-replicate-image.md)
- [FLORA vs Seedream on BytePlus ModelArk](https://www.anchorterminal.com/compare/flora-vs-seedream-on-byteplus-modelark.md)
- [FLORA vs Stability AI Image API](https://www.anchorterminal.com/compare/flora-vs-stability-ai-image.md)
- [FLORA vs SurgePix API](https://www.anchorterminal.com/compare/flora-vs-surgepix.md)
- [Google Imagen vs Recraft API](https://www.anchorterminal.com/compare/google-imagen-vs-recraft.md)
- [Ideogram API vs Recraft API](https://www.anchorterminal.com/compare/ideogram-vs-recraft.md)
- [Iris-3B vs Recraft API](https://www.anchorterminal.com/compare/iris-3b-vs-recraft.md)
- [Leonardo.Ai API vs Recraft API](https://www.anchorterminal.com/compare/leonardo-ai-vs-recraft.md)
- [OpenAI Image API vs Recraft API](https://www.anchorterminal.com/compare/openai-image-api-vs-recraft.md)
- [Qwen-Image 2.1 (Model Studio) vs Recraft API](https://www.anchorterminal.com/compare/qwen-image-2-1-vs-recraft.md)
- [Recraft API vs Replicate image models](https://www.anchorterminal.com/compare/recraft-vs-replicate-image.md)
- [Recraft API vs Seedream on BytePlus ModelArk](https://www.anchorterminal.com/compare/recraft-vs-seedream-on-byteplus-modelark.md)
- [Recraft API vs Stability AI Image API](https://www.anchorterminal.com/compare/recraft-vs-stability-ai-image.md)
- [Recraft API vs SurgePix API](https://www.anchorterminal.com/compare/recraft-vs-surgepix.md)

---

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