canonical: https://jentic.com/apis/singlestore.com/singlestore

# SingleStore Data API

SingleStore cloud database Data API for executing SQL queries, managing databases, and accessing query results via REST. The API exposes 5 endpoints secured with apiKey authentication.

## For AI agents

Programmatically execute query, execute query (tuples). Covers 5 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- Execute query
- List workspaces
- Get workspace
- Query and filter SingleStore Data API records by parameters
- Monitor SingleStore Data API operational status and events

## Use cases

### E-Commerce Operations

Use the SingleStore Data API to perform e commerce operations programmatically. The API provides 5 endpoints covering core functionality including execute query, execute query (tuples), list workspaces.

Example prompt: Call POST `/v2/query/rows` to execute query

### Automated Databases Management

Automate databases operations by combining multiple SingleStore Data API endpoints. Agents can execute query (tuples) and then list workspaces in a single workflow.

Example prompt: Call POST `/v2/query/tuples` to execute query (tuples), then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SingleStore Data 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 apiKey tokens manually.

Example prompt: Search Jentic for 'execute query', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v2/query/rows` | Execute query |
| POST | `/v2/query/tuples` | Execute query (tuples) |
| GET | `/v1/organizations/{orgId}/workspaces` | List workspaces |
| GET | `/v1/organizations/{orgId}/workspaces/{workspaceId}` | Get workspace |
| GET | `/v1/organizations/{orgId}/workspaces/{workspaceId}/databases` | List databases |

## Key resources

- **Databases** — Operations related to Databases
- **Queries** — Operations related to Queries
- **Workspaces** — Operations related to Workspaces

## Why Jentic

- **Setup:** Wiring the SingleStore Data API by hand means setting up its key in the Authorization header and carrying it across every query and workspace call yourself. Through Jentic you install once, import SingleStore from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** SingleStore puts the organization and workspace ids in the URL path (`/v1/organizations/{orgId}/workspaces/{workspaceId}`), so a rule can pin your agent to one workspace: it can read that workspace and its databases and nothing else. You choose the operations it may call, so a write query against rows is not included unless you add it.
- **Credential handling:** Your SingleStore API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'run a query' or 'list workspace databases', and Jentic returns the matching SingleStore operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### What authentication does the SingleStore Data API use?

The SingleStore Data API uses an API key passed in the `Authorization` header. 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 execute query with the SingleStore Data API?

Yes. Use the POST `/v2/query/rows` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the SingleStore Data 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 execute query through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'execute query'. Jentic returns the matching SingleStore Data API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the SingleStore Data API have?

The SingleStore Data API exposes 5 endpoints covering databases, queries, workspaces operations.

### Can I limit what my agent is allowed to do with the SingleStore Data API?

Yes. Because Jentic One is self-hosted and you set its rules, you decide which SingleStore operations your agent may call and which credentials it may use. Since SingleStore puts the organization and workspace ids in the URL path, such as `/v1/organizations/{orgId}/workspaces/{workspaceId}`, you can pin the agent to a single workspace so it only reads that workspace and its databases. You also control the operation list, so a write query through POST `/v2/query/rows` is excluded unless you explicitly add it.