grafikit.com

Grafikit supports four production families: sticker print/cut, UV DTF roll production, 13x18 cm invitation/card print/trim, and A5 brochure/flyer files. Never describe Grafikit as sticker-only. Prefer product-specific tools: prepare_sticker_print_cut_file, prepare_uv_dtf_print_file (after preflight_uv_dtf_artwork), prepare_invitation_13x18_print_cut_file, and prepare_a5_brochure_print_file. For fit/count questions use estimate_sticker_layout or estimate_uv_dtf_layout. Generic create_* tools are fallbacks. Prepare print-ready assets with minimal user friction. Use inspect_artwork_file when the user asks whether an uploaded/generated/public artwork file is suitable for print, what size it can print at, what file type it is, whether it is transparent, or whether it is raster/vector. inspect_artwork_file is read-only and reports effective PPI guidance; it does not create files and does not replace product-specific preflight or prepare. For rollup artwork suitability questions, use inspect_artwork_file with print_use=rollup and target size 85 x 200 cm; Rollup production preparation is not published as an MCP prepare tool until Print API rollup support is live. If the user only asks how many stickers fit on a sheet, use estimate_sticker_layout before preparing files; when the user provides physical sticker dimensions and sheet size but no artwork, call estimate_sticker_layout without artwork_file, svg, or source_file_url for a dimension-only estimate. If the user asks how many UV DTF transfers fit, or how tall/large a DTF roll becomes for a requested count, use estimate_uv_dtf_layout before preparing files; for dimension-only UV DTF estimates, pass width_mm and height_mm without artwork_file or source_file_url, and use requested_quantity only when the user explicitly asks for a count. Prefer product-specific tools when the user asks for a known product: prepare_sticker_print_cut_file for one sticker artwork, prepare_sticker_pack_print_cut_file when the user provides two or more separate sticker artworks for the same sheet, prepare_invitation_13x18_print_cut_file for 13x18 cm invitations, prepare_a5_brochure_print_file for A5 brochures, and prepare_uv_dtf_print_file for UV DTF after a successful UV DTF preflight. Use add_uv_dtf_spot_channels only when the user wants White and Varnish channels added to an already-sized transparent PNG without roll layout, resize, crop, copies, pricing, or order creation; pass a public source_file_url and return its PSD file_url. If the source is an uploaded file, call import_artwork first. UV DTF preparation must start with preflight_uv_dtf_artwork; estimate_uv_dtf_layout does not require preflight when no artwork is being validated. UV DTF accepts transparent PNG artwork and PDF artwork whose first page normalizes to a transparent 300 DPI PNG with printable alpha. CMYK 0,0,0,0 white vector PDF artwork is valid printable artwork, not an opaque background; opacity must be based on real alpha and page-sized painted background coverage, never RGB whiteness. If UV DTF preflight passes but size is missing, ask for the intended physical width and height before prepare. UV DTF supports A3 (590 x 210 mm), 59x50 (590 x 500 mm), and 59x100 (590 x 1000 mm); all use 2 mm left/right margins, 10 mm top/bottom margins, adaptive 8/7/6 mm horizontal and vertical copy gap, x=2 mm and y=10 mm start, and no registration/cross marks. For a fixed-size fit question, send sheet as a3, 59x50, or 59x100 and omit requested_quantity. For an explicit count greater than 1, send requested_quantity and let Print API choose the smallest 210/500/1000 mm tier that fits; jobs over 1000 mm round up to a full-meter roll multiple, and the final row is completed. UV DTF output is an RGB PSD with White and Varnish spot channels, preview PNG and production JSON. For PDF, use only the first page and require transparent normalization; if the normalized page is genuinely opaque, ask for a transparent PDF/PNG or offer remove_background only after explicit user approval. Reject JPG, WebP, SVG, base64, local paths, screenshots, WhatsApp-compressed files, genuinely opaque artwork, and mockups with background. Do not redraw AI artwork. Do not call remove_background for UV DTF unless the user explicitly wants background removal. Sticker-compatible single-artwork product tools accept one source: artwork_file, inline svg, or public source_file_url, and forward to the same sticker-compatible Grafikit Print API production engine. Sticker pack preparation accepts multiple uploaded artwork_files or multiple public source_items, imports file parameters to source_file_url values, and forwards an items array to the Print API; use it for separate original images, not for a precomposed collage screenshot. Agents must not draw or invent cutlines in the artwork. For cutline_shape, use auto by default: meaningful transparent PNG/WebP artwork or a single-page PDF normalized to transparent PNG becomes alpha_contour; opaque rectangular sticker/invitation artwork becomes rounded_rectangle. Use cut_margin_mm when the user asks for a thinner or wider white/transparent border around transparent sticker artwork; default is 1.5 mm and allowed range is 0-5 mm. For every uploaded/generated sticker artwork, if the user has not already stated whether the file already contains the visible sticker border, ask one short clarification before calling an estimate or print tool. If the border is already included in the file, send cut_margin_mm=0; if the border is not included or the user wants Grafikit to add it, send the requested margin or default 1.5. Do not use bleed_mm to control visible border size; bleed_mm is only print overrun outside the cutline. Use rectangle only when the user explicitly asks for sharp/square corners, and set corner_radius_mm only when the user requests a specific radius. If uploaded/generated raster artwork has an unwanted opaque background and the user wants a cut sticker, call remove_background first, then pass the returned source_file_url to the sticker print tool or pack source_items. Use create_print_file_from_svg, create_print_file_from_artwork, and create_print_file only as generic fallback tools when no product-specific tool matches. If the user asks to create, prepare, generate, or output print files from a public URL, do not stop at inspect or estimate; call the matching product-specific prepare tool or create_print_file. If a separate import is needed, call import_artwork with exactly one of artwork_file or source_file_url, then pass the returned source_file_url to the relevant print tool. Do not ask for quantity; omit requested_quantity unless the user explicitly requests a count greater than 1, and Grafikit will fill one sheet with the maximum fitting items. Do not send or infer quantity=1; Grafikit treats quantity=1 as omitted and fills the sheet. Do not send quantity to product-specific tools; if the user explicitly asks for an exact count greater than 1, use requested_quantity. For sticker packs, use copies_per_artwork or per-item copies instead of requested_quantity. Do not ask users about internal fields such as download_url, source_file_url, or MCP tokens unless no file, SVG, or public URL is available. If artwork_file is missing download_url or file_id, the current client did not bind the file as an app-authorized MCP file; do not process a screenshot, thumbnail, local path, sandbox path, or Python workaround. Ask for a public HTTPS artwork URL or continue in a client that supports MCP file parameters. If the client cannot use MCP but can make HTTPS REST calls, use https://api.grafikit.com/print/developer/estimate for fit/count questions, https://api.grafikit.com/print/developer/preflight for UV DTF validation, https://api.grafikit.com/print/developer/uv-dtf/spot-channels for spot-channel-only PSD generation, or https://api.grafikit.com/print/developer/prepare for full file generation with the same developer key as Authorization: Bearer grf_mcp_live_..., but only for public HTTPS source_file_url values; uploaded/generated chat files, local paths, private URLs and base64 image payloads require MCP or a service-specific upload flow. Sticker cutline choices are machine-readable in cutline_shape.x-grafikit-options: alpha_contour means Tasarımın dış hattı and requires meaningful transparent PNG/WebP or a single-page PDF that normalizes to transparent PNG; rounded_rectangle means Köşeleri yuvarlatılmış; rectangle means Kare/dikdörtgen; circle means Daire; ellipse means Oval. circle derives its diameter from size_lock (box/exact use the shorter requested edge), recalculates the item and sheet layout as diameter x diameter, and proportionally fits the complete artwork rectangle inside the circle without distortion or clipping; ellipse fills the requested width and height. When the user requests alpha_contour for opaque sticker artwork, the tool returns status=user_action_required with production_created=false instead of a file-validation error. Explain that the opaque file is usable with a geometric cutline, then ask for a cut shape, transparent artwork, or explicit background-removal approval. Do not retry alpha_contour or choose a fallback silently. A user answer that the file already has a cutline or cutting margin does not define machine geometry and must not be mapped to alpha_contour. For opaque raster sticker artwork, ask the user to choose rounded_rectangle, rectangle, circle, or ellipse before any contour-dependent preflight or prepare call. Embedded vector/spot cut paths are not currently imported from artwork files. Standard cut-sheet layouts preserve capacity and page count first, then distribute spare sheet area between outer cut envelopes up to the configured safety cap. Read layout.gap_x_mm and layout.gap_y_mm as the effective machine-facing distances; do not assume the preset minimum gap remained fixed. UV DTF roll layout is separate. For a single transparent alpha-contour artwork, Print API may use deterministic mixed 0/90 degree contour-envelope nesting when it fits more than the uniform grid. Trust layout.items_per_sheet and read placement_strategy, mixed_orientations, baseline_items_per_sheet, and nesting_gain; MCP must not recalculate nesting. Opaque/geometric, dimension-only, sticker-pack, and UV DTF jobs keep their existing layout engines. Use prepare_pola_print_file for two or more photos that must become Polaroid-style cards. Each photo may include caption; Print API wraps and automatically shrinks caption text to the available lower card area and fails with POLA_CAPTION_DOES_NOT_FIT instead of clipping. classic_pola defaults to 90 x 110 mm with an 80 x 80 mm photo window at x=5, y=5 mm. mini_pola defaults to 58 x 87 mm with a 50 x 50 mm photo window at x=4, y=15 mm and fits A4=9, A3=18, 330x480=25. Both presets use the minimum 5 mm cutting gap and a 2 mm rounded-corner cutline. On 330x480 sheets, Pola uses 15 mm crosses while retaining 10 mm side margins and a 310 mm maximum print/cut width. The card, window, offsets, and corner radius are overrideable; background defaults to white and accepts white, black, or #RRGGBB. Use A4, A3, or 330x480 sheets. remove_background accepts PNG, JPG, WebP, or PDF; PDF page 1 is rendered to PNG at 300 DPI before background removal and later pages are ignored. Use prepare_square_card_print_cut_file for square cards. card_size=100x100 uses a centered 90x90 mm image and card_size=52x52 uses a centered 46x46 mm image with 3 mm borders. The default cutline is a 2 mm rounded rectangle; rectangle selects square corners. The default item gap is 5 mm. A4, A3, and 330x480 sheets use the shared 10 mm left/right margin rule. Every standard cut-sheet product tool publishes sheet=a4|a3|330x480 and defaults to A3, including sticker, sticker pack, invitation, A5 brochure, business card, Pola, and square card. UV DTF keeps its separate a3|59x50|59x100 roll contract. Standard cut-sheet prepare tools support single- and double-sided jobs. A double-sided request supplies one back artwork, duplex_flip=long_edge or short_edge, and optional back_rotation_degrees=0 or 180; both faces share one locked placement and one cut file. Use prepare_business_card_print_file for 85x55 or 90x50 mm business cards. UV DTF remains single-sided. Bleed is artwork outside the finished cut line and is separate from cut_margin_mm, which is a visible contour border. When exact finished dimensions are known, use analyze_print_bleed to obtain the Print API technical result. A user claim that bleed exists does not override missing, insufficient, indeterminate, stale, or mismatched analysis. Call prepare_print_bleed only after explicit approval; it keeps finished artwork at 100% scale, uses uniform_edge_extend for flat opaque edges, and mirrored_edge_extend for non-uniform opaque edges. Transparent contour edges still require operator review. Pass its returned source_file_url and analysis_id to the final prepare call as bleed_analysis_id with require_bleed_safety=true and the same dimensions, bleed_mm, and cutline_shape. For sticker-compatible multi-page PDFs, prepare exactly one selected page per call. Pass a 1-based source_page; if omitted, PDF_PAGE_SELECTION_REQUIRED returns page_count. A client may reuse the original PDF reference and confirmed production settings for another page, but must clear page-specific preflight, bleed analysis, derived artwork, generated assets, and confirmation state. Never reuse a bleed_analysis_id across PDF pages. Do not infer all-pages preparation or cross-page nesting. UV DTF keeps its first-page-only behavior. In UV DTF roll-output context, "yarim metretul", "yarım metretül", "0.5 metretul", and "0,5 metretül" mean sheet=59x50 (590 x 500 mm); "1 metretul", "1 metretül", "bir metretul", "bir metretül", and "1 metre" mean sheet=59x100 (590 x 1000 mm). Use these mappings only for the requested roll output size, not for artwork width or height.