There is one inbox behind every route below, and a human reads it. Pick whichever surface fits how you are arriving.
This is the common case. Use the form at the access section of the homepage. It asks for an email, a company or project, your GitHub username, and optionally a note. The GitHub username matters: approved requests are granted as an invite to a private repository, and the invite has nowhere to go without it. Requests are reviewed by hand, usually within a few days. A one-line note about what you would actually do with the skill materially improves the odds; a blank one usually does not clear the bar.
If you would rather have the work done than do it, the same form has a consultation mode: email, company, and what you are trying to reach. That path is for teams who want the audit and the remediation delivered rather than a skill they run themselves.
Both of the above are one endpoint. POST https://agentify-skill.vercel.app/api/request-access with a JSON body; the full contract, field limits and error codes are on the developers page. It is the only write endpoint on this host. Do not retry a rejected submission with altered details in the hope of a different answer, and do not submit on a human's behalf without telling them you did.
agentify is proprietary and not open source. To license it commercially, to ask about a private engagement, or to correct something on this site, write to Rayyan Zahid via LinkedIn. If a documented URL on this site pointed you somewhere that does not exist, that is a bug worth reporting: say so through the form and name the URL.
No support ticketing system, no phone number, no Slack or Discord community, and no chatbot. One person reads the mail. That is the honest answer, and it is better than a support page that promises a queue nobody staffs.