Install Jentic One Beta

Connect the DataEcho Public API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DataEcho Public 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%2Fdataecho.ai%2Fdataecho" | 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%2Fdataecho.ai%2Fdataecho" | 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 DataEcho Public API.

Publish a file or folder to a live, edge-served URL

Create versioned cloud drives and list, read, and move files in them

Stage presigned uploads and finalize them with ETag preconditions

Serve per-site data collections as records an agent can read and write

Create short links and manage custom domains and subdomain handles

GET STARTED

Start building with DataEcho Public API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use DataEcho Public API for, with concrete tasks.

★ Agent Memory and Handoff

An AI agent connected through Jentic can keep working files between runs in a private, versioned drive: it creates a drive, stages a presigned upload of a context file, finalizes it with an ETag precondition, and reads it back in a later run. Because drives are versioned, an agent can hand off state to another agent and recover an earlier version if needed.

Create a drive, stage an upload of a context file, finalize it, and read it back in a later run

Instant Static Publishing

DataEcho turns a folder of files into a live, edge-served URL in one flow. An agent creates a site, uploads the files through presigned URLs, finalizes the version to make it live, and returns the public URL. Metadata controls such as TTL, viewer, and password let it tune how the published site behaves.

Publish a folder of HTML files, finalize the version to make it live, and return the public URL

Site Data and Links

Beyond static files, DataEcho stores structured records per site and short links that point to them. An agent can create a record in a site's data collection, read or update it, and mint a short link for sharing. This pairs a published site with a small backing data store and link management.

Create a record in a site's data collection and create a short link pointing to the site

Key Endpoints

56 endpoints — the dataecho api publishes files and folders to live, edge-served urls and stores them in private, versioned cloud drives.

METHOD

PATH

DESCRIPTION

POST

/api/v1/publish

Create a site from presigned uploads

GET

/api/v1/publish/{slug}

Get site details and manifest

POST

/api/v1/drives

Create a drive

GET

/api/v1/drives/{driveId}/files

List files in a drive

POST

/api/v1/drives/{driveId}/files/uploads

Stage a write

GET

/api/v1/drives/{driveId}/files/{path}

Read a file

POST

/api/v1/links

Create or update a link

POST

/api/v1/publish

Create a site from presigned uploads

GET

/api/v1/publish/{slug}

Get site details and manifest

POST

/api/v1/drives

Create a drive

GET

/api/v1/drives/{driveId}/files

List files in a drive

POST

/api/v1/drives/{driveId}/files/uploads

Stage a write

GET

/api/v1/drives/{driveId}/files/{path}

Read a file

POST

/api/v1/links

Create or update a link

Why Jentic?

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

Setup

Wiring the DataEcho API by hand means handling its bearer key, the sign-in code exchange that issues it, presigned upload staging, and ETag preconditions on finalize. Through Jentic you install once, import DataEcho from the API Directory, store the key once, and your agent calls it.

Permission scoping

DataEcho puts the site slug and drive id in the URL path, so a rule can pin your agent to one drive's file operations or one site's data. Destructive operations like site or file deletion stay out of that set unless you add them.

Credential isolation

Your DataEcho 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 'upload a file' or 'publish a site', and Jentic returns the matching DataEcho operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using DataEcho Public API through Jentic.

What authentication does the DataEcho API use?

The DataEcho API authenticates with a bearer token per its OpenAPI spec: you send an Authorization header carrying your API key, which you obtain by requesting and verifying a one-time sign-in code. Through Jentic the token is stored once, encrypted, by your own Jentic One instance and injected at call time.

Can I store files for agent memory with the DataEcho API?

Yes. You can create a versioned drive, stage a presigned upload, finalize it with ETag preconditions, and read or move files later. Drives are private and versioned, which suits agent memory, context, and handoff between runs.

What are the rate limits for the DataEcho API?

The OpenAPI spec does not define rate limits for the DataEcho API. Check the DataEcho documentation at https://dataecho.ai for current limits.

Is there a DataEcho MCP server?

You don't need an MCP server to connect your agent to the DataEcho API. Jentic imports it directly from the API Directory: store your key once and your agent can publish files, manage drives, and read records. Operations are discovered on demand without loading another server's tool definitions into context.

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

Yes. Write a rule that allows only the operations the task needs, such as creating drives and uploading files, so destructive operations like deleting a site, deleting a drive file, or deleting a domain are not included unless you add them. Every call the agent makes is logged.

How do I publish a folder with the DataEcho API through Jentic?

Search Jentic for 'publish a folder to a live URL', and it returns the matching DataEcho operations with their input schemas. Your agent creates the site, uploads the files, finalizes the version, and returns the public URL. To run it on your own infrastructure, install Jentic One from its GitHub repo.

DataEcho Public API

AI ReadinessFoundational (D+)49/100

See full scorecard

Official vendor OpenAPI document · agent-readyStorageObject Storagebearer56 EndpointsREST

For Agents

Publish files and folders to live edge URLs and store them in private versioned drives. Stage presigned uploads, read and move files, serve site data records, and manage links, domains, and secret variables.

Use for: I want to publish a folder to a live URL, Create a cloud drive for agent memory, Stage an upload of a file to a drive, Read a file back from a drive

Not supported: Does not handle relational databases, transactional email, or video transcoding. Use for publishing files to edge URLs and storing them in versioned drives only.

The DataEcho API publishes files and folders to live, edge-served URLs and stores them in private, versioned cloud drives. It creates sites from presigned uploads, finalizes a version to make it live, and serves per-site data collections as records. Drives give agents a place to keep files, context, and handoff state between runs, with staged uploads, ETag preconditions, moves, and reads.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: BSignals: 4

65%

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

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

52%

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.

60%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

93%

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

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: DSignals: 1

44%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the DataEcho Public API to your agent

Capabilities

Start building with DataEcho Public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

DataEcho Public API

Jentic AI Readiness Score

DataEcho Public 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