Moderation state of a listing — how the submitter polls for approval, with no credential.

Every submission is born pending. A bounded automatic review approves clear, low-risk MCP listings; uncertain cases stay private for a person to review. This is the receipt you poll after POST /api/listings (its response carries this URL as status_api). Only the decision comes back, never the unreviewed content: the id (lst_…, unguessable) is all it takes, and the page itself keeps its rule — owner only until it is public. Answers are cached for 60 s per point of presence: poll every few minutes, not every second. Returns: { id, status, public, message, reason?, api, status_api }

get/api/listings/{id}/status

Request

  • Base URL: https://agentalog.com
  • URL: https://agentalog.com/api/listings/{id}/status
  • Auth: none required

Path parameters

idstring required

Listing ID, from the id of the POST /api/listings response.

Response

{ id, status, public, message, reason?, api, status_api }

idstring required

Listing ID.

status'pending' | 'live' | 'low' | 'hidden' | 'blocked' required

Moderation state. pending is waiting; live and low are approved; hidden and blocked are not published.

publicboolean required

true when the listing is reachable in the catalog (live or low).

messagestring required

What the state means and what to do next.

reasonstring

Why it was hidden or blocked, when the moderator left a reason. Absent otherwise.

apistring required

The listing's page (GET /api/listings/:id): the owner reads it with the token that created it; everybody else once it is public.

status_apistring required

This URL, to poll again.

Changes

No recorded changes to this operation across all 1 revision of this API.