Skip to content

v1.1.0

Choose a tag to compare

@qmt qmt released this 01 Oct 08:23
· 30 commits to main since this release
f05ecac

An audit of the npm page (2026-10-01, every claim checked against the code and Ideogram's documentation).

Changed

  • ideogram_edit posts to /v1/ideogram-v3/inpaint: Ideogram marks /v1/ideogram-v3/edit "Legacy: use inpaint instead. This endpoint will be removed in a future release" — same image, mask and prompt fields, same response. A test with a fake fetch pins the endpoint.
  • The per-image cap is 25 MB, Ideogram's documented maximum (it was 10 MB, called an API limit); the error names the real limit. A test pins both sides of the cap. ideogram_edit refuses image + mask at or over Ideogram's 50 MB request limit before uploading anything. A timed-out POST is no longer retried: the server may have accepted and billed it, and the multipart body (now up to 50 MB) would be sent again; connection failures and 429/5xx are retried as before, and a timed-out image download (an idempotent GET) still is. The pair is measured with stat before either file is read, with 64 KB reserved for the multipart overhead. The NETWORK_ERROR message names the failure (TimeoutError, TypeError).
  • Every public claim says what the code does: Ideogram 3.0 through the v1 API (Ideogram 4.x and the v2 API are not used; the v1 API keeps working with no announced sunset); the describe and upscale endpoints named as such; style_type defaults to GENERAL on the API side (the descriptions said AUTO); num_images and seed in every tool except describe; describe_model_version, negative_prompt, upscale's prompt and image_weight documented; API keys at ideogram.ai/platform (the old manage-api link answers 403); Node.js ≥ 22 stated; the ideogram-mcp command and a claude mcp add one-liner; npm test and npm run typecheck in Development; the mask has no "10 % black" rule; SECURITY.md labels the review history (1.0.0, April 2026) and says a symlinked parent directory is followed and that any readable image path the model names may be uploaded; "zero-trust" and "flagship" dropped; the npm and MCP registry descriptions agree.
  • package.json names the repository as git+https://… — the form npm publishes, so a publish prints no auto-correction.