Install Jentic One Beta

Connect the Strev (Revnue) API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Strev (Revnue) 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%2Frevnue.com%2Frevnue" | sh

Step 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%2Frevnue.com%2Frevnue" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with Strev (Revnue) API.

Create asset

List assets

Update asset

Delete asset

Attach file to asset

Use Cases

GET STARTED

Start building with Strev (Revnue) API

Explore with Jentic One

View OpenAPI Document

Automated Asset Owners Management

Automate asset owners operations by combining multiple Strev (Revnue) API endpoints. Agents can list assets and then update asset in a single workflow.

Call GET /asset to list assets, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Strev (Revnue) 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.

Search Jentic for 'create asset', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

51 endpoints — revnue api for managing assets, contracts, customers, suppliers, licenses, and related business entities.

METHOD

PATH

DESCRIPTION

POST

/asset

Create asset

GET

/asset

List assets

PUT

/asset/{id}

Update asset

DELETE

/asset/{id}

Delete asset

POST

/asset_attachment

Attach file to asset

POST

/contract_attachment

Attach file to contract

POST

/customer_attachment

Attach file to customer

POST

/supplier_attachment

Attach file to supplier

POST

/asset

Create asset

GET

/asset

List assets

PUT

/asset/{id}

Update asset

DELETE

/asset/{id}

Delete asset

POST

/asset_attachment

Attach file to asset

POST

/contract_attachment

Attach file to contract

POST

/customer_attachment

Attach file to customer

POST

/supplier_attachment

Attach file to supplier

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Strev (Revnue) API by hand means handling its Authorization header API key, sending that key on every call to developer.revnue.com, and managing retries yourself. Through Jentic you install once, import the Strev (Revnue) API from the API Directory, store the API key once, and your agent calls it.

Permission scoping

Strev puts the asset id in the URL path (/asset/{id}), so a rule can pin your agent to one asset: it can read that asset and nothing else. You choose the operations it may call, so destructive ones like deleting an asset or updating it are not included unless you add them.

Credential isolation

Your Strev (Revnue) 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.

Intent-based discovery

Agents search Jentic by intent such as 'create an asset' or 'attach a file to a contract', and Jentic returns the matching Strev (Revnue) API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Strev (Revnue) API through Jentic.

What authentication does the Strev (Revnue) API use?

The Strev (Revnue) 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 create asset with the Strev (Revnue) API?

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

What are the rate limits for the Strev (Revnue) 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 asset through Jentic?

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

How many endpoints does the Strev (Revnue) API have?

The Strev (Revnue) API exposes 51 endpoints covering asset owners, assets, attachments operations.

Can I limit what my agent is allowed to do with the Strev (Revnue) API?

Yes. Because you run Jentic One yourself, your own rules decide which Strev (Revnue) API operations and credentials your agent may use. Since Strev puts the asset id in the URL path (/asset/{id}), you can pin the agent to a single asset so it reads that asset and nothing else. You also choose the operations it may call, so destructive ones like deleting an asset (DELETE /asset/{id}) or updating it (PUT /asset/{id}) stay out of reach unless you add them.

Revnue Strev (Revnue) API

Name: Strev (Revnue) API
Brand: Strev (Revnue) API
Availability: InStock

Official vendor OpenAPI document · agent-readyDeveloper ToolsSource ControlapiKey51 EndpointsREST

For Agents

Programmatically create asset, list assets. Covers 51 operations with apiKey authentication.

Use for: I need to asset, I want to assets, Search for asset, Find all asset

Not supported: Does not handle payments, communications, or crm - use for developer tools only.

Revnue API for managing assets, contracts, customers, suppliers, licenses, and related business entities. The API exposes 51 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Connect the Strev (Revnue) API to your agent

Capabilities

Use Cases

Start building with Strev (Revnue) API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Revnue Strev (Revnue) API