Turso

turso-http-v2restprimary

78% coverage

Offload Valuejudged · weight 15 · Oct 5, 2026

Turso's HTTP API is essentially a remote SQLite engine: execute SQL statements, bind parameters, open interactive transactions, dump the schema, and poll migration jobs. The SQL engine does provide genuine computation offload (filtering, joins, aggregation, transactional durability, and the dump reveals a diskann vector index capability), which is more than a dumb store-what-you-send API. But the documented surface here is overwhelmingly persistence and connection management: there is no proprietary data, no external side effect beyond writing rows, and no domain logic the agent doesn't have to author itself. The agent still carries all the cognitive load of composing the SQL and interpreting results.

• https://docs.turso.tech/sdk/http/reference

  The endpoint accepts a series of operations to perform against a database connection. The supported operation types are: execute : execute a statement on the connection. close : close the connection.

• https://docs.turso.tech/sdk/http/reference

  The endpoint accepts a series of operations to perform against a database connection. The supported operation types are: execute : execute a statement on the connection. close : close the connection.

• https://docs.turso.tech/sdk/http/reference

  The endpoint accepts a series of operations to perform against a database connection. The supported operation types are: execute : execute a statement on the connection. close : close the connection.

Interaction Costmeasured · weight 15 · Oct 5, 2026

Median over 2 successful run(s): 9306.5 tokens, 3 calls. Ratio to the best in "backend-database" (4 surfaces measured, v0.2 scale). Cold, without documentation: 1/1 succeeded.

Error Recoverabilityprobed · weight 15 · Oct 5, 2026

unknown_endpoint → HTTP 404, clarity 55/100 (field named: yes, allowed values: no, RFC 9457: no) · wrong_type → HTTP 400, clarity 50/100 (field named: no, allowed values: yes, RFC 9457: no) · hallucinated_enum → HTTP 400, clarity 75/100 (field named: yes, allowed values: yes, RFC 9457: no) · unknown_field → HTTP 200, clarity 25/100 (field named: no, allowed values: no, RFC 9457: no)

• https://agentscore-bench-nicolascharr.aws-eu-west-1.turso.io/v2/pipeline

  HTTP 401: {"error":"Unauthorized: `unauthorized access attempt on database: empty JWT token`"}

• https://agentscore-bench-nicolascharr.aws-eu-west-1.turso.io/v2/nonexistent_resource_xyz

  HTTP 404: {"error":"route not found: [\"v2\", \"nonexistent_resource_xyz\"]"}

• https://agentscore-bench-nicolascharr.aws-eu-west-1.turso.io/v2/pipeline

  HTTP 400: {"error":"JSON parse error: invalid type: integer `42`, expected a string at line 1 column 50"}

• https://agentscore-bench-nicolascharr.aws-eu-west-1.turso.io/v2/pipeline

  HTTP 400: {"error":"JSON parse error: unknown variant `run`, expected one of `close`, `execute`, `batch`, `sequence`, `describe`, `store_sql`, `close_sql`, `get_autocommit` at line 1 column 26"}

Doc Legibilitymeasured · weight 12 · Oct 5, 2026

text/markup ratio 1.8% (weight 30) · rendering without JavaScript undetermined (excluded from the calculation) (weight 25) · machine-readable spec: none found (weight 25) · llms.txt: https://docs.turso.tech/llms.txt (weight 10) · 7 runnable example(s) (weight 10). Weighted average over 75 points of available sub-criteria.

• https://docs.turso.tech/sdk/http/reference
• https://docs.turso.tech/llms.txt

Auth Frictionmeasured · weight 10 · Oct 5, 2026

Authorization: Bearer <key>, verified by a successful call. One header, no ceremony.

• https://agentscore-bench-nicolascharr.aws-eu-west-1.turso.io/v2/pipeline

  HTTP 400: {"error":"JSON parse error: unknown variant `run`, expected one of `close`, `execute`, `batch`, `sequence`, `describe`, `store_sql`, `close_sql`, `get_autocommit` at line 1 column 26"}

• https://agentscore-bench-nicolascharr.aws-eu-west-1.turso.io/v2/pipeline

  HTTP 200: {"baton":null,"base_url":null,"results":[{"type":"ok","response":{"type":"execute","result":{"cols":[{"name":"1","decltype":null}],"rows":[[{"type":"integer","value":"1"}]],"affected_row_count":0,"las

• https://agentscore-bench-nicolascharr.aws-eu-west-1.turso.io/v2/pipeline

  HTTP 401: {"error":"Unauthorized: `unauthorized access attempt on database: empty JWT token`"}

• https://agentscore-bench-nicolascharr.aws-eu-west-1.turso.io/v2/nonexistent_resource_xyz

  HTTP 404: {"error":"route not found: [\"v2\", \"nonexistent_resource_xyz\"]"}

Safety & Reversibilityprobed · weight 10

If I retry after a timeout, do I charge the customer twice?

Payload Efficiencyprobed · weight 8

Can I ask for only the fields I need, or do I have to swallow 200 attributes to extract one?

Task Atomicitymeasured · weight 6 · Oct 5, 2026

Median over 2 successful run(s): 9306.5 tokens, 3 calls. Ratio to the best in "backend-database" (4 surfaces measured, v0.2 scale). Cold, without documentation: 1/1 succeeded.

Prior Knowledge Coveragemeasured · weight 5 · Oct 5, 2026

Median over 2 successful run(s): 9306.5 tokens, 3 calls. Ratio to the best in "backend-database" (4 surfaces measured, v0.2 scale). Cold, without documentation: 1/1 succeeded.

Async Compatibilityprobed · weight 2

If the operation is asynchronous, can I get the result without hosting a web server?

Tool-Native (MCP)binary · weight 2

Does the vendor publish an official, maintained MCP server?