Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the rv 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%2Fsheetlabs.com%2Frv-api" | 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%2Frv-api" | 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 rv API.
Fetch all verses sung for a specific category of god, person, or object
Manage identity auth data programmatically
Integrate rv API into automated workflows
Query and filter rv API records by parameters
Monitor rv API operational status and events
GET STARTED
Patterns agents use rv API for, with concrete tasks.
★ Identity and Authentication Operations
Use the rv API to perform identity auth operations programmatically. The API provides 1 endpoints covering core functionality including fetch all verses sung for a specific category of god, person, or object.
Call GET /resources to fetch all verses sung for a specific category of god, person, or object
Data Retrieval and Monitoring
Query rv 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.
Poll the primary rv API endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call rv 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 'fetch all verses sung for a specific category of god, person, or object', load the operation schema, and execute with Jentic-managed credentials
1 endpoints — introduction this api returns information about all of the verses in rig veda.
METHOD
PATH
DESCRIPTION
/resources
Fetch all verses sung for a specific category of god, person, or object
/resources
Fetch all verses sung for a specific category of god, person, or object
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the rv API by hand means pointing at its api-rv.herokuapp.com host and shaping the resources query for verse lookups yourself. Through Jentic you install once, import the rv API from the API Directory, and your agent calls it.
Permission scoping
The rv API exposes a single read-only resources endpoint, so scope the agent to that one operation and it can fetch verse data without any write access.
Credential isolation
The rv 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.
Intent-based discovery
Agents search Jentic by intent such as 'fetch all verses sung for a specific god, person, or object', and Jentic returns the matching rv 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.
Specific to using rv API through Jentic.
What authentication does the rv API use?
The rv 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 verses sung for a specific category of god, person, or object with the rv 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 rv 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 verses sung for a specific category of god, person, or object through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'fetch all verses sung for a specific category of god, person, or object'. Jentic returns the matching rv API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the rv API have?
The rv API exposes 1 endpoints covering resources operations.
Can I limit what my agent is allowed to do with the rv API?
Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials your agent may use. The rv API exposes only a single read-only GET /resources endpoint, so you can scope the agent to just that one operation and it fetches Rig Veda verse data without any write access. Nothing outside that verse-lookup call is reachable unless you allow it.
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically fetch all verses sung for a specific category of god, person, or object. Covers 1 operations.
Use for: I need to fetch all verses sung for a specific category of god, person, or object, Find available identity auth operations, Get the current status of rv API resources, List all records from rv API
Not supported: Does not handle payments, communications, or crm - use for identity and authentication only.
Introduction This API returns information about all of the verses in Rig Veda. The results are JSON objects that contain the name of the god, poet, and meter of the verses in Rig Veda, the category of the god and the poet, and the _mandal_ and _sukta_ number. The API uses the Swagger 2.0 specification. Authentication This is an open API. Try it out This sandbox can be used to get data for only one. The API exposes 1 endpoints.