The tools API

Every action of every tool in Reliafy’s Claude connector (MCP) is also a REST call, with the same arguments, the same checks and the same result. The REST calls are built from the connector’s tools, so a new tool or action is here as soon as it ships.

POST/api/v1/{tool}/{action}

A tool with actions (or, for get and list, kinds). The body is a JSON object of the action’s arguments; the action is in the path, not the body.

POST/api/v1/{tool}

A tool without actions, such as guide or upgrade_link.

GET/api/v1/tools

The tools and actions your token may call, each with its path and its required and optional arguments.

GET/api/v1/openapi.json

An OpenAPI 3.1 spec of every tool action with its full argument schema: the complete, always-current reference. Without a token it covers the core tools; with one, everything that account may call. Generate a client from it, or import it into Postman or similar.

Open the OpenAPI spec · Worked examples

Long-running calculations

A long simulation or search answers at once with a job_id and a status of queued or running. Poll it until status is done (with the result) or failed. The Python client (wait=True) and the command line wait for you.

curl -X POST https://reliafy.com/api/v1/get/job \
  -H "Authorization: Bearer $RELIAFY_TOKEN" -H "Content-Type: application/json" \
  -d '{"id": "JOB_ID"}'

Every tool and action

Loading the tool list…

The full list of tools, actions and arguments is in the OpenAPI spec, and GET /api/v1/tools (or reliafy tools) lists what your token may call.