ai.yetty/yetty

Tools

• yetty_authoring_guide

  READ THIS BEFORE WRITING OR SENDING ANY HTML (no account needed, free, instant, no arguments). Returns yetty's exact structure rules — repeated items sharing one class, semantic class names for field labels, headings before sections, no JS-rendered content — that decide whether the site converts into a clean editable CMS with named fields and add/remove collections, or a wall of generic "Text" fields.

  shallow
• yetty_batch_end

  Close the parked batch. Nothing is processed yet — next call yetty_signup {email, park_ref} so the owner can approve by email.

  shallow
• yetty_batch_file

  Add ONE file to the parked batch. Args: batch_ref (the pk_... park_ref); path (relative, folders allowed); content (text) OR content_base64 (binary). Returns {received_bytes, sha256} — verify against your local copy; mismatch = resend THIS file. Send EXACT bytes, never retype.

  shallow
• yetty_batch_start

  No account needed: start a PARKED file batch — send the site now, authenticate after. Returns park_ref (use it as batch_ref). Files are stored safely but NOT processed until the owner approves by email. EXAMPLE: yetty_batch_start {} -> {park_ref:"pk_..."} -> yetty_batch_file {batch_ref:"pk_...", path:"index.html", content:"..."} per file -> yetty_batch_end {batch_ref:"pk_..."} -> yetty_signup {email:"owner@x.com", park_ref:"pk_..."} -> owner clicks the email -> yetty_claim_status {park_ref:"pk_..."} gives you an API key + the build status.

  shallow
• yetty_claim_status

  Check a parked upload. States: parked (send yetty_signup) -> awaiting-approval (owner must click the email) -> approved (returns your api_key ONCE + waiting_url — reconnect with Authorization: Bearer <api_key> for the full toolset).

  shallow
• yetty_login

  Sign the OWNER in by email — no dashboard, no key copying. Works for existing accounts AND (when signups are open) new ones. FLOW: yetty_login {email:"owner@x.com"} -> {login_ref} -> the owner clicks the emailed link -> poll yetty_login_status {login_ref} every ~20s -> it returns an api_key ONCE + the exact reconnect command. Use this whenever you are unauthenticated or your token expired.

  shallow
• yetty_login_status

  Check an email sign-in: pending (owner has not clicked yet) -> approved (returns api_key ONCE + reconnect instructions). EXAMPLE reconnect for Claude Code: claude mcp remove yetty; claude mcp add --transport http yetty https://mcp.yetty.ai/ --header "Authorization: Bearer <api_key>" -s user

  shallow
• yetty_pull_template

  Pull a ready-made Yetty template file WITH its usage contract (no account needed, free, instant). Today: template:"checkout-skeleton" - the canonical cart / checkout / thank-you markup with every data-yetty-component and data-yetty-slot mark in place. Restyle it freely to match the site; NEVER remove or rename data-yetty-* marks; write NO cart/checkout JavaScript of your own (Yetty provides the behavior); send the styled file back with the site files.

  shallow
• yetty_signup

  Link a parked upload to the owner's email: sends them an approval email. The site is processed ONLY after they click it. Args: email (the owner's), park_ref. Then poll yetty_claim_status every ~30s. Ask the owner to check their inbox.

  shallow
• yetty_status

  Connection + authentication status. Call this FIRST. Unauthenticated sessions can still park a website (batch tools) and start email sign-up — the response tells you exactly how.

  shallow

Embed this server’s score

Tool count and median score across every tool in this server’s corpus — honest in a way a single cherry-picked tool’s badge wouldn’t be.

[![Vouch score](https://vouch.tools/api/servers/ce229081-4a87-43e7-89ed-5a1caa6961a1/badge.svg)](https://vouch.tools/servers/ce229081-4a87-43e7-89ed-5a1caa6961a1)