Skip to content
Rival Docs

Importing & Exporting Agents

Overview

An agent can be exported as a single portable JSON file and imported into any other Rival workspace - a colleague’s organization, a second environment, or a backup you keep yourself. The file carries the agent’s design: instructions, personality, tools, sub-agents, knowledge, and rituals. It never carries API keys, connected accounts, or memory - whoever imports it supplies their own.

Both actions live on My Tools (/my-tools).

Exporting an agent

  1. On My Tools, open the ⋯ menu on the agent’s card and choose Export.

  2. The Export agent dialog shows a preview of the JSON. Click Download to save it as Name.agent.json, or Copy JSON to put it on the clipboard.

Export is offered to anyone who can open the agent with Editor access - its creator, an org Owner or Admin, or an Editor on a team that holds it. Executors on a team can run the agent but don’t see Export, since the file is the whole design and outlives the grant that produced it. You also need an active agent seat.

An adopted agent whose instructions the publisher locked can’t be exported - the lock exists to keep the instructions private.

What the file contains

  • Name, description, instructions, theme, avatar, and categories
  • Personality and guardrails
  • The LLM provider and model choice, and artifact settings
  • Tools - a reference to each attached tool, plus the names of any external keys it needs
  • Sub-agents, including their own tools and nested sub-agents
  • Knowledge - files travel as extracted text (up to 200,000 characters per item), not as the original bytes
  • Rituals, schedules, and eval definitions
  • A list of which connectors the agent uses

What is never included

  • API keys, bring-your-own-model keys, and the secrets behind external keys - only the names of required keys travel
  • Connected accounts (Gmail, Calendar, and other connectors)
  • Conversations and memory
  • Eval runs and scores, ritual and schedule run history
  • Custom-endpoint or internal-only models - the copy opens on the platform default instead

Importing an agent

  1. On My Tools, click Create, hover over New Agent, and click the Import chip that appears beside it.

  2. In the Import an agent dialog, click Choose a .json file, or paste the JSON into the text box.

  3. Click Import. The agent is created and opened for you, with a summary of anything that needs attention.

Importing always creates a new agent - nothing existing is overwritten. If an agent with the same name already exists, the import is named Name (2), and you’re told so. Importing the same file twice gives you two agents. Any member with an active agent seat can import.

After the import

The summary tells you what resolved and what didn’t:

  • Tools are matched to tools in your workspace. A tool resolves if it’s public on the marketplace or belongs to your organization. Tools that don’t resolve are listed under Tools to replace - the agent is still created, just without them. Attach something equivalent from the marketplace.
  • External keys - tools that need a key are attached with no key chosen. Pick your own secrets on the agent’s tools panel.
  • Connectors need connecting in your workspace. An export never carries an account.
  • Scheduled rituals arrive switched off. Turn them on once you’ve checked them.
  • Sub-agents are created as written. A sub-agent’s tool that doesn’t exist in your workspace fails at run time and shows on that sub-agent’s own panel, rather than in the import summary.
  • Model - if the original used a custom or internal-only model, the copy runs on the platform default until you change it.

Next steps