canonical: https://jentic.com/apis/sheetlabs.com/vs-api

# Sheetlabs vs API

Introduction This API returns data regarding almost all nouns in vedic literature. The results are JSON objects that contain the word transliterated to the Roman script, the word in the Nagari script, the meaning of the word, and the category the word belongs to. Proper nouns are not included (yet). The API uses the Swagger 2.0 specification. Authentication This is an open API. Try it out This san. The API exposes 1 endpoints.

## For AI agents

Programmatically fetch all meanings that contain a specific english string. Covers 1 operations.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- Fetch all meanings that contain a specific English string
- Manage identity auth data programmatically
- Integrate vs API into automated workflows
- Query and filter vs API records by parameters
- Monitor vs API operational status and events

## Use cases

### Identity and Authentication Operations

Use the vs API to perform identity auth operations programmatically. The API provides 1 endpoints covering core functionality including fetch all meanings that contain a specific english string.

Example prompt: Call GET /resources to fetch all meanings that contain a specific english string

### Data Retrieval and Monitoring

Query vs API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary vs API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call vs 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.

Example prompt: Search Jentic for 'fetch all meanings that contain a specific english string', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/resources` | Fetch all meanings that contain a specific English string |

## Key resources

- **resources** — Operations related to resources

## Why Jentic

- **Setup:** Wiring the vs API by hand means pointing at its api-vs.herokuapp.com host and shaping the resources query for meaning lookups yourself. Through Jentic you install once, import the vs API from the API Directory, and your agent calls it.
- **Permission scoping:** The vs API exposes a single read-only resources endpoint, so scope the agent to that one operation and it can fetch meaning data without any write access.
- **Credential handling:** The vs API is configured without a stored secret, 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.
- **Discovery method:** Agents search Jentic by intent such as 'fetch all meanings that contain a specific English string', and Jentic returns the matching vs operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the vs API use?

The vs 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 fetch all meanings that contain a specific english string with the vs API?

Yes. Use the GET /resources endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the vs 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 fetch all meanings that contain a specific english string through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'fetch all meanings that contain a specific english string'. Jentic returns the matching vs API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the vs API have?

The vs API exposes 1 endpoints covering resources operations.

### Can I limit what my agent is allowed to do with the Vedic Society API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. This API exposes a single read-only endpoint, GET /resources, which fetches Vedic word meanings, so you can scope the agent to just that one call and it gets no write or other access. That keeps the agent limited to reading meaning data and nothing more.