Skip to main content
SubmitForBacklinks
Developer docs

AI Agent Submission API Documentation

Build a terminal, REST, or MCP workflow that scans a public product site and submits an owner-reviewed listing to SubmitForBacklinks.

Run the quickstartOpenAPI JSON

Start with the live contract

Capabilities is public and designed for runtime discovery. OpenAPI is the canonical field-level contract for generated clients and validation.

Discover capabilities
curl --fail-with-body https://submitforbacklinks.com/api/v1/agent/capabilities

Five-minute quickstart

Install the single-file CLI, scan a site, review the saved draft, correct it, and submit it.

Run the quickstart

REST API reference

Review endpoints, authentication, idempotency, attestations, and stable errors.

Read the reference

Submission lifecycle

The API separates discovery from accountable submission so an agent can inspect a site without silently accepting terms.

  1. 01

    Scan

    Prepare a stateless proposed draft. Scanning does not reserve a domain or guarantee that creation will succeed.

  2. 02

    Save and retrieve

    Create an owner-scoped draft from reviewed scan copy, then inspect the exact saved fields.

  3. 03

    Correct

    Replace all nine listing fields when the saved draft needs a change.

  4. 04

    Submit

    Finalize only after the owner reviews the saved state and confirms all four attestations.

  5. 05

    Verify

    Issue and verify the free-listing badge on the submitted product domain.

  6. 06

    Track

    Retrieve owner-scoped submission and badge status with the same bearer token.

Owner-scoped authentication

Scanning and capabilities are public. Normal CLI setup proves control of the product domain and stores the submission credential automatically.

Verify once, then stay in the terminal

Run setup with the product URL and contact email, publish the exact returned .well-known proof, and run setup --verify. No email code, copied key, or .env file is required.

  • If the agent controls deployment, it should add and deploy the proof file for the user.
  • The CLI stores the resulting credential outside the project with owner-only permissions.
  • Run claim only when the user wants browser-dashboard editing; Google sign-in needs no email code.
  • Repeat domain setup to recover a lost local credential.
  • Dashboard-created keys remain available for CI, teams, direct REST, and MCP.
  • Submission list and detail responses are restricted to the token owner.

Choose the client boundary

All clients use the same owner-scoped workflow and submission rules.

Terminal CLI

Use a single-file command-line client without adding a package to your product.

CLI commands

Remote MCP

Expose the same workflow to an MCP client that supports a manually configured Authorization bearer header.

MCP tools

Agent workflow guide

See where owner review, confirmation, retries, and editorial moderation fit.

Read the workflow

Backlink verification

Understand the badge requirement for dofollow treatment on a free listing.

Read the badge guide

Media remains optional and browser-managed

Agent API v1, the CLI, and MCP cover listing fields and workflow state, not file uploads.

Owners may add or manage an optional logo and up to three screenshots from the signed-in browser dashboard.