directory

{'type': 'object', 'required': ['name'], 'properties': {'url': {'type': 'string'}, 'name': {'type': 'string'}, 'pack': {'type': 'object', 'properties': {'url': {'type': 'string', 'description': 'The page a visitor lands on, not a waitlist.'}, 'name': {'type': 'string', 'description': 'Exactly as it should appear in a listing. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'logoUrl': {'type': 'string', 'description': 'Square, transparent, 512px or better. The public address of the image: forms with a logo URL field take this one, and it is what shows on your dashboard.'}, 'pricing': {'type': 'string', 'description': 'What it costs, in a sentence a form can take. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'repoUrl': {'type': 'string', 'description': 'The public repository, for open-source directories. Leave it empty for a closed-source product rather than pointing at something else.'}, 'tagline': {'type': 'string', 'description': 'One line, no product name, no full stop. Max 60 characters. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'xHandle': {'type': 'string', 'description': 'Without the @. Launch boards ask for it and some make it a required field, so a pack without one stalls at the last step of a form that is otherwise finished. Fill it only with an account you hold: it is printed on the listing as the maker, and a handle typed to satisfy a validator credits whoever really owns it. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'audience': {'type': 'array', 'items': {'type': 'string'}, 'description': 'The people it is built for, like Freelancers or Small businesses, for the forms with a target-audience picker. Only what the maker told you, never a guess. When a form requires it and it is empty here, ask the maker once, then save the answer with update_project so no other form stops on it. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'coverUrl': {'type': 'string', 'description': '1270x760, the size every gallery accepts. The public address of it.'}, 'location': {'type': 'string', 'description': 'City and country, or country alone. Asked for as headquarters, and it decides the regional directories. Only what the maker told you, never a guess. When a form requires it and it is empty here, ask the maker once, then save the answer with update_project so no other form stops on it. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'logoFile': {'type': 'string', 'description': 'The same logo as a file on the machine your agent runs on, like /Users/you/product/logo-512.png. This is the one a submission form uploads, because a file picker cannot be handed a link. It stays a path: nothing can display it, here or anywhere else.'}, 'makerBio': {'type': 'string', 'description': 'Asked for by launch platforms, not by plain directories. Max 160 characters. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'oneLiner': {'type': 'string', 'description': 'A sentence that works as a meta description. Max 140 characters. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'teamSize': {'type': 'string', 'description': 'How many people work on it, as a number or a range like 2-10. Only what the maker told you, never a guess. When a form requires it and it is empty here, ask the maker once, then save the answer with update_project so no other form stops on it. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'coverFile': {'type': 'string', 'description': 'The same cover as a file on the machine your agent runs on, for the forms that upload it.'}, 'makerName': {'type': 'string', 'description': 'The person shown as the maker, first and last name, exactly as it should be printed on a listing. Launch boards and founder profiles require it. Only what the maker told you, never a guess. When a form requires it and it is empty here, ask the maker once, then save the answer with update_project so no other form stops on it. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'makerRole': {'type': 'string', 'description': 'Their title, like Founder or Solo developer. Only what the maker told you, never a guess. When a form requires it and it is empty here, ask the maker once, then save the answer with update_project so no other form stops on it. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'techStack': {'type': 'array', 'items': {'type': 'string'}, 'description': 'What it is built with, five at most, like Next.js or Postgres. Launch boards for builders make it a required step. Only what the maker told you, never a guess. When a form requires it and it is empty here, ask the maker once, then save the answer with update_project so no other form stops on it. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'buildStory': {'type': 'string', 'description': 'Why and how it was built, with the real numbers, for community posts and maker showcases that want a story rather than a description. Only what the maker told you, never a guess. When a form requires it and it is empty here, ask the maker once, then save the answer with update_project so no other form stops on it. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'categories': {'type': 'array', 'items': {'type': 'string'}, 'description': "Three at most, in the platform's own vocabulary where it has one. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead."}, 'howItWorks': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Three short steps, one per line, under 200 characters each. Only what the maker told you, never a guess. When a form requires it and it is empty here, ask the maker once, then save the answer with update_project so no other form stops on it. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'companyName': {'type': 'string', 'description': 'The business behind the product, when it is not the product name. Review sites and B2B directories list the company. Only what the maker told you, never a guess. When a form requires it and it is empty here, ask the maker once, then save the answer with update_project so no other form stops on it. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'foundedYear': {'type': 'string', 'description': 'Four digits. Only what the maker told you, never a guess. When a form requires it and it is empty here, ask the maker once, then save the answer with update_project so no other form stops on it. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'galleryUrls': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Three to five, first one a poster slide. Public addresses, one per line. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'contactEmail': {'type': 'string', 'description': 'The address you submit under. Most forms ask for one, and it is where the confirmation link lands, so a mailbox nobody opens stalls the submission. Per product, not per person: a client launch and a side project rarely want the same address, and the one you use here is the one the listing belongs to. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'demoVideoUrl': {'type': 'string', 'description': 'Optional almost everywhere, decisive on a few. A watch page or a hosted file.'}, 'firstComment': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Product Hunt and Show HN only, and it matters there. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'fundingStage': {'type': 'string', 'description': 'Bootstrapped, or what was raised and at which stage. Only what the maker told you, never a guess. When a form requires it and it is empty here, ask the maker once, then save the answer with update_project so no other form stops on it. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'galleryFiles': {'type': 'array', 'items': {'type': 'string'}, 'description': 'The same frames as files on the machine your agent runs on, in the same order, one per line. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'alternativeTo': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Well-known products this replaces, by name. Alternative directories will not take a listing without one. Only what the maker told you, never a guess. When a form requires it and it is empty here, ask the maker once, then save the answer with update_project so no other form stops on it. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'demoVideoFile': {'type': 'string', 'description': 'The video as a file on the machine your agent runs on, for the few platforms that upload rather than embed.'}, 'monthlyRevenue': {'type': 'string', 'description': 'MRR or a bracket like $0-1k, and only if the maker is happy for it to be public: forms that ask for it usually display it. Only what the maker told you, never a guess. When a form requires it and it is empty here, ask the maker once, then save the answer with update_project so no other form stops on it. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'longDescription': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Two or three paragraphs, for the forms with room. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'monthlyVisitors': {'type': 'string', 'description': 'A real figure from their analytics. Some directories make it a required number and print it. Only what the maker told you, never a guess. When a form requires it and it is empty here, ask the maker once, then save the answer with update_project so no other form stops on it. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'shortDescription': {'type': 'string', 'description': 'The paragraph most directory forms ask for. Max 260 characters. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'extendedDescription': {'type': 'string', 'description': 'A full write-up of 400 words or more (about 2,500 characters) for the forms that set a minimum length. The long description above is shorter on purpose. Drafting it from the product is fine, but show the maker before it is used, because it goes out under their name. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}}}, 'facts': {'type': 'object', 'properties': {'stage': {'enum': ['idea', 'prelaunch', 'live', 'revenue'], 'type': 'string'}, 'categories': {'type': 'array', 'items': {'enum': ['agent-skill', 'ai', 'b2b', 'christian', 'community', 'content', 'design', 'dev', 'directory', 'extension', 'free', 'hardware', 'indie', 'local', 'marketing', 'marketplace', 'mcp', 'mobile', 'no-code', 'open-source', 'prelaunch', 'productivity', 'saas', 'turkish-founders', 'web'], 'type': 'string'}, 'description': 'Every audience and form factor this product belongs to, not just the main one. A product is often several at once, and one missing tag is one directory it never hears about: a repository holding a browser extension and a web app is `extension` and `web`, and an open-source AI dev tool is `open-source`, `ai` and `dev`. Look at what the product actually ships before you answer: a manifest.json means `extension`, an ios or android target means `mobile`, a public repository means `open-source`, an mcp server is `mcp`, a workspace with several of those means all of them. Then answer what it is commercially, which is a separate question and the one most runs lose platforms on: most launch boards say what they take by who ships it, not by what it runs on, so a subscription mobile app is `mobile` and `saas`, anything a solo maker or small team shipped is `indie`, and something sold to companies is `b2b`. Leaving those off does not make the run safer, it makes it shorter. Tags: agent-skill, ai, b2b, christian, community, content, design, dev, directory, extension, free, hardware, indie, local, marketing, marketplace, mcp, mobile, no-code, open-source, prelaunch, productivity, saas, turkish-founders, web.'}, 'pricingModel': {'enum': ['free', 'freemium', 'paid', 'lifetime'], 'type': 'string'}}, 'description': 'Same shape qualify_project takes: stage, pricingModel, categories, and the booleans. It is also where the two answers that decide a run order live once the maker has given them (`goal`, `budget`, and `launchAt` if they named a date), which is what stops the next session asking again. Leave domainRating out: the url is measured against Ahrefs on the way in and the measured number is what gets stored, so a guess here is overwritten anyway.'}, 'pitch': {'type': 'string', 'description': "One paragraph in the maker's own words."}}}

{'type': 'object', 'required': ['slug'], 'properties': {'slug': {'type': 'string', 'description': 'Platform slug, e.g. "product-hunt".'}, 'brief': {'type': 'boolean', 'description': 'Include agentPrompt and agentGotchas. This is the paid half and it spends a tracked platform, once, for good. Leave it out while you are deciding where to submit: eligibility, disqualifiers, gotchas, approval time and link type all come back either way. A platform this account has already spent a slot on is free to brief again, so re-reading one costs nothing.'}, 'projectId': {'type': 'string', 'description': 'Which project the brief is for, when brief is true. Omit it when the account has one project. A brief is one form being worked on for one product, and the project it belongs to cannot be issued another until this one has an outcome recorded.'}}}

{'type': 'object', 'properties': {}}

{'type': 'object', 'properties': {'projectId': {'type': 'string', 'description': 'Omit it when the account has one project, which is the free tier.'}}}

{'type': 'object', 'required': ['items'], 'properties': {'items': {'type': 'array', 'items': {'type': 'object', 'required': ['platformSlug'], 'properties': {'reason': {'type': 'string', 'description': 'Why this platform, and why here in the order.'}, 'platformSlug': {'type': 'string'}}}, 'description': 'In the order they should be submitted. First is next.'}, 'summary': {'type': 'string', 'description': 'Why this order, in a sentence or two. The maker reads this.'}, 'checklist': {'type': 'array', 'items': {'type': 'object', 'required': ['title'], 'properties': {'title': {'type': 'string', 'description': 'Short and doable, as an instruction.'}, 'detail': {'type': 'string', 'description': 'The specifics: sizes, lengths, why.'}}}, 'description': 'What the maker has to prepare before any of this can be submitted: the gallery, the demo video, a privacy policy page, a launch date. Write it from what the platforms in this plan actually demand and what the project is missing, not from a generic template. The maker ticks these off or throws them away on their dashboard, and anything they have already decided on keeps that decision when you plan again.'}, 'projectId': {'type': 'string', 'description': 'Omit it when the account has one project, which is the free tier.'}}}

{'type': 'object', 'properties': {'url': {'type': 'string'}, 'docs': {'type': 'boolean'}, 'goal': {'enum': ['already-live', 'launching-later'], 'type': 'string', 'description': 'What this run is for, which decides the order of it. `already-live` means the product is out and wants listings, links and traffic now, so the run leads on fast approvals, dofollow links and strong domains. `launching-later` means there is a launch date ahead, so it leads on the platforms with months of queue. Ask the maker rather than guessing: absent, it is inferred from `stage` and the response says so.'}, 'name': {'type': 'string'}, 'stage': {'enum': ['idea', 'prelaunch', 'live', 'revenue'], 'type': 'string'}, 'budget': {'enum': ['free-only', 'will-pay'], 'type': 'string', 'description': 'Whether platforms that charge to list may appear in the run. Absent means `free-only`, which is the assumption that cannot cost anybody anything. `freemium` platforms are in the run either way: their submission is free, and paying to skip their queue is a separate question at the form.'}, 'launchAt': {'type': 'string', 'description': 'ISO 8601 date the maker is launching on, when they have named one.'}, 'demoVideo': {'type': 'boolean'}, 'categories': {'type': 'array', 'items': {'enum': ['agent-skill', 'ai', 'b2b', 'christian', 'community', 'content', 'design', 'dev', 'directory', 'extension', 'free', 'hardware', 'indie', 'local', 'marketing', 'marketplace', 'mcp', 'mobile', 'no-code', 'open-source', 'prelaunch', 'productivity', 'saas', 'turkish-founders', 'web'], 'type': 'string'}, 'description': 'Every audience and form factor this product belongs to, not just the main one. A product is often several at once, and one missing tag is one directory it never hears about: a repository holding a browser extension and a web app is `extension` and `web`, and an open-source AI dev tool is `open-source`, `ai` and `dev`. Look at what the product actually ships before you answer: a manifest.json means `extension`, an ios or android target means `mobile`, a public repository means `open-source`, an mcp server is `mcp`, a workspace with several of those means all of them. Then answer what it is commercially, which is a separate question and the one most runs lose platforms on: most launch boards say what they take by who ships it, not by what it runs on, so a subscription mobile app is `mobile` and `saas`, anything a solo maker or small team shipped is `indie`, and something sold to companies is `b2b`. Leaving those off does not make the run safer, it makes it shorter. Tags: agent-skill, ai, b2b, christian, community, content, design, dev, directory, extension, free, hardware, indie, local, marketing, marketplace, mcp, mobile, no-code, open-source, prelaunch, productivity, saas, turkish-founders, web.'}, 'coverImage': {'type': 'boolean'}, 'logoSquare': {'type': 'boolean'}, 'openSignup': {'type': 'boolean'}, 'publicRepo': {'type': 'boolean'}, 'pricingPage': {'type': 'boolean'}, 'domainRating': {'type': 'number'}, 'pricingModel': {'enum': ['free', 'freemium', 'paid', 'lifetime'], 'type': 'string'}, 'livePublicUrl': {'type': 'boolean'}, 'privacyPolicy': {'type': 'boolean'}, 'monthlyTraffic': {'type': 'number'}, 'acceptsBacklink': {'type': 'boolean'}, 'payingCustomers': {'type': 'boolean'}}}

{'type': 'object', 'required': ['platformSlug', 'status'], 'properties': {'note': {'type': 'string', 'description': 'Required with `planned`: what you need from the maker, in one line they can act on.'}, 'status': {'enum': ['planned', 'attempted', 'submitted', 'live', 'rejected', 'needs_changes'], 'type': 'string', 'description': 'Use `attempted` when the form was sent and you cannot prove it arrived: the tab died, the connection dropped, the page never came back. It is not a lesser `submitted`, it is the honest one, and it carries the verification the platform record describes so somebody can settle it later. Never re-send a form to find out; every platform has a way to check without submitting twice. Use `planned`, with a note, to hand a platform back to the maker when it is waiting on them. A first record is `submitted`, `attempted` or `planned`: `live`, `rejected` and `needs_changes` come after one of those.'}, 'launchAt': {'type': 'string', 'description': 'ISO 8601, if it is scheduled.'}, 'projectId': {'type': 'string', 'description': 'Omit it when the account has one project, which is the free tier.'}, 'listingUrl': {'type': 'string', 'description': "The product's URL on that platform."}, 'submittedAt': {'type': 'string', 'description': 'ISO 8601.'}, 'platformSlug': {'type': 'string'}, 'differsFromRecord': {'type': 'string', 'description': 'Only when the live platform did not match the brief or the platform record: say what differed, in one line, as fact. A price where the record said free, a sign-in or phone check it did not mention, a field it did not list, a submit page that moved, an audience it does not accept. We read these and fix the record, so the next maker is not sent into the same wall. Leave it out when everything matched.'}}}

{'type': 'object', 'properties': {'sort': {'enum': ['approvalDays', 'domainRating'], 'type': 'string', 'description': 'Fastest approval first (the default), or strongest domain first. Either way, a platform that publishes no approval time comes last rather than reading as instant.'}, 'limit': {'type': 'number', 'description': 'Return at most this many. The count is unaffected.'}, 'query': {'type': 'string', 'description': 'Free text matched against name, tagline, domain, slug and categories. A bare domain works: "startupfa.me" finds Startup Fame.'}, 'pricing': {'enum': ['free', 'freemium', 'paid'], 'type': 'string'}, 'category': {'type': 'string', 'description': 'e.g. "AI tools", "Dev tools", "Web apps".'}, 'dofollow': {'type': 'boolean', 'description': 'Only platforms giving a dofollow backlink.'}, 'projectId': {'type': 'string', 'description': 'Omit it when the account has one project, which is the free tier.'}, 'excludeTracked': {'type': 'boolean', 'description': 'Leave out every platform this project has already been submitted to or planned for. Needs a token, and is what makes "one I have not done yet" answerable.'}, 'maxApprovalDays': {'type': 'number', 'description': 'Only platforms approving within this many days. Leaves out every platform that publishes no approval time, the same way a rating bound leaves out the unrated.'}, 'maxDomainRating': {'type': 'number', 'description': 'Only platforms up to this domain rating. The small, quick, unglamorous end of the directory, which is where a first submission usually belongs.'}, 'minDomainRating': {'type': 'number', 'description': 'Only platforms with at least this domain rating.'}, 'requiresBacklink': {'type': 'boolean', 'description': 'Filter on whether they demand a badge/link back.'}}}

{'type': 'object', 'required': ['platformSlug'], 'properties': {'signInAs': {'type': 'string', 'description': 'The Google address the maker wrote out when they agreed you could sign in, or sign up, for them on this project, whether they said it when asked or before you started. Pass it on every call after they say it, so the answer travels with the work instead of living in your head. It belongs to one project: on a different one, ask again rather than sending the address you were given for the last. Leave it out if they have not written one: sign-in then goes back to them, which is the safe end.'}, 'projectId': {'type': 'string', 'description': 'Omit it when the account has one project, which is the free tier.'}, 'platformSlug': {'type': 'string'}}}

{'type': 'object', 'properties': {'url': {'type': 'string'}, 'name': {'type': 'string'}, 'pack': {'type': 'object', 'properties': {'url': {'type': 'string', 'description': 'The page a visitor lands on, not a waitlist.'}, 'name': {'type': 'string', 'description': 'Exactly as it should appear in a listing. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'logoUrl': {'type': 'string', 'description': 'Square, transparent, 512px or better. The public address of the image: forms with a logo URL field take this one, and it is what shows on your dashboard.'}, 'pricing': {'type': 'string', 'description': 'What it costs, in a sentence a form can take. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'repoUrl': {'type': 'string', 'description': 'The public repository, for open-source directories. Leave it empty for a closed-source product rather than pointing at something else.'}, 'tagline': {'type': 'string', 'description': 'One line, no product name, no full stop. Max 60 characters. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'xHandle': {'type': 'string', 'description': 'Without the @. Launch boards ask for it and some make it a required field, so a pack without one stalls at the last step of a form that is otherwise finished. Fill it only with an account you hold: it is printed on the listing as the maker, and a handle typed to satisfy a validator credits whoever really owns it. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'audience': {'type': 'array', 'items': {'type': 'string'}, 'description': 'The people it is built for, like Freelancers or Small businesses, for the forms with a target-audience picker. Only what the maker told you, never a guess. When a form requires it and it is empty here, ask the maker once, then save the answer with update_project so no other form stops on it. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'coverUrl': {'type': 'string', 'description': '1270x760, the size every gallery accepts. The public address of it.'}, 'location': {'type': 'string', 'description': 'City and country, or country alone. Asked for as headquarters, and it decides the regional directories. Only what the maker told you, never a guess. When a form requires it and it is empty here, ask the maker once, then save the answer with update_project so no other form stops on it. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'logoFile': {'type': 'string', 'description': 'The same logo as a file on the machine your agent runs on, like /Users/you/product/logo-512.png. This is the one a submission form uploads, because a file picker cannot be handed a link. It stays a path: nothing can display it, here or anywhere else.'}, 'makerBio': {'type': 'string', 'description': 'Asked for by launch platforms, not by plain directories. Max 160 characters. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'oneLiner': {'type': 'string', 'description': 'A sentence that works as a meta description. Max 140 characters. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'teamSize': {'type': 'string', 'description': 'How many people work on it, as a number or a range like 2-10. Only what the maker told you, never a guess. When a form requires it and it is empty here, ask the maker once, then save the answer with update_project so no other form stops on it. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'coverFile': {'type': 'string', 'description': 'The same cover as a file on the machine your agent runs on, for the forms that upload it.'}, 'makerName': {'type': 'string', 'description': 'The person shown as the maker, first and last name, exactly as it should be printed on a listing. Launch boards and founder profiles require it. Only what the maker told you, never a guess. When a form requires it and it is empty here, ask the maker once, then save the answer with update_project so no other form stops on it. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'makerRole': {'type': 'string', 'description': 'Their title, like Founder or Solo developer. Only what the maker told you, never a guess. When a form requires it and it is empty here, ask the maker once, then save the answer with update_project so no other form stops on it. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'techStack': {'type': 'array', 'items': {'type': 'string'}, 'description': 'What it is built with, five at most, like Next.js or Postgres. Launch boards for builders make it a required step. Only what the maker told you, never a guess. When a form requires it and it is empty here, ask the maker once, then save the answer with update_project so no other form stops on it. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'buildStory': {'type': 'string', 'description': 'Why and how it was built, with the real numbers, for community posts and maker showcases that want a story rather than a description. Only what the maker told you, never a guess. When a form requires it and it is empty here, ask the maker once, then save the answer with update_project so no other form stops on it. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'categories': {'type': 'array', 'items': {'type': 'string'}, 'description': "Three at most, in the platform's own vocabulary where it has one. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead."}, 'howItWorks': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Three short steps, one per line, under 200 characters each. Only what the maker told you, never a guess. When a form requires it and it is empty here, ask the maker once, then save the answer with update_project so no other form stops on it. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'companyName': {'type': 'string', 'description': 'The business behind the product, when it is not the product name. Review sites and B2B directories list the company. Only what the maker told you, never a guess. When a form requires it and it is empty here, ask the maker once, then save the answer with update_project so no other form stops on it. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'foundedYear': {'type': 'string', 'description': 'Four digits. Only what the maker told you, never a guess. When a form requires it and it is empty here, ask the maker once, then save the answer with update_project so no other form stops on it. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'galleryUrls': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Three to five, first one a poster slide. Public addresses, one per line. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'contactEmail': {'type': 'string', 'description': 'The address you submit under. Most forms ask for one, and it is where the confirmation link lands, so a mailbox nobody opens stalls the submission. Per product, not per person: a client launch and a side project rarely want the same address, and the one you use here is the one the listing belongs to. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'demoVideoUrl': {'type': 'string', 'description': 'Optional almost everywhere, decisive on a few. A watch page or a hosted file.'}, 'firstComment': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Product Hunt and Show HN only, and it matters there. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'fundingStage': {'type': 'string', 'description': 'Bootstrapped, or what was raised and at which stage. Only what the maker told you, never a guess. When a form requires it and it is empty here, ask the maker once, then save the answer with update_project so no other form stops on it. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'galleryFiles': {'type': 'array', 'items': {'type': 'string'}, 'description': 'The same frames as files on the machine your agent runs on, in the same order, one per line. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'alternativeTo': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Well-known products this replaces, by name. Alternative directories will not take a listing without one. Only what the maker told you, never a guess. When a form requires it and it is empty here, ask the maker once, then save the answer with update_project so no other form stops on it. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'demoVideoFile': {'type': 'string', 'description': 'The video as a file on the machine your agent runs on, for the few platforms that upload rather than embed.'}, 'monthlyRevenue': {'type': 'string', 'description': 'MRR or a bracket like $0-1k, and only if the maker is happy for it to be public: forms that ask for it usually display it. Only what the maker told you, never a guess. When a form requires it and it is empty here, ask the maker once, then save the answer with update_project so no other form stops on it. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'longDescription': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Two or three paragraphs, for the forms with room. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'monthlyVisitors': {'type': 'string', 'description': 'A real figure from their analytics. Some directories make it a required number and print it. Only what the maker told you, never a guess. When a form requires it and it is empty here, ask the maker once, then save the answer with update_project so no other form stops on it. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'shortDescription': {'type': 'string', 'description': 'The paragraph most directory forms ask for. Max 260 characters. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}, 'extendedDescription': {'type': 'string', 'description': 'A full write-up of 400 words or more (about 2,500 characters) for the forms that set a minimum length. The long description above is shorter on purpose. Drafting it from the product is fine, but show the maker before it is used, because it goes out under their name. Write it as the maker would: no em dashes, which read as machine-written and get the whole listing dismissed. Use a comma, a colon, a semicolon, brackets or a full stop instead.'}}}, 'facts': {'type': 'object'}, 'pitch': {'type': 'string'}, 'projectId': {'type': 'string', 'description': 'Omit it when the account has one project, which is the free tier.'}}}

{'type': 'object', 'properties': {}}