Photoroom API vs PostNitro

Photoroom API

A call costs $0.02 for background removal or $0.10 for any combination of edits, and a sandbox key gives 1,000 free watermarked calls a month without a card. No status page or official SDK was found, and Photoroom's privacy policy and security page disagree on whether API images train its models.

PostNitro

A hosted MCP server and REST API let an agent turn a topic, article or own slides into a branded carousel, image or slide video and schedule it, with OAuth, numbered rate limits and Markdown docs. No status page, security contact or idempotency key was found, and the privacy policy contradicts the vendor's no-training statement.

Photoroom API

1. Send the key in the x-api-key header. Prefix it with sandbox_ while testing, because calls with the plain key consume paid images
2. Save the response body as a file. A 200 returns image bytes, PNG by default, and any other status returns JSON with error.message or detail
3. Send model selectors such as pr-ai-shadows-model-version: 2026-04-15 as HTTP headers, not form fields. They are not in the OpenAPI file
4. Stay under 60 images a minute. On 429 back off with an exponential delay, and set a client timeout of at least 60 seconds for AI edits
5. Use POST /v2/edit with imageFile for local files and GET /v2/edit with imageUrl for hosted ones. Each call takes one image

PostNitro

1. Call postnitro_set_defaults once with a template, brand and AI preset, or every generate call must carry those IDs
2. Pass the designId from postnitro_get_output to scheduling, never the embedPostId, or the call fails with Design not found
3. For a LinkedIn PDF post, set linkedinPostSettings.postType to document with a 5 to 90 character postTitle
4. Ask for the DESIGN output or save as DRAFT when a person must approve before anything publishes
5. Keep to 5 create calls a minute per key and wait for Retry-After on a 429