Skip to main content
SubmitForBacklinks

Agent submission guide

How to Submit a SaaS Listing With an AI Agent

Automate the repetitive parts of a product submission without automating away ownership, consent, or editorial review.

By
SubmitForBacklinks
Published
Updated

Choose the interface that fits the agent

REST, CLI, and MCP use the same account boundary and submission rules. Choose based on the client rather than creating separate product records. The recommended sequence is draft, retrieve, review, correct if needed, retrieve again, and finalize. A direct submission is accepted only when the caller supplies every reviewed listing field from an earlier scan.

CLI

Best for shell-based agents, CI jobs, and a founder auditing each command.

Open CLI documentation

REST

Best for a service that already manages HTTP, secret storage, and retries.

Open the API reference

MCP

Best for an MCP assistant that supports a manually configured Authorization bearer header.

Open MCP documentation

OpenAPI

Best for generating client types or validating requests against the canonical contract.

Download OpenAPI JSON

Six accountable steps

  1. 01

    Confirm authority and public access

    Use a live HTTPS product URL and proceed only if the account owner is authorized to represent the product.

  2. 02

    Scan without creating a listing

    Ask the agent to call the stateless public scanner and save its output. It does not reserve the domain or guarantee creation. Inspect proposed copy, category, tags, pricing, source URLs, confidence, and warnings.

  3. 03

    Verify the domain and create a draft

    Run terminal setup, publish the short-lived .well-known proof, and let the CLI store its credential automatically. Then pass the reviewed scan fields into an owner-scoped draft before entering editorial review.

  4. 04

    Retrieve and correct the saved state

    Retrieve the exact saved draft. If anything needs correction, replace its complete nine-field listing set, retrieve it again, and show that result to the owner.

  5. 05

    Explicitly submit and track it

    Finalize the reviewed draft, optionally choose an available launch week, confirm all four attestations, and track the returned submission ID.

  6. 06

    Issue and verify the free badge

    Install one exact markup theme on a public HTTPS page of the product domain, verify that target, and retrieve its follow-window and link-policy state.

Start with a non-writing scan

A scan prepares content but does not create a listing. This gives the owner a clear review point before authentication or submission. It does not reserve the domain or guarantee that a later create request will pass duplicate and eligibility checks. Saving the output also lets the draft command preserve the exact copy that was reviewed.

Inspect a public product site
./submitforbacklinks scan https://yourproduct.com --pretty > scan.json

What the agent must not decide silently

The agent must not claim authority over a product, accept legal terms, acknowledge the backlink badge requirement, or assert that generated copy was reviewed without an explicit owner decision. Paid placement does not guarantee approval, rankings, traffic, or domain-rating growth.

Run the documented workflow

The quickstart includes installation, authentication, scan, draft, saved-state review, correction, submission, status, and a REST-only alternative.

Open the terminal quickstart