For Agents
Programmatically create new rows, get spreadsheet content. Covers 12 operations.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SheetDB API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsheetdb.io%2Fsheetdb" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsheetdb.io%2Fsheetdb" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with SheetDB API.
Create new rows
Get spreadsheet content
Search rows (AND)
Query and filter SheetDB API records by parameters
GET STARTED
Use for: I need to new rows, I want to spreadsheet content, Search for column headers, Find all spreadsheet name
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Turn Google Spreadsheets into JSON REST APIs with full CRUD operations (formerly Sheetsu, now SheetDB). The API exposes 12 endpoints.
Monitor SheetDB API operational status and events
Patterns agents use SheetDB API for, with concrete tasks.
★ Developer Tools Operations
Use the SheetDB API to perform developer tools operations programmatically. The API provides 12 endpoints covering core functionality including create new rows, get spreadsheet content, get column headers.
Call POST /{api_id} to create new rows
Automated all Management
Automate all operations by combining multiple SheetDB API endpoints. Agents can get spreadsheet content and then get column headers in a single workflow.
Call GET /{api_id} to get spreadsheet content, then verify the result
AI Agent Integration via Jentic
AI agents discover and call SheetDB API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.
Search Jentic for 'create new rows', load the operation schema, and execute with Jentic-managed credentials
12 endpoints — turn google spreadsheets into json rest apis with full crud operations (formerly sheetsu, now sheetdb).
METHOD
PATH
DESCRIPTION
/{api_id}
Create new rows
/{api_id}
Get spreadsheet content
/{api_id}/keys
Get column headers
/{api_id}/name
Get spreadsheet name
/{api_id}/count
Get row count
/{api_id}/search
Search rows (AND)
/{api_id}/search_or
Search rows (OR)
/{api_id}/{column_name}/{value}
Update rows
/{api_id}
Create new rows
/{api_id}
Get spreadsheet content
/{api_id}/keys
Get column headers
/{api_id}/name
Get spreadsheet name
/{api_id}/count
Get row count
/{api_id}/search
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the SheetDB API by hand means building each call around your sheet's api_id on the sheetdb.io host and constructing the read, search, and update paths yourself. Through Jentic you install once, import the SheetDB API from the API Directory, and your agent calls it.
Permission scoping
SheetDB puts the sheet's api_id in the URL path (/{api_id}/...), so a rule can pin your agent to one sheet. You choose the operations it may call, so writes like patching a row are not included unless you add them.
Credential isolation
SheetDB is configured without a stored secret for these operations, and your Jentic One instance still runs the call in its own execution context so no connection details enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create new rows' or 'search a sheet', and Jentic returns the matching SheetDB operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
Specific to using SheetDB API through Jentic.
What authentication does the SheetDB API use?
The SheetDB API uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I create new rows with the SheetDB API?
Yes. Use the POST /{api_id} endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the SheetDB API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I create new rows through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create new rows'. Jentic returns the matching SheetDB API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the SheetDB API have?
The SheetDB API exposes 12 endpoints covering all, batch_update, count operations.
Can I limit what my agent is allowed to do with the SheetDB API?
Yes. Because you run Jentic One yourself, your own rules decide which SheetDB operations and credentials the agent may use. Since SheetDB puts the sheet's api_id in the URL path, a rule can pin the agent to a single sheet, and you choose which operations it can call, so read calls like getting spreadsheet content, column headers, row counts, or searching rows can be allowed while writes such as creating rows (POST) or updating rows (PATCH) stay off unless you add them.
Search rows (AND)
/{api_id}/search_or
Search rows (OR)
/{api_id}/{column_name}/{value}
Update rows