Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PlayCanvas 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%2Fplaycanvas.com%2Fplaycanvas" | 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%2Fplaycanvas.com%2Fplaycanvas" | 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 PlayCanvas API.
Download app
Get app
Create asset
Delete asset
List assets
Patterns agents use PlayCanvas API for, with concrete tasks.
GET STARTED
★ HR and Recruiting Operations
Use the PlayCanvas API to perform hr recruiting operations programmatically. The API provides 11 endpoints covering core functionality including download app, get app, get project apps.
Call POST /apps/download to download app
Automated Apps Management
Automate apps operations by combining multiple PlayCanvas API endpoints. Agents can get app and then get project apps in a single workflow.
Call GET /apps/{id} to get app, then verify the result
AI Agent Integration via Jentic
AI agents discover and call PlayCanvas 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 tokens manually.
Search Jentic for 'download app', load the operation schema, and execute with Jentic-managed credentials
11 endpoints — rest api for playcanvas, a web-based 3d game engine.
METHOD
PATH
DESCRIPTION
/apps/download
Download app
/apps/{id}
Get app
/projects/{projectId}/apps
Get project apps
/assets
Create asset
/assets/{assetId}
Get asset
/assets/{assetId}
Delete asset
/projects/{projectId}/assets
List assets
/projects/{projectId}/branches
List branches
/apps/download
Download app
/apps/{id}
Get app
/projects/{projectId}/apps
Get project apps
/assets
Create asset
/assets/{assetId}
Get asset
/assets/{assetId}
Delete asset
/projects/{projectId}/assets
List assets
/projects/{projectId}/branches
List branches
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the PlayCanvas API by hand means learning its bearer auth and hand-building requests across its app, asset, project and branch endpoints yourself. Through Jentic you install once, import PlayCanvas from the API Directory, store the token once, and your agent calls it.
Permission scoping
PlayCanvas puts the resource id in the URL path (/projects/{projectId}/assets, /assets/{assetId}), so a rule can pin your agent to one project or asset: it reads and lists that project's assets and branches and nothing else. You choose the operations it may call, so destructive ones like deleting an asset are not included unless you add them.
Credential isolation
Your PlayCanvas 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 'download an app build' or 'list a project's assets', and Jentic returns the matching PlayCanvas 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 PlayCanvas API through Jentic.
What authentication does the PlayCanvas API use?
The PlayCanvas API uses a Bearer token in the Authorization header. 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 download app with the PlayCanvas API?
Yes. Use the POST /apps/download endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the PlayCanvas 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 download app through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'download app'. Jentic returns the matching PlayCanvas API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the PlayCanvas API have?
The PlayCanvas API exposes 11 endpoints covering apps, assets, jobs operations.
Can I limit what my agent is allowed to do with the PlayCanvas API?
Yes. Jentic One is self-hosted, so your own rules decide which PlayCanvas operations and credentials the agent may use. Because PlayCanvas puts the resource id in the URL path, such as /projects/{projectId}/assets and /assets/{assetId}, you can pin the agent to a single project so it only lists and reads that project's assets and branches. You also choose which operations it may call, so a destructive endpoint like DELETE /assets/{assetId} stays off limits unless you explicitly add it.
For Agents
Programmatically download app, get app. Covers 11 operations with bearer authentication.
Use for: I need to download app, I want to app, Search for project apps, Find all asset
Not supported: Does not handle payments, communications, or crm - use for hr and recruiting only.
REST API for PlayCanvas, a web-based 3D game engine. Manage apps, assets, branches, scenes, checkpoints, jobs, and project exports. The API exposes 11 endpoints secured with bearer authentication.
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>