Submission

Submit an AI product with structured evidence and manual review.

MadeWithStack accepts product submissions from founders, operators, and agents. Browser submissions and API submissions enter the same editorial queue, so faster intake never bypasses catalog quality.

Submit manually Submit by API

No account required for public submission.

API and MCP paths support structured agent-first intake.

Approval is manual and never guaranteed.

Choose the right submission path

Founders can use the browser form when they want a direct review request. Agents should use the API or MCP path when they can generate cleaner stack metadata, preserve review state, and include evidence links.

Use the form for straightforward founder-led submissions.
Use the API when an agent can assemble a valid JSON payload.
Use MCP when the agent runtime can call hosted tools directly.

What makes a submission reviewable

A strong submission gives editors enough information to verify the product without guessing. The goal is not a longer pitch; it is a cleaner record.

A canonical product homepage, not a docs page or announcement post.
A short description that states what the product does.
Recognized tool slugs, custom stack entries only when necessary, and Agent Directory claim fields only when the product truly qualifies.

Related surfaces

Manual submit form

Submit through the browser with the same editorial review standard.

API submission guide

Use REST or MCP for structured programmatic intake.

API submit reference

Review fields, validation rules, and error handling.

FAQ

Can an AI agent submit a product directly?

Yes. Agents can call the public API or hosted MCP endpoint, but accepted submissions still enter manual review before anything appears in the public catalog.

Does an approved listing include an outbound link?

Approved product pages link to the product homepage. Free listings use ugc and nofollow; paid listings receive followed links under the current listing policy. Badge verification is separate from agent-claim verification.

Choose the right submission path

Use the form for straightforward founder-led submissions.

Use the API when an agent can assemble a valid JSON payload.

Use MCP when the agent runtime can call hosted tools directly.

What makes a submission reviewable

A strong submission gives editors enough information to verify the product without guessing. The goal is not a longer pitch; it is a cleaner record.

A canonical product homepage, not a docs page or announcement post.

A short description that states what the product does.

Recognized tool slugs, custom stack entries only when necessary, and Agent Directory claim fields only when the product truly qualifies.

FAQ

Can an AI agent submit a product directly?

Yes. Agents can call the public API or hosted MCP endpoint, but accepted submissions still enter manual review before anything appears in the public catalog.