Revenium Metering API
43
AI ReadinessFoundational (D)43/100
Official vendor OpenAPI document · agent-readyDeveloper ToolsSource ControlapiKey377 EndpointsREST
For Agents
Programmatically retrieve a user, update a user. Covers 377 operations with apiKey authentication.
Use for: I need to a user, I want to a user, Search for a user, Find all deactivate a user
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Revenium Metering API. The API exposes 377 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the Revenium Metering API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Revenium Metering 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.
1
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%2Frevenium.io%2Frevenium" | sh2
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%2Frevenium.io%2Frevenium" | 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.
Capabilities
What an agent can do with Revenium Metering API.
Retrieve a user
Update a user
Delete a User
Deactivate a user
Activate a user
Create a traffic anomaly rule
Use Cases
Patterns agents use Revenium Metering API for, with concrete tasks.
★ Developer Tools Operations
Use the Revenium Metering API to perform developer tools operations programmatically. The API provides 377 endpoints covering core functionality including retrieve a user, update a user, delete a user.
Call GET /users/{id} to retrieve a user
Automated Invoice Reports Management
Automate invoice reports operations by combining multiple Revenium Metering API endpoints. Agents can update a user and then delete a user in a single workflow.
Call PUT /users/{id} to update a user, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Revenium Metering 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 'retrieve a user', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
377 endpoints — revenium metering api.
METHOD
PATH
DESCRIPTION
GET
/users/{id}
Retrieve a user
PUT
/users/{id}
Update a user
DELETE
/users/{id}
Delete a User
PUT
/users/{id}/deactivate
Deactivate a user
PUT
/users/{id}/activate
Activate a user
POST
/traffic-anomalies/rules
Create a traffic anomaly rule
PUT
/traffic-anomalies/rules
Update a traffic anomaly rule
GET
/tiers/{id}
Get a tier
GET
/users/{id}
Retrieve a user
PUT
/users/{id}
Update a user
DELETE
/users/{id}
Delete a User
PUT
/users/{id}/deactivate
Deactivate a user
PUT
/users/{id}/activate
Activate a user
POST
/traffic-anomalies/rules
Create a traffic anomaly rule
PUT
/traffic-anomalies/rules
Update a traffic anomaly rule
GET
/tiers/{id}
Get a tier
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
R
Revenium Metering API
- Foundational (D)43/100
44
Foundational Compliance67
Developer Experience & Jentic Compatibility29
AI-Readiness & Agent Experience40
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
44
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: DSignals: 4
77%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
67
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B+Signals: 4
30%
Example Density
How richly the API is illustrated with examples.
98%
Example Validity
Percentage of examples that conform to their schemas.
46%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
93%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
29
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
60%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
54%
Summary Coverage
Coverage of summaries across operations/tags/info.
40
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: FSignals: 1
40%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Revenium Metering API by hand means handling its X-API-KEY header auth, threading that key through every metering call, and managing retries against api.revenium.io yourself. Through Jentic you install once, import the Revenium Metering API from the API Directory, store the API key once, and your agent calls it.
Permission scoping
Revenium puts the user id in the URL path (/users/{id}), so a rule can pin your agent to one user: it can read that user and nothing else. You choose the operations it may call, so destructive ones like deleting or deactivating a user are not included unless you add them.
Credential isolation
Your Revenium 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 'retrieve a user' or 'create a traffic anomaly rule', and Jentic returns the matching Revenium Metering API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Revenium Metering API through Jentic.
What authentication does the Revenium Metering API use?
The Revenium Metering API uses an API key passed in the `X-API-KEY` 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 retrieve a user with the Revenium Metering API?
Yes. Use the GET /users/{id} endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Revenium Metering 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 retrieve a user through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'retrieve a user'. Jentic returns the matching Revenium Metering API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Revenium Metering API have?
The Revenium Metering API exposes 377 endpoints covering invoice reports, invoices, product keys operations.
Can I limit what my agent is allowed to do with the Revenium Metering API?
Yes. Because you run Jentic One yourself, your own rules decide which Revenium operations and credentials the agent may use. Since the user id sits in the URL path (GET /users/{id}), you can pin the agent to a single user so it reads only that record, and you choose exactly which operations it may call. Destructive calls such as deleting or deactivating a user (DELETE /users/{id}, PUT /users/{id}/deactivate) stay off unless you add them.
GET STARTED