Submit your app
Three ways, all free. There is no account to create and no review queue. A bot checks the file and lists it within a minute or two.
-
Send your agent a link
Your agent writes a setup file, puts it on your site and submits it. You approve each step.
Follow https://setupmd.com/setup.md to list my app on setupmd. -
Paste a link to your file
Already have
yourapp.com/setup.md? Paste it and a bot lists it in a minute or two. -
Upload the file
No way to host it? Drop the file into a GitHub issue, and prove the domain with one meta tag.
What gets listed
- A markdown file on your own domain, served over https. Or an uploaded file, with the domain proved.
- Named
setup.md,install.md,skill.md,agents.mdoryourapp.md. - At the top of your site, or in
/docs/or/.well-known/. - The summary comes from your file: its
descriptionfront matter, or its first paragraph. - It has to pass the check, and it is checked again every day.
- Your GitHub account must be at least 30 days old.
A good setup file
- Opens by saying what gets installed, and what it will never do.
- Marks each step the person has to do, like a browser sign-in.
- Has a section for each agent you support.
- Ends with a free check that it worked, and how to remove it.
Proving your domain for an upload
A file on your own site proves itself. An uploaded file needs one of these, naming the GitHub account that posts it, so nobody can list your app for you.
# On your home page, inside <head>
<meta name="setupmd-verify" content="your-github-username">
# Or a DNS TXT record
_setupmd.yourapp.com TXT "github=your-github-username"
Submitting from the command line
What an agent runs, with its person's OK. Use cases are optional: valid ones are the names on the use case pages.
# A file on your site
gh issue create -R shansabnani/setupmd \
--title "submit: https://yourapp.com/setup.md" \
--body "use_cases: email, automation"
# Or upload one, once the domain is proved
gh issue create -R shansabnani/setupmd \
--title "submit: yourapp.com" --body-file setup.md