Adding AI Tools
Contribute to the AI Tools Directory by submitting new tools or updating existing ones.Before You Submit
Search for the Tool
- Visit devradar.dev/tools
- Search for the tool by name
- Check if it already exists
Verify Tool Information
Only submit tools you can verify:- Official website exists
- Active development (updated within 6 months)
- Clear description of capabilities
- Pricing information available
Required Information
| Field | Description | Example |
|---|---|---|
| Tool Name | Official name | Cursor |
| Category | Tool type | ai-ide, cli-agent, vibe-coding, managed |
| Website | Official URL | https://cursor.sh |
| Description | What it does | AI code editor with GPT-4 integration |
| Platforms | Supported platforms | desktop, web, cli |
| Pricing | Cost information | Free tier available, $20/month Pro |
| Privacy | Data handling | Trains on code, cloud storage |
| Evidence | Sources | Official docs, website, GitHub |
Tool Categories
AI IDEs
Code editors with integrated AI capabilities. Examples: Cursor, Windsurf, JunoCLI Agents
Terminal-based AI coding assistants. Examples: Aider, Trae, KiroVibe Coding
AI platforms that generate full applications from prompts. Examples: Lovable, Bolt.new, v0Managed Platforms
Cloud-based development environments with AI. Examples: Replit, Firebase StudioCapabilities to Document
| Capability | Description | How to Verify |
|---|---|---|
| SSR Support | Works with server-side rendering | Check docs/examples |
| Mobile | Supports mobile development | Framework mentions |
| Database | Can handle database operations | Features list |
| API | API development support | Documentation |
| Deployment | Can deploy apps | Platform features |
Verification Methods
Privacy Information
Accurate privacy information is critical:Data Training
| Model | Description | Example |
|---|---|---|
| Trains on code | Code used for model training | ”May use code for improvements” |
| Local-only | All processing on your machine | ”Data never leaves your device” |
| Optional | User can choose | ”Opt-in for training” |
Data Storage
| Model | Description | Example |
|---|---|---|
| Cloud | Stored on provider servers | ”Data stored securely in cloud” |
| Local | Stored on your device | ”All data local” |
| Hybrid | Mixed approach | ”Cache local, sync cloud” |
Submission Template
Method 1: GitHub Issue (Recommended)
Method 2: API Submission
Review Criteria
Accuracy Checklist
- Tool name matches official branding
- Website is official/current
- Category is correct
- Capabilities are verified
- Privacy info is accurate
- Pricing is current
- Evidence links work
Quality Checklist
- Description is clear and concise
- No marketing language (objective tone)
- Relevant details included
- Sources are authoritative
Review Process
| Stage | Duration | Action |
|---|---|---|
| Initial Review | 1-2 days | Verify completeness |
| Verification | 3-5 days | Test tool, check docs |
| Approval | Within 7 days | Add to directory |
Status Updates
- Received - Submission acknowledged
- Under Review - Being verified
- More Info Needed - We have questions
- Approved - Added to directory
- Declined - Cannot accept (reason provided)
Best Practices
1. Use Official Sources
2. Be Current
3. Be Specific
4. Verify Privacy Claims
Privacy claims are critical - double-check:5. Include Pricing Details
Vague pricing isn’t helpful:Examples
Example 1: AI IDE Submission
Example 2: CLI Agent Submission
Updating Existing Tools
Tool information changes - help keep it current:What’s Next
- Adding Compatibility Rules - Submit compatibility data
- Contributing Overview - Other ways to contribute
Submit now: Open an Issue →