NagentArtefacts
Dev & Technology
Enterprise and White Glove
Company
Turso connects to a Nagent workspace with an API key. Once it is connected, agents can call 3 Turso actions: "Closest Region", "Listen To Changes" and "Validate API Token". Nothing is enabled on connect: each action is allowed one at a time, and an action with side effects runs or waits for a person according to the agent's level.
Every operation an agent can call against Turso, with input parameters and output schema.
TURSO_CLOSEST_REGIONTool to get the closest Turso region based on client location. Use when you need to minimize latency by selecting the nearest deployment region.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TURSO_LISTEN_TO_CHANGESListen to committed table changes in a Turso database via the /beta/listen endpoint. This tool streams real-time insert/update/delete events for a specific table. IMPORTANT: Requires a database-specific URL (e.g., 'https://mydb-myorg.turso.io'), NOT the platform API URL (api.turso.tech). Note: The /beta/listen endpoint is NOT available on AWS regions for Free, Developer, and Scaler plans. When unavailable, the action falls back to a /v2/pipeline health check.
Input parameters
Name of the table to listen for changes on (e.g., 'users', 'orders')
Type of change event to listen for: 'insert' (new rows), 'update' (modified rows), or 'delete' (removed rows)
The database-specific URL to connect to (e.g., 'https://mydb-myorg.turso.io'). This is NOT the platform API URL (api.turso.tech). Get this from the 'hostname' field when listing databases via the Platform API.
Optional database-specific JWT token for authentication. If not provided, a token will be automatically generated using the Platform API. You can create one via POST /v1/organizations/{org}/databases/{db}/auth/tokens
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TURSO_VALIDATE_API_TOKENValidates a Turso API token and retrieves its expiration time. Use this action to verify that an API token is valid and check when it expires. Returns the token's expiration timestamp, or -1 if the token has no expiration.
Input parameters
Validation mode: 'platform' (recommended) validates via the Platform API at https://api.turso.tech/v1/auth/validate and returns token expiration. 'pipeline' validates by executing a health-check SQL query against a database URL (requires a database-specific base_url like https://<db>-<user>.turso.io). 'auto' tries platform first, falling back to pipeline on failure.
SQL statement to execute for health validation when mode is 'pipeline' or during 'auto' fallback. Only used when validating against a database instance.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
Agents can call 3 Turso actions on Nagent: "Closest Region", "Listen To Changes" and "Validate API Token". Closest Region: Get the closest Turso region based on client location. Each action is listed on this page with its input parameters and its output.
Turso connects with an API key, under your workspace's own connection. Nothing is enabled on connect: each action is allowed one at a time and can be scoped to the agents that need it.
It returns data, error and successful.