Peach AI - 3D Website Builder

Showing 25 of 61 from the live probe.

• List video presets

  List peach video-grammar presets — 5 reference product films × 4 director-lens variants. Each realizes as a cinematic scroll animation on any scanned 3D product.

• Get preset details

  Get the full shot-grammar for one preset id: energy/cutStyle/arc plus per-beat { shot, move, subject, motion, light, dur }.

• Render video preset

  Enqueue a render job: realize a video-grammar preset as a cinematic scroll animation on a scanned 3D model, then scroll-capture the beat frames. Returns a jobId immediately — a render takes ~1–3 min, so poll get_render with the jobId for status + frames. Requires auth.

• Check render status

  Poll a render job by id. Returns { status: queued|running|done|error, progress }, and on done: the realized beat frames as inline image content blocks, the auto-score (cinemaGrade 0-100 + per-beat notes, when scoring is configured), and a storyboard clip URL. Requires auth.

• Batch render presets

  Batch enqueue: render every model × preset combination (max 12 jobs per call). Returns the jobId grid — poll each with get_render. The worker renders serially (~3-6 min per job). Requires auth.

• Get judging rubric

  Client-side cinematography gate (scores on YOUR plan, no API credits): returns the judging rubric, the grammar, and the finished render's beat frames. YOU (the calling model) judge the frames against the rubric, then call submit_score with your JSON verdict to store it on the job. Requires auth.

• Submit render score

  Store a cinematography score on a finished render job (the write-back half of judge_render). get_render then returns it as cinemaGrade/verdict/beatNotes. Requires auth.

• Identify caller

  Identify the current MCP caller: resolved userId, auth method (staff act-as, personal token, or oauth sign-in), job-store backend, and the hourly render cap. Call this first — every other user-plane tool needs a resolved userId.

• List your scenes

  List YOUR saved scenes (peach 3D scroll-scenes), most recently updated first. Requires auth.

• Get scene data

  Get one scene's full data doc by id — your own, or any public/builtin scene. The doc is often 50–400 KB: to understand a scene call summarize_scene, and to read specific fields call read_scene_path. Requires auth.

• Save scene

  Create or overwrite one of YOUR scenes. Omit `id` to create a new scene; pass `id` to overwrite (must be one of yours). Requires auth.

• List experiences

  List YOUR peach experiences (published sites/embeds), most recently updated first. Requires auth.

• Get experience

  Get one of YOUR experiences (or any public one) by id — metadata + live URL, and the data doc when include_data is true: the DRAFT for your own experiences, the PUBLISHED version only for anyone else's. Requires auth.

• Summarize scene

  A ~2 KB summary of one scene instead of its full data doc (often 50–400 KB): the model (shape, label, and the uploaded asset's host + file name, never the signed URL), group/single mode and count, background, lighting, which post-FX are on, camera and controls, an inlined experience's section/UI/hotspot counts, key counts per authoring category (the author_scene_patch vocabulary) and per editor folder, and the five largest keys with their JSON Pointers. Use this instead of get_scene to understan

• Read scene path

  Read the value at one JSON Pointer inside a scene's data doc — e.g. "/bloomIntensity" or "/experience/sections/0". Values up to 20,000 bytes come back inline; a larger object or array comes back as its child pointers with their byte sizes, largest first, so you can read one level deeper. Use it instead of get_scene when you need specific fields (get paths from summarize_scene or describe_scene_vocabulary). Same access as get_scene. Requires auth.

• Summarize experience

  Where an experience document's bytes are and what its parts are called — the complement of outline_experience, repeating none of it: total bytes and the draft vs published sizes, bytes per top-level key (one key like savedWraps can hold most of a 400 KB doc), bytes per scene, each section's name, each UI block's template, headline and hotspot count, and the total hotspot count. Use it with outline_experience instead of get_experience(include_data). Your own experience: the draft by default, or t

• List 3D models

  List YOUR uploaded 3D model assets, each with its id (for create_scene) and public url. Requires auth.

• List experience templates

  List the ready-made starter experiences that create_experience can copy with template_id. Requires auth.

• Create experience

  Create a NEW experience on the user's account. Pass exactly one source: scene_id (one of their scenes, giving a one-section experience) or template_id (from list_experience_templates, giving a full copy of that template, scenes included). It starts PRIVATE and unpublished, and nothing existing changes. Edit it with patch_experience; publishing (patch_experience publish:true, or prepare_embed) also makes it public. Requires auth.

• Duplicate experience

  Copy an experience into the user's account: their own draft, or the published version of someone else's public one. Every scene is copied too, so editing the copy never touches the original. The copy starts PRIVATE and unpublished. Requires auth.

• Change experience visibility

  Make one of the user's experiences private (unpublish: its link and every embed stop showing it to visitors) or public again. Only visibility changes, never content. Publishing already makes an experience public, so use this mainly to unpublish. Before making a live experience private, confirm with the user: sites embedding it go blank. Requires auth.

• Delete experience

  PERMANENTLY delete one of the user's experiences. Its link, custom domains and every embed stop working, and it cannot be undone. Always ask the user first, then pass confirm_name exactly equal to the experience's name; a mismatch deletes nothing. Its scenes are kept; remove those separately with delete_scene. Requires auth.

• Delete scene

  PERMANENTLY delete one of the user's scenes. Refused while any experience still uses it, and the refusal names them. Always ask the user first, then pass confirm_name exactly equal to the scene's name. Requires auth.

• Import 3D model

  Import a 3D model from a public https link into the user's model library, the same as uploading it in the editor. Accepts binary glTF (.glb) up to 50 MB only; a .gltf with separate files, .fbx, .obj or .usdz must be converted to .glb first. Importing the same file twice reuses the first copy. Returns model_id; next, create_scene { name, model_id }. Requires auth.

• Generate 3D model

  Generate a 3D model with AI from a text prompt or a public https image link; it is saved to the user's model library like a model generated in the editor. Costs AI credits: 150 credits on the default engine (Designer plan and up), and takes about 5 minutes. The FIRST call without confirm only returns the quote (price, what the user gets, time) and charges nothing: show it to the user and ASK them. Only after they agree, call again with the same input and confirm: true — that charges the credits