Use OxCode regularly
Build real projects so feedback comes from actual engineering work.
Ambassador Program
OxCode Ambassador Program
A practical handbook for contributing, earning XP, and representing OxCode responsibly as an early builder.
OxCode Ambassador Program
Welcome to the OxCode Ambassador Program.
This guide explains how you can contribute, earn XP, and represent OxCode responsibly as one of our early builders.
The Goal
The Ambassador Program exists to help us build a better product together.
We value genuine usage, thoughtful feedback, and meaningful contributions far more than volume. Quality will always outweigh quantity.
The goal isn't to collect XP. It's to help build a better AI Software Engineer for everyone.
Ways to Contribute
Contribute through real usage, clear evidence, and helpful community work. The team reviews referrals, bug reports, feedback, and other submissions manually.
Report bugs
Send reproducible issues, broken workflows, bad outputs, and errors.
Share feedback
Explain what worked, what felt confusing, and what slowed you down.
Suggest features
Share ideas that would make OxCode more useful in real projects.
Build projects
Show what you built with OxCode and what the workflow looked like.
Create tutorials
Teach practical workflows through demos, videos, articles, or guides.
Share on social media
Post honest experiences, useful workflows, and product updates.
Refer developers
Invite builders who would genuinely use OxCode, not passive signups.
Organize university initiatives
Run coding club intros, campus workshops, or hands-on sessions.
Help other users
Answer questions, share examples, and help builders get unstuck.
01
Refer developers with your code
Copy your unique referral code from the dashboard and send invited builders to oxcode.oxlo.ai/request-access. They must enter the code while requesting access.
02
Report problems with enough context
Include what you asked OxCode to do, what happened, what you expected, any error message, the relevant file or command, and clear reproduction steps.
03
Submit feedback from the dashboard
Good feedback names the task, explains what happened, and describes how the experience could improve.
Sharing your referral code does not guarantee approval. Every access request is reviewed individually by the OxCode team.
Do not share API keys, passwords, private credentials, confidential source code, or customer data in reports, forms, chats, or community channels.
XP Guide
XP is a signal of contribution quality and impact. It is not awarded automatically when a form is submitted.
| Contribution | Typical XP |
|---|---|
| General product feedback | 10-30 XP |
| Detailed product feedback | 30-75 XP |
| Feature suggestion | 20-60 XP |
| Feature adopted | 100-300 XP |
| Minor bug | 20-50 XP |
| Reproducible bug | 50-100 XP |
| Critical bug | 100-300 XP |
| Public social media post | 30-75 XP |
| High-quality article | 75-200 XP |
| Tutorial / Demo | 100-300 XP |
| Project built with OxCode | 100-500 XP |
| University workshop | 200-500 XP |
| Coding club introduction | 200-600 XP |
| 7-day streak | 70 XP |
| 2-week streak | 150 XP |
| Monthly streak | 400 XP |
| Activated referral | 50-150 XP |
| Power-user referral | 150-300 XP |
| Exceptional contribution | Team discretion |
XP is reviewed manually by the OxCode team. The ranges above are guidelines. Quality and impact always matter more than quantity.
Sharing About OxCode
Share practical, honest examples that help other developers understand what OxCode can do.
Things you builtInteresting workflowsHonest experiencesTutorialsProduct updatesComparisons based on your own usage
Honest feedback, including constructive criticism, is far more valuable than exaggerated praise.
Brand Kit
OxCode brand resources
The Brand Kit includes logos, icons, screenshots, product images, and brand resources for public content.
Suggested Hashtags
#OxCode#AISoftwareEngineer#AIEngineering#BuildWithOxCode#FoundingBuilder
Use hashtags only where they naturally fit your content.
Mentioning OxCode
LinkedInOxCode
Things to Avoid
Represent OxCode honestly. Do not trade trust for reach.
Sharing confidential featuresLeaking unreleased screenshotsMisrepresenting capabilitiesUnfair competitor attacksSpamFake engagementFake referralsDuplicate accountsMisleading tutorials
If you're unsure whether something can be shared publicly, ask the team first.
Reporting Bugs & Feedback
Submit reports and feedback through the dashboard so the team can track issues, prioritize improvements, allocate XP correctly, and keep reports organized.
01
Dashboard
Start from your OxCode dashboard so the report is tied to your account.
02
Bug report / feedback
Choose the right submission type and include enough context to act on it.
03
Reviewed by team
The OxCode team reviews submissions for clarity, impact, and product relevance.
04
XP allocation
Qualified contributions are considered for manual XP assignment.
05
Product improvements
Strong signals feed directly into fixes, roadmap decisions, and product polish.
Reports shared only in WhatsApp may not always qualify for XP because they cannot be tracked efficiently.
Referrals
Referral XP is awarded based on activation and genuine product usage. Simply signing up does not qualify.
Quality referrals are always valued more than inactive signups. Invite developers who are likely to build, test, give feedback, and stay engaged.
Leaderboard
Rankings consider overall contribution across product usage, feedback, bug reports, feature suggestions, activated referrals, community initiatives, projects, tutorials, missions, and social contributions.
The leaderboard rewards long-term contribution, not short-term activity.
Need Help?
Questions about the program?
If you have questions about XP, missions, referrals, or the Ambassador Program, reach out through the Founding Builders WhatsApp community.
We're excited to build OxCode together.