FLORA vs Stability AI Image API

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.

Stability AI Image API 8

The newest image change we can date is SD 3.5 Flash, added to Stability's API notebooks on 31 July 2025 (commit 2fefbb6); the notebooks' only later work is the Stable Audio 3 examples on 14 May 2026, not images, read from a clone on 5 November 2026. More than 180 days (0). No image entries to count in the 90 days from 12 August (0). Public release notes and support, not tested (5). The official Python SDK is the gRPC client, v0.8.6 on 9 May 2024 (3). Nothing current to assess (0). Release notes per the 1 October check, not re-read on 10 November 2026 (terms pause). 0 + 0 + 5 + 3 + 0 = 8.

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.

Stability AI Image API 10

No public OpenAPI file a page we read links. The API reference draws Stability's OpenAPI document from the API host by script, which this run doesn't count (0). No llms.txt; platform.stability.ai/llms.txt returned the docs app shell (0). Endpoint descriptions, typed inputs with enums and examples were read only from that reference, so those lines are 0, 0 and 0, as for Stable Audio. Dated release notes exist, though they render only with JavaScript (10, held). Per the 30 September to 2 October 2026 checks, not re-read on 10 November 2026 (Stability's terms bar automated access to its websites and Services). 0 + 0 + 0 + 0 + 0 + 10 = 10.

FLORA 68

MCP reading for context cost. 59 tools (56 callable by the model) with no toolsets or read-only subset; since 23 September 2026 the list is filtered to the account's access and flora_list_tools returns what the connection has (7 of 25). Cursor pagination with limit 1 to 100 on 10 REST list endpoints, history filters by workspace, project and status, include_inputs off by default, per-node and per-slide document reads, and up to 20 runs read in one call (17 of 20). One REST error envelope with code, message and field errors, retryability per code, a Flora-Request-Id, MCP failures grouped into retry now, retry later, change input and report, and retired tool names answering with their replacement (18 of 20). Idempotency-Key on every mutating REST request and a body key on Technique runs; every MCP tool carries readOnlyHint and destructiveHint annotations and spending tools are marked destructive; quote: true prices before running; the MCP create call has no idempotency key (16 of 20). Few required parameters (project_id, type, prompt, with the workspace resolved from the project) and an official TypeScript SDK and a Go CLI, but no SDK in a second language (10 of 15). 7+17+18+16+10 = 68.

Stability AI Image API 5

Response formats (raw bytes with accept image/* or base64 JSON), format and aspect-ratio controls, the async job model and defaults were read only from the script-drawn API reference, so the context, pagination, errors and idempotency lines are 0, as for Stable Audio. The 1 October check's 8 for errors rested on nothing it read. The only official SDK is the legacy gRPC client, stability-sdk v0.8.6 of 9 May 2024, read from its repository (5). Per the 30 September to 2 October 2026 checks, not re-read on 10 November 2026 (Stability's terms bar automated access to its websites and Services). 0 + 0 + 0 + 0 + 5 = 5.

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.

Stability AI Image API 30

One API key per account from the platform page, no scopes found (20). No least-privilege mode or spend cap found (0). Returns generated images only (10). No per-call log found (0). No security.txt, and no bug bounty or certification found (0). Per the 30 September to 2 October 2026 checks, not re-read on 10 November 2026 (Stability's terms bar automated access to its websites and Services). 20 + 0 + 10 + 0 + 0 = 30.

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.

Stability AI Image API 35

status.stability.ai, as read for Stable Audio on 2 October, runs on incident.io with one component, 'Stability.ai Platform & Services', and nothing specific to the image API (15 of 20). Its feed held one incident in the record, elevated 500s on generation endpoints across the API Platform, Brand Studio and Stable Audio on 14 September 2026. The 'major' label and the 4 hours 8 minutes came from the status page's incidents JSON, which is struck, and the feed publishes no duration, so it could be minor or one major (15, as Stable Audio). The 12 August to 10 November window is read only to 2 October, and a partly unread window keeps the recorded award. The limit of 150 requests every 10 seconds and the 60-second lockout on a 429 came from the API reference, which draws Stability's OpenAPI document from the API host by script, the reading struck for Stable Audio, so neither line is met (0 and 0). No SLA (0). The endpoints agents call sit under /v2beta (5, a held partial). Per the 30 September to 2 October 2026 checks, not re-read on 10 November 2026 (Stability's terms bar automated access to its websites and Services). 15 + 15 + 0 + 0 + 0 + 5 = 35.

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.

Stability AI Image API 60

No x402, MPP or L402 (0). Fixed credit prices per call published at $0.01 a credit (20). 25 free credits on sign-up (20). Browser sign-up (0). Per the 30 September to 2 October 2026 checks, not re-read on 10 November 2026 (Stability's terms bar automated access to its websites and Services). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.