Documentation menu ＋
submit_product
Prepare a Tool Atlas launch submission and finish it in the browser.
This page documents the Tool Atlas submission contract. It is not a hosted MCP tool endpoint. The safe flow creates or updates a submission record, but it never publishes a product or charges a plan from an agent call.
Start with the product URL
Open the launch form with a normalized URL. Tool Atlas will prefill what it can, and the owner can review every generated field before submitting.
https://toolatlas.io/submit/new?url=https%3A%2F%2Fyourproduct.com
Submission fields
The browser form validates the product name, HTTPS URL, category, pricing, short description, owner email, and optional media. A complete REST request uses the same validation rules.
POST https://toolatlas.io/api/submissions
Content-Type: application/json
{
"name": "Your Product",
"url": "https://yourproduct.com",
"category": "Developer Tools",
"pricing": "FREE",
"shortDesc": "A clear one-line description.",
"email": "you@example.com"
}What the request does
A valid request returns 201 with submission and site identifiers. Existing products become claim requests; new products enter the review queue. It does not publish immediately.
What happens next
- Review and edit the generated listing in the browser.
- Choose the launch plan in the browser. Paid plans continue to the existing checkout.
- Wait for Tool Atlas review and publication. Badge verification applies where the selected plan requires it.
Errors to handle
400 means validation failed or a media URL is unreachable. 401 means an account-only browser action was requested. 429 means slow down. 500 means the submission was not confirmed; check status before retrying.
Do not send
Never send passwords, one-time codes, payment details, or session tokens to this endpoint. Keep those steps in the Tool Atlas browser session.