Tools
Tools overview
Tools are the core execution units of the Rival platform. They encapsulate reusable logic that can process data, automate workflows, or expose functionality as callable endpoints.
A tool can be executed:
- Directly within the Rival platform
- Externally via API keys or cURL
Accessing public tools
Rival provides a Marketplace where all public tools across organizations are listed.
You can:
- Browse tools built by other developers
- Explore categories and sectors
- View tool details, usage, and performance
The Marketplace is publicly accessible - you can browse tools even without logging in.
Once logged in, you can:
- Run tools using your credits
- Favorite tools
- Leave reviews and participate in Q&A discussions with developers
Accessing your tools
All tools within your organization are accessible from the My Tools section.
Steps
- Log in to Rival
- Navigate to My Tools from the top navigation
This page provides a centralized view of all tools in your organization, along with operational insights such as:
- Total published tools
- Total executions (runs)
- Revenue generated
Each tool is displayed as a card containing:
- Tool name and type
- Visibility (Public / Private)
- Version
- Execution count
- Revenue
- Rating
You can also:
- Search and filter tools
- Sort by usage or performance
- Access favorited tools
- View associated digital assets
Tool card actions
Each tool card includes quick actions:
- Edit Tool
- Delete Tool (Owner/Admin only)
- Add to Favorites
- View in Marketplace
- Try (run the tool instantly)
- Preview (view details, versions, and configuration)
Creating a tool
Creating a tool defines executable logic that can be reused across workflows, APIs, or teams.
Step 1: Basic information
Provide the core metadata for your tool:
-
Tool name
Must be unique within your organization (different organizations can have tools with the same name). -
Short description
A concise summary displayed on tool cards and listings. -
Tool type
-
Category
Select one primary category for discovery. -
Sector
Select up to 4 sectors to improve discoverability. -
Tags
Freeform keywords for search and filtering. -
Runtime
Choose execution environment:- Python
- JavaScript
- Lua
-
Compute type
- CPU
- GPU
Click Save & Next to continue.
Step 2: Code & versions
This is where the core logic is defined.
You can:
- Write and edit code
- Add test cases
- Configure environment variables
Environment variables
Environment variables allow you to securely manage configuration values such as API keys, tokens, or constants.
- They are defined per tool
- Managed globally at the organization level via Workspace Settings
- Accessible across tool executions
Step 3: Icon & branding
Customize how your tool appears:
- Upload a custom icon
- Or generate one using AI
Step 4: Overview
Describe your tool in structured terms:
- What it does
- When to use it
- Strengths and limitations
You can use Generate from AI to auto-fill this section.
Step 5: Documentation
Provide a detailed markdown description of your tool.
This includes:
- Inputs and outputs
- Use cases
- Behavior and edge cases
Step 6: Publish
Finalize and release your tool.
You must provide:
- Version type (Patch / Minor / Major)
Rival automatically generates the version name based on your selection:
-
Patch →
0.0.1 → 0.0.2(bug fixes, small tweaks) -
Minor →
0.0.1 → 0.1.0(backwards-compatible changes) -
Major →
0.0.1 → 1.0.0(breaking changes) -
Changelog
-
Default use case / test case
Choose visibility:
- Private → internal use
- Public → listed in marketplace (requires pricing)
Click Confirm to publish.
Tool visibility
Tools can be either Public or Private.
Public tools
Public tools:
- Are listed in the Marketplace
- Require pricing per version
- Can be executed by external users
- Generate revenue
- Support ratings, reviews, and Q&A
Q&A allows users to ask developers questions directly, with answers displayed on the tool page.
Private tools
Private tools:
- Are accessible only within the organization
- Are not publicly discoverable
- Are used for internal workflows
Tool versioning
Every tool is managed through versions.
Each version represents a specific state of:
- Code
- Version name (auto-generated)
- Changelog
- Default test/use cases
- Environment variables (if modified)
Fixed properties per tool
The following cannot change across versions:
- Runtime
- Compute type
Version behavior
-
Private versions
- Can be edited
- Can be made public
-
Public versions
- Are immutable
- Cannot be modified
Automatic tool verification pipeline
Rival includes an automated verification pipeline triggered on every publish (private or public).
This pipeline:
- Validates tool behavior
- Detects security vulnerabilities
- Ensures execution integrity
Only approved versions can be made public.
Verification status
Inside Preview → Versions, you can see:
- Approved versions
- Versions flagged with issues
Deprecating vs deleting
Rival provides two mechanisms: Deprecation and Deletion.
Deprecation
Used for public tools or versions still in use.
When deprecated:
- Marked for removal
- Deleted after 30 days
- Notifications sent to creators and users
Tool-level
- All public versions are deprecated
- Removed from marketplace after grace period
- Cannot be edited anymore
- No new versions can be created
Version-level
- Only selected version is deprecated
- Other versions remain unaffected
Deletion
Deletion is immediate and permanent.
Allowed when:
- Tool/version is private
- No public versions exist (for full deletion)
Tool-level
- Removes entire tool and all versions
Version-level
- Removes only selected version
Favoriting tools
Favoriting allows quick access to frequently used tools.
How to favorite
- Go to My Tools or Marketplace
- Click the ❤️ icon
Access favorites
- Navigate to My Tools
- Open the Favorites tab