Skip to content
Rival Docs

Community & Support

If you run into a problem, have a billing question, or want to report unexpected behavior, this page tells you how to reach us and what to include so we can help quickly.

Contact support

Email support@rival.io for any account, billing, or technical issue. This is the primary support channel for all Rival users.

What to include in your support request

The faster you give us context, the faster we can help. When writing to support, include:

  • Your organization name (as it appears in your workspace)
  • What you were trying to do - describe the action or workflow
  • What actually happened - the behavior you observed
  • Any error messages you received - copy them exactly, don’t paraphrase

Reporting a bug

If you’re reporting a bug with a specific tool execution, also include:

  • The tool ID and version you were running
  • The input that triggered the issue (or a minimal reproduction)
  • The error response - including any HTTP status code or error reference code
  • A link to the run in Run History (under My Tools) if available

A precise bug report is the single biggest factor in how quickly an issue gets resolved. Vague reports (“it didn’t work”) are hard to act on; specific ones (“here’s the exact input and here’s the exact error”) get fixed.

Common things to check first

  • 402 errors - your Run Balance is empty. Top Up from Billing.
  • 401 errors - API key missing or wrong header. Pass as Authorization: <key>, no Bearer prefix.
  • 408 timeouts - your run exceeded the 300s limit.
  • Cryptic handler errors - open the run in Run History and inspect the full trace.

See the full Error Reference for codes and fixes.

Additional resources

  • Documentation - the full Rival docs are at docs.rival.io. The search bar at the top of any page covers all content.
  • Marketplace - browse and run tools at cortexone.rival.io/marketplace. Reading well-built listings is a fast way to learn what good looks like.
  • FAQs - quick answers about credits, publishing, and plans.

Community

Join the community forum: rival.discourse.group