Contribution paths for people who want to help inAi's public work: Open Source, documentation, examples, research notes, AI for Everybody, product feedback, translations, and public website improvements.
inAi builds AI-native products and open technology for the intelligence era.
Some people will work with inAi as employees, interns, contractors, investors, research partners, pilots, or testers. Others may want a lighter path: improving a public repository, correcting documentation, suggesting a useful example, writing a clear explanation, helping with a translation, reviewing a public page, sharing structured product feedback, or proposing a focused idea that can improve the public work.
This page is for that contribution path.
It is not a job application page, not an internship page, not a product-support page, not a generic contact form, and not a promise that every suggestion will be accepted. It is the place for serious public contributions to inAi’s Open Source projects, public documentation, product explanations, research-adjacent notes, AI for Everybody, website architecture, product feedback, and ecosystem work.
This page is for people who want to help inAi’s public work without necessarily starting a formal employment, internship, investment, research, or pilot conversation.
The best contributions are concrete. A useful contribution usually identifies a problem, proposes a fix, improves a public asset, adds an example, clarifies a page, corrects an error, or makes a public project easier to use.
Contributions should make public work better.
That public work may be a repository, a page, a guide, an explanation, a research-output list, a product-category description, an example, a translation, a form route, a documentation file, or a feedback report. The common point is simple: the contribution should help inAi bring AI into real products, real workflows, real agents, real Open Source tools, and real public understanding.
There are several useful contribution areas. Not all areas are always open for active collaboration, and not every contribution can be accepted. Still, these are the categories where public contribution can make sense.
Different contribution types should go through different paths.
A good contribution is useful, specific, and respectful of the project’s boundaries.
A contribution path should be honest.
inAi can offer a place where serious public contributions may improve real work: repositories, documentation, public explanations, product pages, research-adjacent notes, and website structure.
Depending on the contribution, inAi may offer review when capacity allows, discussion on GitHub or by email, public credit where appropriate and agreed, merge or publication if the contribution fits, follow-up conversation if the contribution suggests deeper collaboration, or a route toward Work with us, Internships, Testers, Academia / Research, or Partners where relevant.
But inAi does not guarantee response to every message, acceptance of every contribution, merge of every pull request, publication of every article, payment, employment, internship acceptance, investor access, formal partnership, public credit in every case, ongoing maintainer status, access to internal systems, or access to private roadmap or architecture.
The contribution path is open, but it is not automatic.
inAi may evaluate contributions based on relevance to current public architecture, whether it improves a real page or repository, accuracy, review scope, respect for maturity labels, avoidance of private material, unsupported claims, tone, maintenance burden, product/legal/trust/public-private boundaries, and whether the contributor has the right to share the material.
A contribution can be useful and still not be accepted.
Reasons may include timing, scope, quality, mismatch with current priorities, legal/IP concerns, unsupported claims, implementation burden, maintenance burden, or simply lack of capacity.
Do not send material unless you have the right to share it.
For repository contributions, the relevant repository license and GitHub contribution norms apply. Read the repository license and any contribution instructions before submitting code, documentation, examples, or other repository material.
For writing, research notes, translations, website copy, diagrams, examples, or product feedback, do not assume that sending material creates a confidential relationship, paid relationship, employment relationship, partnership, or obligation to publish. If a contribution becomes substantial, inAi may need a clearer agreement before using it.
If the rights situation is unclear, do not send the material in the first message. Describe the idea instead.
A useful contribution message should be short and specific.
Please include your name; the contribution area; the page, repository, or product category involved; what you noticed; what you propose; links to relevant work; whether you are proposing a one-time contribution or ongoing collaboration; any rights/license context if you are sending code, text, examples, research notes, translation, or design material; and the best way to contact you.
For GitHub contributions, include repository name, issue or pull request link, environment, reproduction steps, expected result, actual result, and proposed fix if any.
For writing or research contributions, include topic, target reader, suggested title or question, short outline, source notes, claim boundaries, and whether you want credit if published.
For website/copy corrections, include page URL, current wording, issue, suggested wording, and why the change improves clarity or claim safety.
Subject: Contribution — [Area] — [Your name]
My name is [name]. I would like to contribute to [repository / page / product category / AI for Everybody / Products for Agents / Open Source documentation].
I noticed [specific issue or opportunity].
I propose [specific contribution].
I have the right to share this material, and it does not include private customer, supplier, candidate, employer, or personal data.
For code and repository changes, GitHub issues or pull requests are usually better than email. For broader contribution ideas, use Contact or email contact@inai.world.
Use the route that matches the contribution.
For Open Source repositories, start from the relevant GitHub repository where possible. Use Open Source to find the public project list.
For general contribution ideas, use Contact if available, or email contact@inai.world.
For broader collaboration, use Partners or the relevant partner page.
For work or internship interest, use Work with us or Internships.
For product testing, use Testers.
For research collaboration, use Academia / Research or email research@inai.world.
For partnerships, pilots, grants, institutions, or investors, use the relevant partner page or email partnerships@inai.world.
