mcp changelog

https://appscreenshotstudio.com/llms.txt

− - 28 templates built from 7 designs across 6 categories+ - 6 template designs, one per category (finance, fitness, productivity, travel, wellness, games and social), each in 4 device sizes

https://appscreenshotstudio.com/llms.txt

− - Making alternate versions of an existing set to test in Apple's Product Page Optimization (PPO): up to 3 per set, matching PPO's 3 treatments against the current page. Apple runs the test; this makes the treatments.− - Test variants: up to 3 alternates of a set for Apple's Product Page Optimization, as bold concepts (a different reason to install, ready in under a minute) or one change each (so a win shows what worked), compared on the real cards. Any that fail the readability and layout checks are refunded+ - Making alternate versions of an existing set to test in Apple's Product Page Optimization (PPO): up to 3 per set, matching PPO's 3 treatments against the current page, or up to 2 for a Google Play store listing experiment. The store runs the test and reports the result; this makes the treatments.+ - Test variants: up to 3 alternates of a set for Apple's Product Page Optimization (2 for a Google Play store listing experiment), as bold concepts (a different reason to install, ready in under a minute) or one change each (so a win shows what worked), compared on the real cards. Any that fail the readability and layout checks are refunded. In the web builder every version downloads as one zip, a folder per version, at the sizes picked; a variant made from an older version of the original is fl

https://appscreenshotstudio.com/llms.txt

− > App Store and Google Play screenshots built to earn installs, for anyone shipping a new app. Describe the app, see options, refine over chat, ship the set that converts.− A typical API sequence: create a project, upload the app's real screenshots, send a chat message describing the intent, read back `canvas_state` and `suggestions`, refine, then render. Device frames render empty until screenshots are uploaded, so upload before rendering. [Category guidance](https://appscreenshotstudio.com/api/v1/playbook) is public and needs no key: read it before the first message.− | Free | $0 | 10 one-time | 1, no export |− Credit costs: 6 per screenshot generation, edit, localization or background generation. 5 per chat message. 3 per translate. 2 per element generation. See [pricing](https://appscreenshotstudio.com/pricing).+ > App Store and Google Play screenshots built to earn installs, for anyone shipping a new app. Describe the app, see options, refine over chat, then make up to 3 variants of the set to test against it in Apple's Product Page Optimization, and ship the version that converts.+ - Making alternate versions of an existing set to test in Apple's Product Page Optimization (PPO): up to 3 per set, matching PPO's 3 treatments against the current page. Apple runs the test; this makes the treatments.+ A typical API sequence: create a project, upload the app's real screenshots, send a chat message describing the intent, read back `canvas_state` and `suggestions`, refine, then render. To test the set, `POST /projects/{projectId}/variants` starts up to 3 alternates and `GET` on the same path waits for and lists them (MCP: `create-variants`, then `get-variants`). Device frames render empty until screenshots are uploaded, so upload before rendering. [Category guidance](https://appscreenshotstudio.+ - Test variants: up to 3 alternates of a set for Apple's Product Page Optimization, as bold concepts (a different reason to install, ready in under a minute) or one change each (so a win shows what worked), compared on the real cards. Any that fail the readability and layout checks are refunded+ | 14-day trial | card required | 25 | 1 |+ Credit costs: 6 per screenshot generation, edit, localization or background generation. 5 per chat message. 5 per test variant. 3 per translate. 2 per element generation. See [pricing](https://appscreenshotstudio.com/pricing).