Skip to main content
Preview. The Tools API is not yet generally available. Access requires a key with the api:call scope, which is provisioned on request rather than self-serve. To build against Nikiwa today, use the MCP server, which works with a key you create in the app. Contact the team to request Tools API access.
The Nikiwa Tools API exposes a curated set of analysis tools as a REST API. Each tool takes exact inputs and returns a structured data object, the same data the app renders as modules, handed to you raw.
The Tools API is deterministic and data-only. It does not route intent, interpret, or synthesize; that reasoning is your application’s job. For a reasoning layer over the same tools, connect an assistant via the MCP server.

​
Base URL

https://pro-api.nikiwa.com

​
The two surfaces

The API separates discovery (cheap, read-only) from execution (heavy).
MethodPathPurposeAuth
GET/api/toolsList available tools and their input specsAPI key
GET/api/tools/openapi.jsonOpenAPI spec for the public toolsNone
POST/api/tools/{tool_name}Execute a tool and return its resultAPI key
Only a curated allowlist of tools is public. A tool that is not on the allowlist returns 404; it is neither listed by discovery nor callable. The full tool set is available through the MCP server.

​
Typical flow

1

Get a key

Request a key with the api:call scope. See Authentication.
2

Discover

Call GET /api/tools to see which tools exist and what inputs each expects.
3

Execute

Call POST /api/tools/{tool_name} with the tool’s inputs as a JSON body.

​
Response shape

Every tool returns a JSON object. On success that is the tool’s data. When a tool has nothing to return, or hits a problem, it returns a status marker instead: 
{ "status": "no_data" }
See Errors & status for the full contract.

Authenticate

How to pass your API key.