Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SmartHub User 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%2Fep.com%2Fep" | shStep 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%2Fep.com%2Fep" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with SmartHub User API.
List the studios and projects a user can access in the EP Residuals Hub
Browse a project's library roots and walk down through nested child folders
Create nested folder paths in one call and attach custom fields such as a ticketNumber
Upload residuals documents to a folder with an overwrite mode and document-type metadata
GET STARTED
Update a folder's custom fields to map a ticketNumber onto an existing folder
Read file metadata and resolve the SmartHub viewer URL to preview a document
Patterns agents use SmartHub User API for, with concrete tasks.
★ Residuals Document Filing
A post-production team files residuals paperwork into the EP Residuals Hub organised by project and quarter. The SmartHub User API creates the nested folder path in one idempotent call, attaches the residuals ticket number as folder metadata, and uploads the signed report with its document type and label so it is findable later.
Create the folder path 2024/Q4/Residuals under a project folder with a ticketNumber of RES-12345, then upload the residuals report into it with a documentType of 'Residuals Report'
Project Library Browsing
An agent navigates a studio's document library without a human clicking through SmartHub. It lists the projects the user can access, reads the root folders for a chosen studio such as Sony Pictures, and walks down through child folders to locate the right residuals folder before acting on its files.
List accessible projects, get the root folders for the Sony Pictures project, then browse its child folders to find the Residuals folder
AI Agent Document Automation via Jentic
An AI agent connects to the SmartHub User API through Jentic without holding EP's OAuth2 or PingOne tokens itself. It searches by intent, receives the matching operation and its input schema, and runs folder creation and file uploads with credentials injected at run time, so a residuals filing workflow completes end to end.
Search Jentic for 'upload a residuals document', load the upload operation schema, and send a file to the target folder with Jentic-managed credentials
9 endpoints — the smarthub user api lists the studios a user can access in the ep residuals hub, browses the folder tree inside each project, and uploads residuals documents with their metadata.
METHOD
PATH
DESCRIPTION
/projects
List accessible studios and projects
/projects/{projectId}/folders
Get a project's library root folders
/folders/{folderId}/folders
Create a folder, including nested paths, with metadata
/folders/{folderId}/files
List files in a folder
/folders/{folderId}/files
Upload a file to a folder
/folders/{folderId}
Update a folder's custom fields
/files/{fileId}
Get file metadata
/projects
List accessible studios and projects
/projects/{projectId}/folders
Get a project's library root folders
/folders/{folderId}/folders
Create a folder, including nested paths, with metadata
/folders/{folderId}/files
List files in a folder
/folders/{folderId}/files
Upload a file to a folder
/folders/{folderId}
Update a folder's custom fields
/files/{fileId}
Get file metadata
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the SmartHub User API by hand means managing two credentials at once: an Apigee OAuth2 client-credentials token for the application and a PingOne user JWT for identity, each sent in its own header. Through Jentic you install once, import SmartHub from the API Directory, store both credentials once, and your agent calls it.
Permission scoping
The SmartHub User API carries the project, folder, and file ids in the URL path, so a rule can scope your agent to specific paths and to the operations you pick, such as read-only browsing of one project's folders. You choose which operations it may call, so folder creation and file upload are not included unless you add them.
Credential isolation
Your Apigee OAuth2 and PingOne tokens are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'upload a residuals document' or 'list project folders', and Jentic returns the matching SmartHub operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using SmartHub User API through Jentic.
What authentication does the SmartHub User API use?
The SmartHub User API requires two tokens per its OpenAPI spec: an Apigee OAuth2 client-credentials token in the Authorization header for application authorization, and a PingOne user JWT in the X-PingOne-JWT header for user identity. Through Jentic both are stored encrypted by your own Jentic One instance and injected at execution time, so neither reaches the agent.
Can I create nested folders with the SmartHub User API?
Yes. The create-folder operation accepts a path like 2024/Q4/Residuals and builds the whole hierarchy in one call, returning the existing folder if it is already there. You can attach custom fields such as a ticketNumber to the deepest folder it creates, which is useful for mapping residuals tickets.
What are the rate limits for the SmartHub User API?
The OpenAPI spec does not specify rate limits for the SmartHub User API. Check with the EP SmartHub team for current limits, and note that folder and file list operations are paginated with a pageSize of up to 200 results per page.
How do I upload a residuals document with the SmartHub User API through Jentic?
Search Jentic for 'upload a residuals document' and it returns the SmartHub upload operation with its input schema. Load the schema and send the file to the target folder with the Apigee OAuth2 and PingOne tokens injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with the SmartHub User API?
Yes. Write a rule that allows only the read operations, such as listing projects and browsing folders, so the agent can navigate the library but cannot create folders or upload files. You pick the exact operations it may call, and every request runs through your own instance where it is logged for review.
Is there a SmartHub User API MCP server?
You don't need an MCP server to give your agent the SmartHub User API. Jentic connects it directly from the API Directory: import it, store your EP credentials once, and your agent calls the folder and file operations it needs without a separate server to install.
Know of an official OpenAPI document? Contribute it →
For Agents
Browse projects and folders in the EP Residuals Hub, create nested folders with ticket metadata, upload residuals documents, and read file metadata. Authenticated with an Apigee OAuth2 token and a PingOne user JWT.
Use for: List the projects I can access in the EP Residuals Hub, Browse the folders inside the Sony Pictures project, Create a 2024/Q4/Residuals folder and tag it with a ticket number, Upload a residuals report into a specific folder
Not supported: Does not handle residuals calculation, payroll, or payment processing. Use for filing and browsing documents in the EP Residuals Hub only.
The SmartHub User API lists the studios a user can access in the EP Residuals Hub, browses the folder tree inside each project, and uploads residuals documents with their metadata. It creates nested folder paths such as a 2024/Q4/Residuals hierarchy in a single call and attaches custom fields like a ticketNumber to a folder. File metadata is returned without the binary so an agent can build the SmartHub viewer URL to preview a document.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>