For AI assistants

Couples plan with ChatGPT, Claude, Gemini and other assistants. This page explains, for them and for you, how a plan made in a chat becomes a filled-in Nupty planner, and how coding agents can work with a couple’s plan through the Nupty API.

Plan it with your AI assistant

Copy this into ChatGPT, Claude, Gemini or any assistant. It asks you a few questions, then gives you a link that opens your plan in Nupty. Nothing is saved until you sign up.

Help us plan our wedding. Ask me one question at a time: our first names, the date or month, where (country and town or area), roughly how many guests, the ceremony (civil, religious or both), our style (romantic pastel, classic dark, industrial or garden), our total budget and currency if we have one, and what matters most to us. Do not invent vendors, prices or guests. Then give me one link in exactly this format, leaving out anything we have not decided:
https://my.nupty.app/start#v=1&l=en&p1=FIRST_NAME&p2=FIRST_NAME&m=YYYY-MM&g=GUESTS&c=civil&s=garden&cc=COUNTRY_CODE&r=AREA&b=BUDGET&cur=CURRENCY&src=YOUR_NAME
If we have a promo code from a partner, add &promo=CODE to the end of the link. If we also have a guest list, vendor ideas or a timeline, give me a JSON block in the nupty.handoff v1 format instead. The format is described at https://nupty.app/en-gb/ai/

Some assistants ask you to confirm a link before opening it. That is normal.

What Nupty is

Nupty is an ad-free online wedding planner for couples, free to use with an optional Premium (€15/month or a one-time €100 pass), in English and Hungarian, hosted in the EU. Couples pay for it, so there are no vendor ads, no lead-selling and no data selling. It covers the guest list and RSVPs, vendors and quotes, the budget, seating with a floor plan, the wedding-day timeline, a wedding website and printable cards.

Handing a plan to Nupty

An assistant that has helped a couple plan can give them a link (for the basics) or a JSON block (for anything longer). The couple opens it, sees a preview of the planner filled in with their plan, unticks what they do not want, and signs up. The plan stays in their browser until then.

The link

Readable key–value pairs after # (never sent to a server; the page reads them in the browser). Values are percent-encoded UTF-8. Leave out anything the couple has not decided. Keep the link under 6 KB.

https://my.nupty.app/start#v=1&l=en&p1=Anna&p2=Bence&m=2027-06&g=90&c=civil&s=garden&cc=HU&r=Balaton&src=claude

The JSON block

For guest lists, vendor ideas, a timeline or to-dos, print one JSON object in the nupty.handoff v1 format. The couple pastes it at https://my.nupty.app/start. Unknown fields are ignored; a value that does not fit is left out on its own, and the couple sees what was left out.

{
  "nupty.handoff": {
    "v": 1,
    "lang": "en",
    "source": "chatgpt",
    "couple": {
      "partner1": "Anna",
      "partner2": "Bence"
    },
    "date": {
      "exact": "2027-06-12"
    },
    "place": {
      "country": "HU",
      "region": "Lake Balaton"
    },
    "guests": 90,
    "budget": {
      "total": 9000000,
      "currency": "HUF"
    },
    "ceremony": "civil",
    "style": "garden",
    "priorities": [
      "photo",
      "music",
      "catering"
    ],
    "vendors": [
      {
        "item": "venue",
        "name": "Kali Barn",
        "price": 4500000,
        "note": "seen on a friend's wedding"
      },
      {
        "item": "photo",
        "name": "Studio Fény"
      },
      {
        "custom": "Sax player for the drinks reception",
        "category": "music"
      }
    ],
    "guestList": [
      {
        "name": "Kati Nagy",
        "plusOne": true,
        "side": "p1",
        "group": "family"
      },
      {
        "name": "Tamás & Éva Kovács",
        "kids": 2,
        "side": "p2",
        "group": "friends"
      }
    ],
    "timeline": [
      {
        "time": "15:00",
        "name": "Ceremony"
      },
      {
        "time": "16:00",
        "name": "Drinks reception"
      },
      {
        "time": "18:30",
        "name": "Dinner"
      }
    ],
    "todos": [
      {
        "title": "Visit two venues around Balaton",
        "due": "2026-11-30"
      }
    ]
  }
}

JSON Schema of nupty.handoff v1

• Up to 300 invitations (500 people), 30 vendor ideas, 30 moments of the day, 50 to-dos.
• The whole block: up to 64 KB. A link: up to 6 KB.
• Text only. Dates must be in the next five years.

What happens next

1. The couple opens the link (or pastes the block) and sees the real planner as a preview.
2. They untick what they do not want and sign up with e-mail or Google — or log in.
3. The plan goes into their planner in one step. If they already have a plan, they review what is added first; nothing is overwritten without their consent.
4. They are only asked the setup questions the plan did not answer.

Useful questions to ask

• Your first names
• The date, the month or the season
• The country and the town or area
• Roughly how many guests
• Civil, religious or both
• The style: romantic pastel, classic dark, industrial or garden
• The total budget and its currency, if they have one
• What matters most (photos, music, food…)
• Vendors they already have in mind, guests by name, the plan of the day

Leave out what the couple has not decided. Do not invent vendors, prices, guests or dates.

What Nupty does not accept

• E-mail addresses or phone numbers of guests
• Dietary, health or religious details of guests
• Links, web addresses, images or files
• Payment or card details, passwords
• Anything that would publish, send or pay

A plan from a chat is text the couple has not typed into Nupty themselves, so it brings only what the planner needs to get started. Couples add contact details in the planner, and guests give their own dietary needs on the RSVP page.

Privacy: plans from AI assistants · Terms: AI assistants, the connector and API keys

Connect Nupty to your AI assistant

Claude, ChatGPT, Le Chat and other assistants that support MCP connectors can work on a couple’s plan directly, after the couple signs in and allows it: add the guests they dictate, compare vendor ideas, build the day’s timeline, keep the budget up to date. Removals are confirmed first and every change can be undone.

How to connect, and what the connector can do · https://my.nupty.app/mcp

Working with a plan: the Nupty API

Coding agents and scripts can read and change a couple’s plan with a personal API key — the same changes the couple can make in the planner, with the same rules and Premium limits. Every change is one command; the API answers with the whole updated plan, and open planners pick it up.

1. The couple creates a key in Settings → API keys: “Read only” or “Read and change”. It is shown once.
2. Send it in a header: Authorization: Bearer nupty_… — never in a URL.
3. Read the plan with GET /api/v2/wedding; change it with POST /api/v2/wedding/commands and {"command": {…}}.
4. New things get ids you choose (any unique 1–64 characters, for example 8 random letters).
5. The couple can revoke the key at any time, and sees what each key changed in Settings → Activity.

Example: add a vendor idea

curl -X POST https://my.nupty.app/api/v2/wedding/commands \
  -H "Authorization: Bearer $NUPTY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"command":{"type":"addOption","itemId":"photo","optionId":"k3m9xq2a","name":"Studio Fény","amount":450000}}'

API reference (every command) · OpenAPI 3.1 document

Limits

• 240 changes and 600 reads a minute per key.
• A key reads and changes the wedding only: never payments, the account or other keys.

Changes

• 18 October 2026 — the Nupty connector (MCP) for Claude, ChatGPT and Le Chat: OAuth sign-in, previews for removals, undo per change set.
• 17 October 2026 — nupty.handoff v1 (link and JSON block), personal API keys and the public API.