Submit your SaaS from an AI agent or terminal.
Give an agent a public product URL. SubmitForBacklinks prepares the listing draft, preserves owner review, and accepts a free submission through a documented API, CLI, or remote MCP endpoint.
Owner-controlled automation
One workflow from public URL to reviewed listing.
Scan the public site
The stateless scanner reads public product pages and proposes structured listing copy with source URLs, confidence, and warnings. It does not reserve the domain.
Review and correct the saved draft
The owner or authorized agent retrieves the exact saved fields, corrects them if needed, and reviews the resulting name, copy, category, pricing, platform, and tags.
Confirm the rules
Final submission requires explicit confirmation of the terms, badge requirement, authority to represent the product, and content review.
Track editorial status
Authenticated clients can retrieve owner-scoped submissions without exposing private dashboard sessions.
Public first step
Let the agent inspect before it authenticates.
Site scanning is public. The CLI can then verify product-domain control and store its credential automatically—no copied API key, email code, or .env file. A one-use claim link is available only when the owner wants dashboard editing too.
curl --fail-with-body --request POST \
https://submitforbacklinks.com/api/v1/agent/scan \
--header "Content-Type: application/json" \
--data '{"websiteUrl":"https://yourproduct.com"}'Automation does not bypass editorial review.
Agents can prepare and transmit a submission. They cannot buy approval, guarantee rankings or traffic, or silently accept terms for a product owner.
- A real, publicly reachable product is required.
- Terminal ownership is established by a short-lived proof on the product domain.
- The caller must be authorized to represent it.
- Generated content must be reviewed for accuracy.
- Optional logo and screenshots are managed in the signed-in browser dashboard.
- Free dofollow treatment requires badge verification.
Choose a client
The same contract, three ways to use it.
REST and OpenAPI
Use the versioned JSON API directly or generate a client from the OpenAPI 3.1 contract.
Terminal CLI
Install the single-file CLI to scan, review, update, submit, verify the badge, and track status.
Remote MCP
Connect a client that supports custom Authorization bearer headers to purpose-built MCP tools.
Submission guide
Understand the complete workflow, review boundary, retries, and backlink requirement.