Skip to main content

Public catalog developer guide

Read Sorsivo’s public catalog from the interface you prefer.

Use HTTP, OpenAPI, JSON, Markdown, the standalone Node.js CLI or MCP. These surfaces expose public product information only; they do not provide access to enterprise workspaces, RFQs or customer data.

Fetch the catalog with no account or API key.

Successful API and CLI requests return JSON. Public catalog reads do not require authentication.

HTTP

curl -sS https://sorsivo.com/api/public/v1/catalog

curl -sS "https://sorsivo.com/api/public/v1/products?q=rfq&limit=10"

Standalone CLI

curl -sS https://sorsivo.com/sorsivo-cli.mjs -o sorsivo-cli.mjs
node sorsivo-cli.mjs catalog
node sorsivo-cli.mjs search "rfq" --limit 10

Choose a browsable or machine-readable format.

The same public product information is available as a documented API, whole-catalog files and MCP tools. Use the narrowest interface that fits your workflow.

Read catalog resources and run bounded public checks.

Product search accepts q, category, tag, and limit from 1 to 50. POST checks have separate request bodies and rate limits.

MethodPathPurpose
GET/api/public/v1/statusCheck public API availability.
GET/api/public/v1/catalogRead the complete public catalog envelope.
GET/api/public/v1/productsSearch products with q, limit, category and tag parameters.
GET/api/public/v1/products/{slug}Read one public product record.
GET/api/public/v1/directoriesList public catalog directories.
GET/api/public/v1/taxonomiesList public categories and tags.
GET/api/public/v1/leaderboardRead the public leaderboard representation.
POST/api/public/v1/seo-checkInspect a public HTTPS URL or supplied HTML.
POST/api/public/v1/drRequest provider-backed Domain Rating for up to 10 domains.

Run the clients with Node.js.

Both files are standalone ES modules. The default origin is https://sorsivo.com. Override it with global --origin or the SORSIVO_PUBLIC_ORIGIN environment variable.

# Download
curl -sS https://sorsivo.com/sorsivo-cli.mjs -o sorsivo-cli.mjs
curl -sS https://sorsivo.com/sorsivo-mcp.mjs -o sorsivo-mcp.mjs

# Catalog commands
node sorsivo-cli.mjs catalog
node sorsivo-cli.mjs product <slug>
node sorsivo-cli.mjs directories

# Public checks
node sorsivo-cli.mjs seo https://example.com
node sorsivo-cli.mjs seo --html-file page.html --url https://example.com/page
node sorsivo-cli.mjs dr example.com example.org

# stdio MCP bridge
node sorsivo-mcp.mjs

Each successful CLI command prints one JSON document to stdout. Errors print JSON to stderr and exit with a nonzero status.

Point your MCP client at the downloaded stdio bridge.

Use Node.js as the command and replace the example argument with the downloaded file's absolute path.

{
  "mcpServers": {
    "sorsivo-public": {
      "command": "node",
      "args": ["/absolute/path/to/sorsivo-mcp.mjs"]
    }
  }
}

Public product facts stay separate from enterprise data.

The public catalog does not expose authenticated Sorsivo workspaces, customer RFQs, supplier quotes, uploaded files, mailboxes or quotation decisions. Those product surfaces retain their own authentication and authorization boundaries.

  • No API key is needed for public catalog reads.
  • Rate limits may apply to public checks.
  • DR values remain tied to provider availability.
  • Errors remain explicit in HTTP and CLI output.