Install Jentic One Beta

Connect the Pydio Cells API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Pydio Cells 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%2Fpydio.com%2Fpydio" | 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%2Fpydio.com%2Fpydio" | 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 Pydio Cells API.

Get node metadata

Create file or folder

Delete files or folders

Restore deleted files or folders

Bulk stat nodes

GET STARTED

Start building with Pydio Cells API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Pydio Cells API for, with concrete tasks.

★ Productivity Operations

Use the Pydio Cells API to perform productivity operations programmatically. The API provides 43 endpoints covering core functionality including get node metadata, create file or folder, delete files or folders.

Call GET /a/tree/stat/{Node} to get node metadata

Automated A Management

Automate a operations by combining multiple Pydio Cells API endpoints. Agents can create file or folder and then delete files or folders in a single workflow.

Call POST /a/tree/create to create file or folder, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Pydio Cells 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, oauth2 tokens manually.

Search Jentic for 'get node metadata', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

43 endpoints — rest api for pydio cells, the open-source file sharing and collaboration platform.

METHOD

PATH

DESCRIPTION

GET

/a/tree/stat/{Node}

Get node metadata

POST

/a/tree/create

Create file or folder

POST

/a/tree/delete

Delete files or folders

POST

/a/tree/restore

Restore deleted files or folders

POST

/a/tree/selection

Create a temporary selection of nodes

POST

/a/tree/stats

Bulk stat nodes

POST

/a/tree/admin/list

Admin list nodes

GET

/a/user/{Login}

Get user by login

GET

/a/tree/stat/{Node}

Get node metadata

POST

/a/tree/create

Create file or folder

POST

/a/tree/delete

Delete files or folders

POST

/a/tree/restore

Restore deleted files or folders

POST

/a/tree/selection

Create a temporary selection of nodes

POST

/a/tree/stats

Bulk stat nodes

POST

/a/tree/admin/list

Admin list nodes

GET

/a/user/{Login}

Get user by login

Why Jentic?

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

Setup

Wiring the Pydio Cells API by hand means setting up its bearer or OAuth2 auth, pointing at your own Cells host, and handling tree and user calls yourself. Through Jentic you install once, import the Pydio Cells API from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Pydio Cells drives create, delete, and restore from a request body while node and user reads carry the target in the path, so scope the agent to the operations it needs, such as reading node metadata or listing stats. You choose that allowed set, so deleting nodes is not included unless you add it.

Credential isolation

Your Pydio Cells credential 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 'read node metadata' or 'list files in a folder', and Jentic returns the matching Pydio Cells operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Pydio Cells API through Jentic.

What authentication does the Pydio Cells API use?

The Pydio Cells API uses bearer, oauth2 authentication. 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 get node metadata with the Pydio Cells API?

Yes. Use the GET /a/tree/stat/{Node} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Pydio Cells 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 get node metadata through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get node metadata'. Jentic returns the matching Pydio Cells API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Pydio Cells API have?

The Pydio Cells API exposes 43 endpoints covering a operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which Pydio Cells operations and credentials the agent may use. You can scope it to read-only calls like GET /a/tree/stat/{Node} for node metadata and GET /a/user/{Login} for user lookups, while leaving out the request-body operations that create, delete, or restore nodes. Because you choose the allowed set, POST /a/tree/delete is never callable unless you explicitly add it.

Pydio Cells API

AI ReadinessAI-Aware (B-)63/100

See full scorecard

Official vendor OpenAPI document · agent-readyProductivityCollaborationbearer, oauth243 EndpointsREST

For Agents

Programmatically get node metadata, create file or folder. Covers 43 operations with bearer, oauth2 authentication.

Use for: I need to node metadata, I want to file or folder, Search for files or folders, Find all restore deleted files or folders

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

REST API for Pydio Cells, the open-source file sharing and collaboration platform. Provides 248+ endpoints covering tree/file operations, user management, ACLs, roles, workspaces, sharing, activity streams, configuration, search, jobs/scheduler, authentication, frontend, and meta services. The API exposes 43 endpoints secured with bearer, oauth2 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

97%

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

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

93%

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.

100%

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

75%

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

46%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Pydio Cells API to your agent

Capabilities

Start building with Pydio Cells API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Pydio Cells API

Jentic AI Readiness Score

Pydio Cells 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