Install Jentic One Beta

Connect the Emineo Download Center Folders Files API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Emineo Download Center Folders Files 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%2Fnueva.io%2Fnueva" | 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%2Fnueva.io%2Fnueva" | 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 Emineo Download Center Folders Files API.

Upload a file into an existing product folder by passing productId and parentFolderId

Create a new root-level folder for a product during upload with rootFolderName, defaulting to the product title

Attach a display name, alternativeText, and caption to an uploaded file

Read back the resolved folder path and the stored file's id, mime, size, and url from the upload response

GET STARTED

Start building with Emineo Download Center Folders Files API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Emineo Download Center Folders Files API for, with concrete tasks.

★ Agent-maintained product download pages

A product team's AI agent keeps each product's downloads current when a new datasheet is published. Through Jentic the agent searches for 'upload a file to a product folder', gets the Emineo upload operation with its input schema, and sends a multipart request with the required productId and files, plus the parentFolderId of the product's datasheet folder. The api-token is injected at call time, and the agent records the returned file id for later replacement.

Call POST /folders/files as multipart with productId, parentFolderId, files set to the new datasheet PDF, and caption 'Datasheet v2', then store the returned file.id and file.url

Creating a folder on first upload

When a product has no download folder yet, an upload can create one. Leaving parentFolderId empty and passing rootFolderName creates a new folder at the root of the product's tree, and if rootFolderName is also omitted the product title is used. The response returns the folder id and path so later uploads can target it directly.

Call POST /folders/files as multipart with productId, rootFolderName 'Installation guides', and files set to the install guide, then save the returned folder.id for future uploads

Replacing outdated downloads

Retiring an old file is a single delete. DELETE /folders/files/{id} removes a file by the id returned at upload time, and DELETE /folders/files/by-url removes it by the exact URL stored for the file, which helps when only the public link is known. Both leave the folder in place and return a deleted flag.

Call DELETE /folders/files/by-url with url set to the old datasheet's stored URL, confirm deleted is true, then upload the new version with POST /folders/files

Key Endpoints

3 endpoints — the emineo download center folders files api uploads files into the folder tree that belongs to a product in the emineo download center, and removes them again.

METHOD

PATH

DESCRIPTION

POST

/folders/files

Upload files into a product folder

DELETE

/folders/files/{id}

Delete an uploaded file by id

DELETE

/folders/files/by-url

Delete an uploaded file by URL

POST

/folders/files

Upload files into a product folder

DELETE

/folders/files/{id}

Delete an uploaded file by id

DELETE

/folders/files/by-url

Delete an uploaded file by URL

Why Jentic?

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

Setup

Wiring the Emineo Download Center by hand means sending the api-token header, building multipart uploads with productId and files, and tracking folder ids. Through Jentic you install once, import it from the API Directory, store the token once, and your agent calls it.

Permission scoping

The upload and the two deletes sit at separate paths (/folders/files, /folders/files/{id}, /folders/files/by-url), and the product and folder travel in the request body, so a rule bounds which operations your agent may call rather than which product. You choose the operations, so deletes are not included unless you add them.

Credential isolation

Your Emineo API 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 'upload a file to a product folder' or 'delete a product file by URL', and Jentic returns the matching Emineo operation with its input schema, including productId, parentFolderId, and rootFolderName, so the agent builds the request correctly.

FAQs

Specific to using Emineo Download Center Folders Files API through Jentic.

What authentication does the Emineo Download Center Folders Files API use?

Per its OpenAPI spec, the API authenticates with a static API token sent in the api-token request header. Through Jentic the token is held by your own instance and injected at call time, so your agent never handles it.

Can I upload a file without an existing folder in the Emineo Download Center?

Yes. POST /folders/files requires productId and files, and parentFolderId is optional. Without it, the API creates a root-level folder named by rootFolderName, or by the product title if you omit that too, and returns the new folder's id and path.

What are the rate limits for the Emineo Download Center Folders Files API?

The OpenAPI spec does not specify rate limits. Check with Nueva, the provider, at https://nueva.io for current limits.

How do I delete a file when I only have its link?

Call DELETE /folders/files/by-url with the url query parameter set to the exact file URL as stored for the upload. The response returns the file id, the url, and a deleted flag. If you kept the id from the upload response, DELETE /folders/files/{id} does the same by id.

How do I upload a product file through Jentic?

Search Jentic for 'upload a file to a product folder', load the Emineo upload operation, and send a multipart request with productId, files, and optionally parentFolderId, name, and caption. The response gives the stored file's id and url for your records. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there an Emineo Download Center MCP server?

You do not need an MCP server to give your agent the Emineo Download Center. Jentic connects it directly from the API Directory: import it, store your API token once, and your agent calls the upload and delete operations it needs on demand.

Can I limit what my agent is allowed to do with the Emineo Download Center Folders Files API?

Yes. Write a rule that allows only POST /folders/files, and the agent can add files to product folders but cannot call either delete operation. If you later want it to retire old files, add DELETE /folders/files/{id} alone, and the calls it makes are logged for review.

Nueva Emineo Download Center Folders Files API

AI ReadinessFoundational (D+)47/100

See full scorecard

Community OpenAPI document · agent-readyStorageDocument ManagementapiKey3 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Upload a file into a product's folder in the Emineo download center with an optional caption and alt text, and delete uploaded files by id or by URL.

Use for: Upload a product datasheet PDF to the download center, Add a manual to an existing folder for a product, Create a new folder for a product and upload its brochure, Set a caption and alt text on an uploaded product image

Not supported: Does not list products, browse folder contents, or manage download-center users. Use for uploading files into product folders and deleting uploaded files only.

The Emineo Download Center Folders Files API uploads files into the folder tree that belongs to a product in the Emineo download center, and removes them again. An upload names the owning productId and either an existing parentFolderId or a rootFolderName for a new root-level folder, which defaults to the product title, and can set a display name, alternative text, and caption. The response returns the product, the resolved folder with its path, and the stored file record with its id, MIME type, size, and URL. A file can then be deleted by its id or by its exact stored URL, and the folder itself remains.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

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

75%

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

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: FSignals: 4

37%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

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: ASignals: 1

83%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Emineo Download Center Folders Files API to your agent

Capabilities

Start building with Emineo Download Center Folders Files API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Nueva Emineo Download Center Folders Files API

Jentic AI Readiness Score

Emineo Download Center Folders Files 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