Xyppy Print This

Xyppy Print This starts after someone already has an image they care about. It keeps the first product loop small: bring the image into ChatGPT, understand print quality and crop tradeoffs, choose a physical treatment, and leave with a reviewed configuration rather than an implied order.

The project is not only a repository. A Model Context Protocol server registers read-only tools and a React widget resource for ChatGPT. Historical Developer Mode evidence shows that the custom interface rendered in a live conversation. The host supplies an image when it can; ChatGPT file selection and upload remain deliberate fallbacks.

Configuration can produce deterministic prototype pricing, a stable quote ID, provider-oriented handoff fields, estimated shipping, and a Shopify-first next action. The current runtime cannot create a cart, checkout session, order, payment, production file, or fulfillment task, and every completion surface says so.

Source main passed typecheck, 17 tests, and a production build on August 16, 2026. The connected personal plugin's temporary endpoint did not answer a fresh invocation that day, so current runtime availability remains unproven even though the earlier in-chat widget proof is preserved. Durable hosting and a refreshed host validation are the next product gates.

The app still uses prototype prices and representative previews, does not have a durable public host, and cannot create live commerce or production state. Direct transfer of the immediately preceding generated image is host-dependent. These limits keep the present record honest while identifying the next decisions: hosting, metadata refresh, checkout backend, asset retention, and operational review.

The September 5–9 task Finish Xyppy Print GPT app moved the local interface toward a compact conversational card: image proof and options first, conversational edits synchronized with controls, and valid catalog alternatives for unsupported requests. The source reports the corrected Stripe foundation and consolidated work merged at cf0d333 on September 8. The operator chose an independent Xyppy catalog/order system with Stripe Checkout; Shopify became optional future integration. Later that day the source explicitly selected Printify and reported initial catalog/provider, product-cost, shipping-quote and order-status reads on codex/1004-printify-integration, with 65 tests plus TypeScript, build and MCP checks passing. That September 8 checkpoint had no connected account. The later September 9 repository record supersedes it: a dedicated API shop, Manual submission, disabled Order Routing/Choice upgrade, and authenticated read-only catalog/provider/variant access were verified; the Printify integration merged into main. The user confirmed US-only USD, supplier costs were read and a launch-catalog proposal documented. Customer prices, eligible products, named provider approval and physical samples remained pending. RPS was excluded from this Xyppy fulfillment direction. Hosted credentials, production ordering and the runtime demo catalog were unchanged. Implementation was subsequently paused while the separate marketing site shipped a coming-soon Print This page. The source distinguishes a prior successful Stripe sandbox round trip from the later hosted preview with test/live checkout disabled. These dated implementation reports do not establish a submitted app, live customer checkout, fulfilled order or production-ready supplier integration.