Skip to main content
Once your Relevance Builders profile is set up and ready to go, you can start submitting Agents!

​
How to submit your Agent

To submit an Agent to the Marketplace:
1

Navigate to your Agent

Go to the Agent you want to submit in your project.
2

Open submission

Click the “Submit to Marketplace” button or navigate to the Relevance Builders section and select “Submit new listing”.
3

Fill in listing details

Enter a title and description for your listing. Make sure these meet the requirements outlined below.
4

Set pricing

Choose whether your listing will be free or paid. If paid, set your price (up to $1000 USD).
5

Submit for review

Click “Submit” to send your Agent for review by the Relevance team.

​
Is there an approval process for submitted agents?

All agents submitted to the marketplace will be reviewed by the internal Relevance team. Agents must follow our agent building best practices to ensure all listed agents are usable, reliable, and valuable to the community. If your agent requires updating, the Relevance team will reach out with specific and actionable feedback to update your submission so that your agent can be approved the next time you submit it.

​
Can I push changes and updates to your Agents and Tools once they are approved?

Yes you can! To do this, head to the Agent / Workforce / Tool that has been submitted to Marketplace, make changes and then click ‘Update Marketplace listing’. The new changes will be sent for approval, and once approved, your Marketplace listing will point to the new version of your Agent / Workforce / Tool.

​
Approval requirements for submitting marketplace Agents

You can use the below list as a checklist to tick off before submitting your agent, to make sure it meets the approval criteria.

​
Do not include Sub-Agents

Agents that use Sub-Agents will not be approved, as Sub-Agents is now a legacy feature. Instead, we suggest that you wait until Workforces can be submitted (coming soon).

​
Listing title and description

When you submit an Agent, you will enter a custom title and description.
The title of your Agent must clearly describe what the focus of the Agent is. This should not be longer than 50 characters. You can give the Agent a name if you like, but this is not required.Examples: “Atlas, the Account Analyst”, “Google Calendar Meeting Notetaker”
Your description should start with a short paragraph outlining exactly what your agent does and how it works. After the initial paragraph, you can add some more detail on how the agent works if you would like. You can also link to publicly accessible help docs (e.g. public Notion pages) if you would like - this will help with your agent’s supportability and help get it approved.

​
Agent core prompt

In order to help the user understand what the agent is doing, we recommend you leave comments throughout your core prompt to explain what the agent is doing. You can also leave comments detailing how the user can edit, change, or extend their agent, such as by adding knowledge or suggested triggers. The agent core prompt should be optimised to ensure reliable accuracy and performance. This responsibility is up to you to ensure the agent is performing well and the core prompt following prompt engineering best practices. You can also use comments to link to publicly accessible help docs, or video demos, about how to use the Agent.

​
Tools that require OAuth

If your agent has tools that require OAuth to run, you must make sure these settings are surfaced as required tool inputs. This will allow the user to fill these out when the ‘missing tool inputs’ modal is shown while setting up the agent. Agents that use tools that require OAuth within tool steps that are not surfaced as inputs will not be approved.

​
Using API keys

If you have a tool that requires an API key to work, and we do not have a native OAuth solution for that API key, you will need to create a tool input of type ‘Text’, leave it empty, and provide instructions in the input description on where and how the user can create the API key. For example, you can include a link to relevant docs from the 3rd party tool explaining how to create an API key.

​
Tool inputs

At this stage we do not accept tools which use:
  • The Knowledge feature (in the left side menu in tool builder)
  • Have knowledge table type input fields
Please make sure that the description fields for all tool inputs clearly describe exactly how a user or agent should fill in this input. These descriptions are used by the agent to know how to fill a field reliably, so make sure any critical requirements or guidelines are included in the input description.

​
Agent variables

Agent variables will be copied over when a marketplace listing is cloned, as long as they are not knowledge tables, API keys or OAuth accounts. It is best practice to save any information in the agent core prompt that can be customised for each user as a variable. Good examples include company name, company descriptions, output formatting guidelines, etc.

​
What do I do if my agent is not approved?

If your agent is not approved, the Relevance team will reach out with specific and actionable feedback. You’ll need to make the requested changes to your Agent and then resubmit it to the Marketplace for review.

​
What doesn’t get copied over when users clone your listing?

We currently do not copy over any knowledge tables along with your listing. We plan to add this soon, but in the meantime, we suggest creating a variable and add the knowledge content to that variable. You can then add that variable to the agent’s core instructions.
Triggers will not get carried over, but we will suggest triggers for the user to set up based on the triggers attached to the agent when you submit it - so make sure you have triggers set up when you submit if you think the agent needs them.
Please use agent variables rather than global snippets, as global snippets don’t copy over.
If you have an agent that uses secrets, these should be surfaced as tool inputs of type API key or OAuth so the user can fill them out when setting up the agent. Do not use secrets.
The following tool input or variable types will not have their default values carried over:
  • Knowledge table (avoid using this input type)
  • API key (the user will have to fill this in)
  • OAuth account (the user will have to fill this in)

​
Submission checklist

Before submitting your Agent, make sure you’ve completed the following:
  • Guide for using Agent: Added a ‘Guide for using agent’ in Advanced Settings that tells users how to use the agent or provides examples to test with
  • No Sub-Agents: Confirmed your Agent doesn’t use Sub-Agents
  • Clear title and description: Written a clear, descriptive title (under 50 characters) and created a comprehensive description with usage instructions
  • Optimized core prompt: Added comments explaining what the Agent does, included instructions for customization, and followed prompt engineering best practices
  • OAuth and API keys: Surfaced all OAuth requirements as required tool inputs and provided clear instructions for any API keys needed
  • Tool inputs: Avoided using Knowledge or knowledge table inputs and written clear descriptions for all tool inputs
  • Variables: Used agent variables for customizable information and avoided using global snippets or secrets

​
Next steps

Once your Agent is approved, you can start earning from your listings! Learn more about getting paid for your Agents.