← Home

A HEAD START ON FINDING HELP

Your assistant knows the project.
Bring the details here.

Use the AI assistant you already have to prepare a job request. Then check the details on MendyJob and make it yours.

  1. Describe your project
  2. Open your prepared link
  3. Review & post

Give your assistant a starting point

Copy this prompt into your conversation. Your assistant may need browsing or link-reading access. If it cannot create a link, paste its description here instead.

I have my job details

You stay in control

Every prepared request is a starting point. Edit any field, add photos, and complete your private address on MendyJob. Your job opens for quotes only after you sign in and confirm.

Prepared links contain shareable job information. Encoding does not make them private. Check your description for personal details before sharing a link.

Prefer to start from scratch? Post a job →
Instructions for AI assistants and developers

Read the versioned job schema and current service catalog. Omit unknown fields instead of guessing or sending null. Use category IDs and the selected service’s exact question keys and choices. Respect conditional questions and option variants.

Create a JSON object with schemaVersion: 1. Encode it using encodeURIComponent(JSON.stringify(job)) and append it to https://mendyjob.com/Jobs/Import#job=. Keep the complete link under 12,000 characters; provide JSON for pasting when it is longer. JSON payloads are limited to 12,000 characters.

{"schemaVersion":1,"category":"handyman","description":"Repair a leaking kitchen faucet.","zipCode":"21044","budget":150}

Budget is an optional amount in USD. Timeframe is asap or selected. Selected visit times use availability: [{"date":"YYYY-MM-DD","period":"morning"}]; periods are morning (8–12), midday (12–4), or evening (4–8). Read the schema’s current scheduling range and timezone. Resolve relative dates with the customer. Omit undecided schedules.

All fields except the schema version may be omitted to create a partial draft. Service answers are optional. Never include exact addresses, contact details, access instructions, user IDs, company preferences, tokens, or job status. Do not put payloads in query strings.

This is a form import protocol, not a publishing API. Publishing these instructions does not guarantee automatic assistant discovery. No MCP connection or draft API is required for this version.