OpenWeb Comment API

SEO related to a comment

Operations 1

POST /comment/{spot_id}/{post_id} Create comment SEO markup #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/openweb:openweb-comment-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openweb-comment-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: SEO Service Comment API
  version: '1.0'
  description: SEO related to a comment
servers:
- url: https://seo.spot.im/v2
tags:
- name: Comment
  description: SEO related to a comment
paths:
  /comment/{spot_id}/{post_id}:
    parameters:
    - $ref: '#/components/parameters/spot_id'
    - $ref: '#/components/parameters/post_id'
    post:
      summary: Create comment SEO markup
      operationId: post-comment
      responses:
        '200':
          description: OK
      description: Returns the SEO markup used by Google and other search engines to index your comments
      tags:
      - Comment
      parameters:
      - $ref: '#/components/parameters/json'
components:
  parameters:
    spot_id:
      name: spot_id
      in: path
      required: true
      schema:
        type: string
      description: Unique OpenWeb identifier
    json:
      name: json
      in: query
      required: false
      schema:
        type: boolean
        example: true
      description: Formats response into a JSON structure
    post_id:
      name: post_id
      in: path
      required: true
      schema:
        type: string
      description: 'Unique article identifier that is specific to the article page


        The ideal post ID has the following characteristics:

        - Aligns with the URL slug (`an-article-title`) or article ID (`14325`)

        - Is **less than 50 characters**, ideally 15 characters

        - Uses a combination of letters, numbers, dashes (-), or hyphens (_)

        - Except for the regex `[^\w\s\-\:\.\$\~]`, does not include special characters

        '
x-provenance:
  method: searched
  source: https://developers.openweb.com/reference
  harvested: '2026-10-14'
  tool: harvest-readme-openapi.py
  note: Assembled verbatim from the OpenAPI definition ReadMe embeds in each operation page of the provider's developer portal; paths and components merged by API title, nothing authored.
  assembled_from:
  - https://developers.openweb.com/reference/post-article.md
  - https://developers.openweb.com/reference/post-comment.md
  - https://developers.openweb.com/reference/post-liveblog.md
  - https://developers.openweb.com/reference/post-reviews.md
  merge:
    pages: 4
    deduped: 8
    conflicts_kept_first: 0