submit-to-agentlaunch

Send a POST request to the /agents endpoint with JSON containing name, tagline, description, and website_url. Fetch the /meta endpoint first to get valid category and pricing enum values, since invalid values return a 400 error.

The required fields are name, tagline, description, and website_url. Optional fields include api_docs_url, instructions_url, logo_url, category, pricing, and submitter_name, each with length and format limits defined in the /meta response.

No authentication is required. The API has no keys or bearer tokens, CORS is open on every endpoint, and there are no published rate limit quotas, though clients should avoid polling faster than once per minute.

A 409 means the website_url is already registered after normalization of host, www prefix, trailing slash, and query strings. Treat it as success and reuse the slug from the existing agent returned in the response body.

The logo_url must be a direct image link ending in png, jpg, jpeg, webp, svg, gif, or avif. URLs containing favicon in the path are rejected with a 400 error, so use a real square logo of at least 256 by 256 pixels.

No. Voting is limited to one vote per client IP per agent and is idempotent, returning 409 on re-votes. Looping, batching, or rotating IPs to inflate votes is detectable and results in removal of the submission.