Install Jentic One Beta

Connect the Evana360 API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Evana360 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%2Fswaggerhub.evana-ag%2Fevana360-api" | 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%2Fswaggerhub.evana-ag%2Fevana360-api" | 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 Evana360 API.

Validate user's username and password

Gets a user access token.

Upload a binary file

Download the specified binary file

Delete the specified binary file

GET STARTED

Start building with Evana360 API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Evana360 API for, with concrete tasks.

★ Developer Tools Operations

Use the Evana360 API to perform developer tools operations programmatically. The API provides 51 endpoints covering core functionality including validate user's username and password, gets a user access token., upload a binary file.

Call POST /v1.0.0/authenticate to validate user's username and password

Automated authentication Management

Automate authentication operations by combining multiple Evana360 API endpoints. Agents can gets a user access token. and then upload a binary file in a single workflow.

Call POST /v1.0.0/login to gets a user access token., then verify the result

AI Agent Integration via Jentic

AI agents discover and call Evana360 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 bearer tokens manually.

Search Jentic for 'validate user's username and password', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

51 endpoints — api to consume evana360's logic.

METHOD

PATH

DESCRIPTION

POST

/v1.0.0/authenticate

Validate user's username and password

POST

/v1.0.0/login

Gets a user access token.

POST

/v1.0.0/files

Upload a binary file

GET

/v1.0.0/files/{id}

Download the specified binary file

PUT

/v1.0.0/files/{id}

Upload a new version of the specified binary file

DELETE

/v1.0.0/files/{id}

Delete the specified binary file

GET

/v1.0.0/files/{id}/analysis

Get the data model content (all keys) of the document

GET

/v1.0.0/files/{id}/masterData

Get the elements assigned to the document

POST

/v1.0.0/authenticate

Validate user's username and password

POST

/v1.0.0/login

Gets a user access token.

POST

/v1.0.0/files

Upload a binary file

GET

/v1.0.0/files/{id}

Download the specified binary file

PUT

/v1.0.0/files/{id}

Upload a new version of the specified binary file

DELETE

/v1.0.0/files/{id}

Delete the specified binary file

GET

/v1.0.0/files/{id}/analysis

Get the data model content (all keys) of the document

GET

/v1.0.0/files/{id}/masterData

Get the elements assigned to the document

Why Jentic?

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

Setup

Wiring the Evana360 API by hand means obtaining its bearer token through the authenticate flow, choosing between the sandbox and production Evana hosts, and handling responses yourself. Through Jentic you install once, import the Evana360 API from the API Directory, store the bearer token once, and your agent calls it.

Permission scoping

The Evana360 API puts the file id in the URL path (/v1.0.0/files/{id}/...), so a rule can pin your agent to one file: it can read that file and its analysis and master data and nothing else. You choose the operations it may call, so file deletion is not included unless you add it.

Credential isolation

Your Evana360 API bearer token 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 'get the analysis for a file' or 'upload a file', and Jentic returns the matching Evana360 API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Evana360 API through Jentic.

What authentication does the Evana360 API use?

The Evana360 API uses a Bearer token 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 validate user's username and password with the Evana360 API?

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

What are the rate limits for the Evana360 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 validate user's username and password through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'validate user's username and password'. Jentic returns the matching Evana360 API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Evana360 API have?

The Evana360 API exposes 51 endpoints covering authentication, binary files, documents operations.

Can I limit what my agent is allowed to do with the Evana360 API?

Yes. Because you self-host Jentic One, your own rules decide which Evana360 API operations and credentials the agent may use. Since the API puts the file id in the URL path (/v1.0.0/files/{id}/...), you can pin the agent to a single file so it only reads that file, its analysis, and its master data. You choose the operations it may call, so destructive actions like deleting a binary file are excluded unless you explicitly allow them.

Evana Ag Evana360 API

Browse all Swaggerhub Evana Ag APIs

AI ReadinessAI-Aware (B+)67/100

See full scorecard

Community OpenAPI document · agent-readyDeveloper ToolsSource Controlbearer51 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Programmatically validate user's username and password, gets a user access token.. Covers 51 operations with bearer authentication.

Use for: I need to validate user's username and password, I want to gets a user access token., Search for upload a binary file, Find all download the specified binary file

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

API to consume Evana360's logic. The API exposes 51 endpoints secured with bearer authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

93%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

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

16%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

61%

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: D+Signals: 4

40%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

98%

OperationId Quality

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

57%

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: B-Signals: 1

60%

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.

Connect the Evana360 API to your agent

Capabilities

Start building with Evana360 API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Evana Ag Evana360 API

Jentic AI Readiness Score

Evana360 API

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