Quickstart
You’ll create an account and either use a tool from the Marketplace or build your own through RivalBot. Plan on about five minutes.
1. Sign up
Go to cortexone.rival.io. Sign up with Google or GitHub, or with your name, email, and a password. You’ll then:
- Verify your email - enter the one-time code (OTP) we send you (Google and GitHub sign-ups skip this)
- Choose a plan - the Free plan is one click and needs no card
You land in the app on the Free plan, ready to build - upgrade any time from Billing. Every account works inside an organization (your workspace), set up as part of sign-up.
The left sidebar nav has Search, Marketplace, My Tools, Build, and Projects. On its bottom, it has the Organization popup and Settings options.
2. Pick a path
You have two ways to get something running. Either works.
Option A - Use a tool or Adopt an agent from the Marketplace
- Open Marketplace from the left sidebar nav (also at /marketplace)
- Browse or search for a tool/agent that matches your needs
- Click on the tool/agent, then Run - fill the input and execute right from the details page
- Favourite the tool or adopt the agent to save it and use in future
Option B - Build your own with RivalBot
- Open Build page at cortexone.rival.io/studio
- In the “What do you want to build?” prompt, describe what you want - e.g. “A tool that takes a URL and returns the page title and meta description.”
- RivalBot generates code, an input schema, test cases, and metadata, then hands you off to Studio
- Review, click Run in the Preview panel, and publish when you’re happy
See Creating a Tool for the full step-by-step builder walkthrough.
3. Call your tool from code
Every tool exposes an API endpoint. Create an API key from settings, then POST to your tool with a JSON event body. See the Developer Guide for the full request shape and language examples.
What’s next
- Create a tool - full step-by-step builder
- Create an agent - build a Rival Agent that chats and calls tools
- Run Balance - how runs are charged
- FAQs - common questions about credits, publishing, and plans