2 APIs across 1 product group. All share one credential.
| I want to... | Use | Why |
|---|---|---|
| Retrieve Rig Veda verses and their god, poet, meter, mandal, and sukta | rv API | The Rig Veda API returns verse records filtered by the category of god, person, or object. |
| Look up the meaning and script of a Vedic Sanskrit word | vs API | The Vedic Society API searches nouns by English string and returns transliteration, Nagari, meaning, and category. |
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SheetLabs APIs, 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%2Fsheetlabs.com" | 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%2Fsheetlabs.com" | 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.
Once connected, ask your agent something like: “fetch Rig Veda verses and Vedic Sanskrit word meanings”.
What agents get from Jentic-routed access to this vendor.
Setup
Wiring these APIs by hand means pointing at their separate Heroku hosts and shaping the resources query for verse and word lookups yourself. With Jentic you install Jentic One once, and your agent finds and adds either API from the Jentic directory to your workspace.
Permission scoping
Each API exposes a single read-only endpoint, so your own rules in Jentic One can scope an agent to just the verse lookup, just the word lookup, or both, with no write access anywhere.
Credential isolation
Both APIs are open and store no secret, and your own Jentic One instance still runs each call in its own execution context so no connection details enter the agent's prompt, logs, or context.
Specific to using SheetLabs APIs through Jentic.
What kind of data do the SheetLabs APIs provide?
They provide structured reference data over Vedic Sanskrit literature. The Rig Veda API returns verse records with the god, poet, meter, mandal, and sukta of each verse, and the Vedic Society API returns word records with transliteration, Nagari spelling, meaning, and lexical category.
Do the SheetLabs APIs require authentication?
No. Both APIs are open and require no API key or token. When accessed through Jentic, the connection is still run inside your own Jentic One instance so no connection details enter the agent context.
Can I use both APIs together?
Yes. Verse records from the Rig Veda API can be joined with lexical entries from the Vedic Society API to annotate verses with word meanings or to build a combined Vedic reference dataset.
Are these read-only APIs?
Yes. Each API exposes a single GET endpoint that returns JSON, and there are no write, update, or delete operations across the vendor.
BOOK A DEMO
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.
For Agents
An agent can look up Rig Veda verses filtered by the category of god, person, or object and retrieve each verse's god, poet, meter, mandal, and sukta, and can search Vedic-literature nouns by English meaning to get their transliteration, Nagari script, definition, and lexical category. Both lookups return structured JSON over open GET endpoints.
SheetLabs exposes structured, machine-readable APIs over Vedic Sanskrit source texts, pairing Rig Veda verse metadata with a searchable Vedic lexicon. It is aimed at agents and applications that need programmatic scholarly reference data rather than a general dictionary or translation service.
Use for: Reading Rig Veda verse metadata and searching Vedic-literature word meanings over open, structured JSON endpoints
Not supported: write operations, proper noun coverage, full text translation, authentication services, modern language dictionaries
Credentials: Both APIs are open and require no authentication, so a single (empty) credential setup covers every endpoint across the vendor.
All 2 SheetLabs OpenAPI specs are third-party and indexed by Jentic, kept validated and agent-ready.
SheetLabs hosts two open, read-only reference APIs over Vedic Sanskrit literature. The Rig Veda API returns verse records with the god, poet, and meter of each verse plus its mandal and sukta numbers, and lets callers fetch all verses sung for a given category of god, person, or object. The Vedic Society API returns word records with the Roman transliteration, the Nagari spelling, the meaning, and the lexical category of nearly every noun in Vedic literature, and lets callers fetch all meanings that contain a given English string. Both APIs return structured JSON and require no authentication.
Each workflow spans multiple SheetLabs APIs. Jentic routes each operation to the right API automatically.
Annotate Rig Veda verses with word meanings
Fetch verses for a category of god or object from the Rig Veda API, then resolve the Sanskrit terms in those verses against the Vedic Society lexicon to attach transliteration, Nagari script, and meaning to each verse.
Call the Rig Veda API for verses in a given category, extract candidate terms, and query the Vedic Society API for each term's meaning and script.
rv API + vs API
Build a Vedic reference dataset
Combine verse records from the Rig Veda API with lexical entries from the Vedic Society API to assemble a single structured dataset of verses, poets, meters, and word definitions for search or study tools.
Pull all verse records and all matching lexical entries, join them by term, and export a combined JSON dataset.
rv API + vs API
Intent-based discovery
Agents search the Jentic directory by intent, such as fetching Rig Veda verses or Vedic word meanings, and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing reference docs.
Does the Vedic Society API include proper nouns?
Not currently. It covers nearly all common nouns in Vedic literature with their meanings and categories, but proper nouns are not yet included.
In what format are results returned?
Both APIs return structured JSON objects that agents can parse and act on directly, without scraping or format conversion.
All 3 are in the Jentic catalogue with the same one-credential, intent-search pattern.