Quality standards, pricing guidance, and support expectations for AOS creators. Follow these guidelines to build a successful agent business.
Every agent must include: workflow file (Make.com/n8n JSON), system prompt, setup documentation with screenshots, and configuration guide. Incomplete submissions are rejected.
Your agent must work as described. We test every submission. If core features don't function, it won't be approved. Test thoroughly before submitting.
Documentation should enable a technical user to install the agent without external help. Include prerequisites, step-by-step instructions, and troubleshooting tips.
Describe what your agent does and doesn't do. Overpromising leads to refund requests and bad reviews. Set accurate expectations.
Utility Agents: $99+ (simple automations). Revenue Agents: $299+ (direct business impact). Enterprise Systems: $999+ (complex multi-agent solutions).
Price based on the value delivered, not time spent building. An agent that books 10 meetings/week is worth more than one that sends notifications.
You can offer an optional Update Pass for ongoing updates and priority support. Monthly or yearly subscription. Buyers keep base license forever.
You keep 80% of every sale (90% for founding creators in first 90 days). AOS takes 20% for platform, payments, and support infrastructure.
You must respond to support tickets within 24 hours. Failure to respond leads to escalation and potential account penalties.
Help buyers get the agent working for 7 days post-purchase. This covers setup issues, not customization requests or scope expansion.
If your agent has a legitimate bug (not user error), you must fix it. Refusing to fix bugs leads to forced refunds and listing removal.
You're not obligated to: customize for specific use cases, integrate with unsupported platforms, or provide unlimited consulting. Define scope clearly.
A 5-10 minute video showing installation dramatically reduces support tickets. Highly recommended even though not required.
Include test scenarios and sample inputs so buyers can verify the agent works before connecting to real data.
What happens with unusual inputs? How does the agent handle errors? Document edge case behavior to set expectations.
When you update an agent, document what changed. Buyers need to know if they should re-download and what's different.
| Tier | Minimum Price | Examples |
|---|---|---|
| Utility Agent | $99 | Notification bots, simple data transforms, basic integrations |
| Revenue Agent | $299 | Lead qualification, meeting booking, follow-up sequences |
| Enterprise System | $999 | Multi-agent workflows, complex orchestration, custom integrations |
Before submitting your agent, ensure you have:
The following will result in listing removal and potential account suspension:
Ready to list your agent?