Guide
Tools API v1 documentation
Use API v1 to list tools, fetch tool/page metadata, and integrate salamyx.com with automation systems or LLM orchestration.
Guide
Use API v1 to list tools, fetch tool/page metadata, and integrate salamyx.com with automation systems or LLM orchestration.
Use the production host and call endpoints under /api/v1.
https://salamyx.com/api/v1
GET /api/v1/healthAPI health check and version metadata.
GET /api/v1/toolsList tool catalog records. Supports query params: category, runtime, risk, q.
GET /api/v1/tools?id={toolId}Get one tool record by id via query string.
GET /api/v1/pages/{pageId}Get one canonical page payload by id.
All endpoints return JSON with a top-level status field. Errors return failed with a message and proper HTTP status code.
{
"status": "ok",
"count": 2,
"tools": [
{
"id": "sha256",
"route": "/crypto/sha256/",
"category": "crypto",
"runtime": "browser",
"riskLevel": "low"
}
]
} /api/v1/tools as the source catalog for automation and MCP wrappers./api/v1/pages/{pageId} when you need full metadata including FAQ, limitations, and privacy notes.API v1 serves metadata and catalog data. Browser-only tools continue to process user input locally on their dedicated pages.
No. The first version is metadata-first and exposes tool/page catalog data for integrations.
Use GET /api/v1/tools and apply filters by category, runtime, risk, or search query.
Use GET /api/v1/tools?id={toolId} with the tool id from the catalog response.
Yes. API v1 is designed for automation, MCP wrappers, and workflow systems.
Yes, but only for tools that need server-side processing, secrets, queues, or anti-abuse controls.