Skip to main content
POST
/
api
/
tools
/
{tool_name}
Execute a Tool
curl --request POST \
  --url https://pro-api.nikiwa.com/api/tools/{tool_name} \
  --header 'Authorization: <authorization>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "tool inputs": {}
}
'
Execution runs a single tool and returns its structured data. Pass the tool’s inputs as a JSON body.
​
Authorization
string
required
Your developer key as a Bearer token.
​
tool_name
string
required
The tool to run, for example get_wallet_portfolio_breakdown. It must be a public tool (see the catalog). Unknown or non-public names return 404.
​
tool inputs
object
The tool’s inputs. Most tools take an entity (a wallet as wallet_address or address, a token as token_address, a contract as contract_address, a tx_hash, or an ens_name) and often a network. The exact parameter names vary per tool — read each tool’s schema from discovery or its page under Endpoints.

​
Example: wallet portfolio

curl -X POST https://pro-api.nikiwa.com/api/tools/get_wallet_portfolio_breakdown \
  -H "Authorization: Bearer nkw_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
        "wallet_address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
        "network": "ethereum"
      }'

​
Providing exact entities

Tools are deterministic and expect precise inputs: an exact wallet, token, or contract address, a transaction hash, and a network. If you only have a symbol or a name, resolve it first. Call resolve_token_symbol to turn a symbol into an address, or resolve_ens to turn an ENS name into an address.

​
Result

On success you receive the tool’s data object. Invalid arguments return 422 Unprocessable Entity, so check the tool’s input schema from discovery if you hit one. When a tool has nothing to return, or hits a problem, you receive a status marker instead. See Errors & status.