FAQ

This page answers common questions about developing, publishing, and monetizing components on the Mirra platform. Questions are organized by topic for easy navigation.

General

How do I become a developer?

Sign up for a Mirra account and access the developer dashboard at /developer. If you don't see the developer option, contact support to enable developer access for your account.

See Getting Started for complete setup instructions.

Is there a fee to publish resources or scripts?

No, publishing is completely free. You set your own pricing and keep the majority of revenue. Mirra takes a small platform fee to cover infrastructure costs.

See Creating Resources and Creating Scripts for publishing workflows.

How do I get paid?

Revenue is tracked in your developer dashboard. Payment details and schedules are provided separately. You receive payouts based on your earnings and the payment schedule.

See Managing Your Profile for revenue tracking and payment settings.

Can I publish for free?

Yes. You can offer free resources and scripts to build your user base and reputation. Many developers start with free offerings and add paid features later.

See Best Practices for strategies on pricing and monetization.

Resources

What API formats are supported?

The platform supports REST APIs with OpenAPI 3.0 specifications. Your API should return JSON and use standard HTTP methods (GET, POST, PUT, DELETE, PATCH).

See Resources for detailed specification requirements.

Can I update a published resource?

Yes, you can edit your resource anytime through the developer dashboard. Changes are reflected immediately. However, major breaking changes may affect existing users, so communicate updates clearly in your changelog.

See Handling Reviews for communicating changes to users.

How do I handle API keys?

Users provide their own API keys when installing your resource. You configure where and how the key should be sent (header, query parameter, etc.) in the resource's authentication settings.

See Creating Resources for authentication setup.

What authentication methods are supported?

The platform supports multiple authentication methods for resources:

None: Public APIs that don't require authentication
API Key: Simple key-based authentication via headers or query parameters
OAuth 2.0: Industry-standard authorization protocol for secure delegated access
Bearer Token: Token-based authentication using the Authorization header
Basic Auth: Username and password authentication encoded in Base64

See Resources Authentication for implementation details.

Can I use my own domain?

Resources use your API's existing domain. Users make requests directly to your endpoints through the Mirra platform, which acts as a proxy and handles authentication injection.

See Resources for architecture details.

Scripts

What languages are supported?

The platform currently supports two runtime environments for scripts:

Node.js 18: JavaScript and TypeScript with full npm package support
Python 3.11: Python with pip package support for data processing and machine learning

More runtimes may be added based on developer demand. See Scripts for runtime specifications.

What's the execution time limit?

The default execution time limit is 30 seconds per script invocation. Contact support if you need higher limits for specific use cases.

See Scripts for performance considerations.

Can scripts access external APIs?

Yes, scripts can make HTTP requests to external services using standard libraries (fetch, axios, requests, etc.). You can also use other Mirra resources within your scripts for authenticated API access.

See Script Examples for API integration patterns.

How do I debug scripts?

Use the built-in test panel in the developer dashboard to debug your scripts:

Execute with test data
View console.log() output
See error messages and stack traces
Check execution time and performance

See Creating Scripts for debugging workflows.

What packages are available?

Common packages are pre-installed in both Node.js and Python runtimes. You can specify additional dependencies directly in your script code, and they will be installed automatically.

Contact support to request packages that require special permissions or system-level access. Requests are evaluated based on security and demand.

See Scripts Dependencies for package management.

Can I use environment variables?

Yes, you can configure environment variables for your scripts in the developer dashboard. Environment variables are encrypted at rest and only accessible during script execution.

See Creating Scripts for configuration instructions.

Pricing & Revenue

How should I price my work?

Research similar offerings in the marketplace and consider these factors:

Value provided - What problems does your component solve?
Your costs - API fees, hosting, development time
Market rates - What do competitors charge?
Target audience - Enterprise vs. individual developers

Start with competitive pricing and adjust based on user feedback and usage patterns.

See Best Practices for detailed pricing guidance.

Can I change pricing later?

Yes, you can change pricing anytime through the developer dashboard. However, pricing changes may affect existing users. Consider these strategies:

Grandfather existing users - Keep them on current pricing
Give advance notice - Announce changes 30-60 days ahead
Explain the reasons - Communicate value improvements
Offer migration options - Provide alternative plans

See Best Practices for managing pricing updates.

Mirra takes a platform fee to cover infrastructure, payment processing, and support. The exact percentage is communicated separately. You keep the majority of revenue from your published components.

See Managing Your Profile for revenue details.

When do I get paid?

Payouts are processed on a regular schedule (monthly or quarterly depending on your earnings). Minimum payout thresholds apply to reduce transaction costs.

See Managing Your Profile for payout schedules and thresholds.

Can I offer free trials?

Yes, you can configure free tiers or trial periods for your components. This is an effective strategy to let users test functionality before committing to paid plans.

See Best Practices for trial and freemium strategies.

Profile & Reviews

Can I delete negative reviews?

No, reviews cannot be deleted by developers or users. However, you can reply to reviews to address concerns and demonstrate responsiveness. Well-handled negative reviews can build trust by showing you care about user feedback.

See Handling Reviews for strategies on responding to feedback.

How are ratings calculated?

Ratings are calculated as the average of all user ratings on a 1-5 star scale. Each user can rate each resource or script once. Ratings update in real-time as new reviews are submitted.

See Handling Reviews for details on the rating system.

Can I change my display name?

Yes, you can change your display name anytime in your profile settings. However, this may confuse existing users, so choose your initial name carefully. Your display name appears on all your published work.

See Managing Your Profile for profile customization.

How do I remove my avatar?

Clear the avatar URL field in your profile settings and save. A default placeholder will appear with your initials.

See Managing Your Profile for avatar configuration.

Can I have multiple profiles?

No, the platform supports one developer profile per account. However, you can represent a company or team under a single profile by choosing an appropriate display name and avatar.

See Managing Your Profile for profile setup.

Technical

What's the rate limit for the platform?

Platform rate limits are generous and designed to prevent abuse while supporting legitimate use. If you hit rate limits, contact support to discuss your specific needs and request higher limits.

See Getting Started for current rate limit specifications.

How is data stored?

User data and credentials are encrypted at rest and in transit using industry-standard encryption protocols. The platform follows best practices for security and privacy, including regular security audits.

See Authentication for security details.

Can I see usage analytics?

Yes, your developer dashboard displays comprehensive analytics:

Total users and installations
API calls and script executions
Revenue and earnings trends
Ratings and review summaries
Performance metrics and error rates

See Managing Your Profile for analytics features.

The Mirra platform is GDPR compliant. Users control their data and can request deletion at any time. As a developer, ensure your resources and scripts also comply with privacy regulations including GDPR, CCPA, and other applicable laws.

See Best Practices for privacy guidelines.

How do I report a bug?

Report bugs through the feedback form in the developer dashboard or email support@oznetworks.xyz. Include these details for faster resolution:

Detailed description of the issue
Steps to reproduce the behavior
Expected vs. actual behavior
Screenshots or error messages
Browser and operating system (if relevant)

See Introduction for support channels.

Support

Where can I get help?

The platform provides multiple support channels:

Documentation: Comprehensive guides, API reference, and examples at docs.fxn.world
Discord: Real-time community support and discussions with other developers
Email: Direct technical support at support@oznetworks.xyz
GitHub: Bug reports and feature requests through issue tracking

See Introduction for support details and links.

How quickly will support respond?

The support team aims to respond within 24-48 hours for most inquiries. Critical issues affecting production systems are prioritized for faster response. Community support on Discord is often faster for general questions.

See Introduction for support SLAs.

Can I request new features?

Yes. Feature requests are welcome and help shape the platform roadmap. Submit requests through:

Discord community - Discuss ideas with other developers
Email support - Detailed feature proposals to support@oznetworks.xyz
GitHub issues - Formal feature requests with use cases

Popular requests with strong use cases are prioritized in the development roadmap.

See Introduction for the feature request process.

Is there a developer community?

Yes. Join the Discord server to connect with other developers building on the Mirra platform:

Connect with other developers
Share tips and best practices
Get help from the community
Provide feedback on features
Stay updated on new releases and features

See Introduction for community links.

Best Practices

How often should I update my work?

Regular updates demonstrate active maintenance and build user trust. Maintain your published components by:

Fix bugs promptly - Address reported issues quickly
Add requested features - Respond to user feedback
Update documentation - Keep examples and guides current
Respond to reviews - Engage with user feedback
Keep dependencies current - Update packages for security and performance

See Best Practices for maintenance strategies.

Should I offer a free tier?

Yes, free tiers are recommended for most components. Benefits include:

Build user base - Lower barrier to adoption
Get feedback - Learn from real usage patterns
Establish reputation - Build trust through reviews
Lead to paid conversions - Users upgrade after seeing value

See Best Practices for freemium strategies.

How do I handle breaking changes?

Communicate breaking changes clearly to minimize user disruption:

Announce in advance - Give users 30-60 days notice
Explain the reasons - Communicate the benefits
Provide migration guide - Document upgrade steps
Offer support - Help users through the transition
Consider versioning - Maintain old versions temporarily

See Best Practices for change management.

What makes a resource successful?

Successful resources and scripts share these characteristics:

Quality: Reliable, well-tested, and performant code
Documentation: Clear setup instructions, examples, and troubleshooting guides
Support: Responsive to user questions and feedback
Pricing: Fair, competitive, and aligned with value provided
Updates: Regular improvements, bug fixes, and feature additions

See Best Practices for comprehensive success strategies.