Skip to main content
POST
/
v1
/
tools
/
{slug}
/
execute
curl -X POST https://tools.runtools.ai/v1/tools/github/execute \
  -H "X-API-Key: $RUNTOOLS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "action": "list_repos",
    "params": {
      "owner": "runtools-ai"
    }
  }'

{
  "data": {
    "success": true,
    "result": {
      "repositories": []
    },
    "durationMs": 418
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.runtools.ai/llms.txt

Use this file to discover all available pages before exploring further.

Tool execution endpoints use: 
https://tools.runtools.ai/v1

​
Path Parameters

​
slug
string
required
Tool slug.

​
Request Body

​
action
string
required
Tool action name.
​
params
object
Action parameters.
​
credentials
object
Optional per-request credentials. Prefer stored secrets or OAuth connections for production.
​
credentialOverrides
object
Map tool credential field names to secret names so values stay server-side.

​
Response

​
success
boolean
Whether execution succeeded.
​
result
object
Tool-specific result when successful.
​
error
object
Tool-specific error when unsuccessful.
​
durationMs
number
Server-side execution duration.
curl -X POST https://tools.runtools.ai/v1/tools/github/execute \
  -H "X-API-Key: $RUNTOOLS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "action": "list_repos",
    "params": {
      "owner": "runtools-ai"
    }
  }'

{
  "data": {
    "success": true,
    "result": {
      "repositories": []
    },
    "durationMs": 418
  }
}

​
Credential Resolution

For tool execution, RunTools resolves credentials in this order:
  1. Per-request credentials
  2. credentialOverrides that point at stored secrets
  3. Stored credentials for the installed tool
  4. Matching organization or user secrets
  5. Connected OAuth account when the tool declares an OAuth provider