canonical: https://jentic.com/apis/dataecho.ai/dataecho # DataEcho Public API 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. ## For AI 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. ## Scope Does not handle relational databases, transactional email, or video transcoding. Use for publishing files to edge URLs and storing them in versioned drives only. ## Capabilities - 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 - Store named secret variables without exposing their values - Duplicate, update, and version published sites ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: Create a record in a site's data collection and create a short link pointing to the site ## Key endpoints | 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 | ## Key resources - **Sites** — Publish, finalize, duplicate, and version sites, and manage their metadata. - **Drives and Files** — Create versioned drives and stage, finalize, read, move, and delete files. - **Site Data** — Create, read, update, and delete records in per-site data collections. - **Links, Domains, and Handles** — Create short links, attach custom domains, and claim subdomain handles. - **Variables** — Store and delete named secret variables without exposing their values. ## AI readiness 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. - **Score:** 49 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 66 / 100 - Developer Experience & Jentic Compatibility: 62 / 100 - AI-Readiness & Agent Experience: 28 / 100 - Agent Usability: 93 / 100 - Security: 60 / 100 - AI Discoverability: 44 / 100 - **View full report:** https://jentic.com/apis/dataecho.ai/dataecho/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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. ## Related APIs - **pCloud** — Cloud file storage with upload, download, and sharing. - **Apideck File Storage** — Unified file-storage API across multiple storage providers. - **Amazon MediaStore** — Media object storage with low-latency delivery for streaming assets. ## FAQ ### 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.