Install Jentic One Beta

Connect the VendIoT EV Charging Reporting API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the VendIoT EV Charging Reporting 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%2Felecctro.com%2Felecctro" | 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%2Felecctro.com%2Felecctro" | 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 VendIoT EV Charging Reporting API.

Generate a CSV report of EV charging sessions for a chosen window

Generate a CSV report of accounting periods for billing reconciliation

Filter either report by a start and end date and time range

Use Cases

Patterns agents use VendIoT EV Charging Reporting API for, with concrete tasks.

★ Agent-Driven Charging Report Export

An AI agent connected through Jentic exports EV charging activity on demand by calling the sessions report with a date and time window and handing back the CSV. Because the report is a single parameterised call, the agent fetches a clean, bounded dataset instead of paging a raw event feed.

GET STARTED

Start building with VendIoT EV Charging Reporting API

Explore with Jentic One

View OpenAPI Document

Billing Reconciliation

Operators reconciling charging revenue pull the accounting-periods report for a billing cycle. The VendIoT API returns the accounting data as CSV scoped to the requested date and time window, so a finance pipeline imports the file directly rather than aggregating session rows itself.

Export the accounting-periods report for the current billing window and import it into reconciliation

Usage Dashboard Refresh

A dashboard tracking charging throughput refreshes by requesting the sessions report filtered to the latest window. The date and time filters let an agent fetch only the new rows for an incremental update, keeping the dashboard current without re-pulling history.

Request the sessions report filtered to the last 24 hours and load the rows into the usage dashboard

Key Endpoints

2 endpoints — the vendiot ev charging reporting api generates downloadable csv reports of electric-vehicle charging activity from the elecctro vendiot platform.

METHOD

PATH

DESCRIPTION

GET

/api/evc/sessions

Generate the EV charging sessions report in CSV

GET

/api/evc/accountingPeriods

Generate the accounting periods report in CSV

GET

/api/evc/sessions

Generate the EV charging sessions report in CSV

GET

/api/evc/accountingPeriods

Generate the accounting periods report in CSV

Why Jentic?

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

Setup

Wiring the VendIoT reporting API by hand means setting the `X-API-KEY` header and handling the CSV response format yourself. Through Jentic you install once, import the API from the API Directory, store the key once, and your agent calls the two report operations.

Permission scoping

The API carries only the sessions and accounting-periods report operations, so you choose which of the two your agent may call. There are no write or delete operations here, and a rule keeps the agent to the report you intend.

Credential isolation

Your Elecctro API key is held by your own Jentic One instance, encrypted, and injected into the request header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'export EV charging sessions' or 'pull the accounting report', and Jentic returns the matching VendIoT operation with its date and time parameters so the agent requests the right report.

FAQs

Specific to using VendIoT EV Charging Reporting API through Jentic.

What authentication does the VendIoT EV Charging Reporting API use?

The API authenticates with an API key sent in the `X-API-KEY` request header, per its OpenAPI spec. Through Jentic the key is held by your own Jentic One instance and attached to each report request at execution time, so it never appears in your agent's prompt or logs.

Can I export EV charging sessions as CSV with this API?

Yes. The sessions operation returns a CSV report of charging sessions and the accounting-periods operation returns a CSV accounting report. Both accept a start and end date and time, so your agent can bound each export to exactly the window it needs.

Is there a VendIoT or Elecctro MCP server?

You do not need an MCP server to give your agent the VendIoT EV Charging Reporting API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the two report operations on demand without loading an extra server's tool definitions into its context.

Can I limit what my agent is allowed to do with the VendIoT EV Charging Reporting API?

Yes. The API exposes only two read operations, so you write a rule that allows the sessions report, the accounting-periods report, or both, and the agent can do nothing beyond generating those reports. Every call it makes is logged.

How do I pull EV charging reports through Jentic?

Install the Jentic One command line with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then add the VendIoT EV Charging Reporting API from the Jentic directory and search by intent such as 'export EV charging sessions'. Jentic returns the matching operation with its date and time parameters so your agent builds a valid request. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Elecctro VendIoT EV Charging Reporting API

AI ReadinessAI-Aware (A-)70/100

See full scorecard

Community OpenAPI document · agent-readyAnalyticsBusiness IntelligenceapiKey2 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Generate CSV reports of EV charging sessions and accounting periods from the Elecctro VendIoT platform, filtered to a chosen date and time window.

Use for: Generate a CSV report of EV charging sessions for last month, Export the accounting-periods report for a billing cycle, Retrieve charging session data between two dates, Pull EV charging activity filtered to a specific time window

Not supported: Does not start or stop charging, manage chargers, or process payments. Use for generating EV charging and accounting reports only.

The VendIoT EV Charging Reporting API generates downloadable CSV reports of electric-vehicle charging activity from the Elecctro VendIoT platform. One operation returns a charging-sessions report and the other returns an accounting-periods report, each accepting a date and time window so a pipeline can pull exactly the range it needs. The output is CSV, which drops straight into a billing reconciliation or an energy-usage dashboard.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

50%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C+Signals: 4

89%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

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

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B+Signals: 1

69%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the VendIoT EV Charging Reporting API to your agent

Capabilities

Use Cases

Start building with VendIoT EV Charging Reporting API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Elecctro VendIoT EV Charging Reporting API

Jentic AI Readiness Score

VendIoT - EV Charging Reporting

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness