Skip to main content
Managing AI agents in the Swarms marketplace is simple—just follow 3 easy steps:
  1. Authenticate: Secure your requests with an API key or Supabase session token.
  2. Create, Update, or Query Agents: Use the endpoints below to add, modify, or search agents.
  3. Get Results or Listings: Instantly receive confirmation, your agent listing URL, or search results.

Step 1: Authentication

All agent management actions require authentication using one of these methods:
  • API Key: Send your API key in the Authorization header as Bearer <your-api-key>.
  • Supabase Session: Provide your Supabase session token in the Authorization header.

Base URL


Step 2: Create an Agent

It’s quick and easy to create your own agent in the marketplace.

Endpoint

Input schema (Add Agent)

Request Body (detailed)

Just provide the necessary agent details:
name
string
required
The name of the agent (minimum 2 characters)
agent
string
Agent code/content (minimum 5 characters if provided); can be null
description
string
required
A detailed description of what the agent does
language
string
Programming language used (e.g., “python”, “javascript”)
requirements
array
An array of package requirements
useCases
array
An array of use cases showing what your agent can do
tags
string
Comma-separated tags (minimum 2 characters if provided)
is_free
boolean
default:"true"
Whether the agent is free or paid
price_usd
number
Price in USD (required if is_free is false, minimum: 0.01)
category
string
The agent’s category (e.g., “data-science”, “automation”)
status
string
default:"pending"
The status of the agent (pending, approved, rejected)
image_url
string
Public image URL (valid URL or empty string)
file_path
string
Storage path for image (alternative to image_url)
image_base64
string
Base64-encoded image (alternative to image_url; can include data:image/...;base64, prefix)
Links: array of strings or { "name": string, "url": string } (e.g. website, twitter, telegram for token metadata)
seller_wallet_address
string
Seller wallet address
x402_url
string
x402 payment URL (valid URL or empty string)
mcp_url
string
MCP server URL (valid URL or empty string)
tokenized_on
boolean
Enable tokenization on Solana
ticker
string
Required when tokenized_on is true; uppercase letters and numbers only; max 10 characters
creator_wallet
string
Creator wallet public key; required when tokenized_on is true
private_key
string
Private key for signing (JSON array or base64); required when tokenized_on is true

Validation rules

  • Paid agents: When is_free is false, price_usd is required and must be > 0.
  • Tokenization: When tokenized_on is true, ticker, creator_wallet, and private_key are required; ticker must be uppercase alphanumeric, max 10 characters.
  • Duplicate: Same name and same agent content for the same user returns 400 with existingId.

Success response (200)

On success, you’ll immediately get:
When tokenization is used, tokenized is true and token_address and pool_address are set.

Output schema (Add Agent — success)

Error responses (Add Agent)

  • 400 – Validation: error, message, details, errors, status_code. Content validation: also trustworthiness, contentQuality. Duplicate agent: existingId. Tokenization failed: standard 400 shape.
  • 401error, message, details, how_to_get_key, status_code.
  • 429error, message, details, currentUsage, limits, resetTime, status_code.
  • 500 – Server/database/price conversion/tokenization error: error, message, details, status_code (may include hint, code for DB errors).

Error output schema (common fields)

Example Request


Step 3: Update or Query Agents

You can easily change agent info or search/filter agents—just as effortlessly as creating one!

Update Agent

Endpoint

Request Body

All fields from the create agent endpoint are available, plus:
id
string
required
The unique ID of the agent you want to update

Example Request

Success Response


Query Agents

Endpoint

Request Body

Keyword to match agent names/descriptions
category
string
Filter by category (case-insensitive)
priceFilter
string
default:"all"
Filter by price: “all”, “free”, or “paid”
userFilter
string
Filter by user ID
sortBy
string
default:"newest"
Sort order: “newest”, “oldest”, “popular”, or “rating”
limit
number
default:"6"
Number of agents to return (1-100)
offset
number
default:"0"
Offset for pagination

Example Request

Example Response


Rate Limiting

All agent management endpoints are subject to rate limiting:
  • Daily Limit: 500 agents per user per day
  • Reset Time: Midnight UTC
If you exceed the limit, you’ll receive a 429 error response:

Error Responses

The API uses standard HTTP status codes to signal errors:
  • 200: Success
  • 400: Bad Request (validation errors)
  • 401: Unauthorized
  • 403: Forbidden (content validation failed)
  • 404: Not Found
  • 429: Too Many Requests
  • 500: Internal Server Error

Example Error Response

All endpoints return consistent error responses:
Validation errors may include details, errors, and status_code. Duplicate agent responses include existingId. Rate limit (429) responses include currentUsage, limits, and resetTime. Authentication (401) responses may include how_to_get_key.

Content Validation

Every agent undergoes automated checks, including:
  • Duplicate Detection: Same name and same agent content for the same user returns 400 with existingId
  • Quality Assessment: Checks code completeness and standards
  • Security Scanning: Ensures code is safe
  • Trustworthiness Scoring: Rates each agent on quality and trust (content validation responses may include trustworthiness, contentQuality)
Agents failing validation will get a 403 Forbidden or 400 Bad Request with detailed reasons.
In summary: you can create, edit, or search for agents in the Swarms marketplace in just 3 easy steps!