Install Jentic One Beta

Connect the Deno API to your agent

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

Create projects and deploy code, and redeploy with new configuration

Read build logs and execution logs for a deployment

Provision KV databases and enable database backups

Attach custom domains to a deployment and verify domain ownership

Provision and upload TLS certificates for a domain

GET STARTED

Start building with Deno API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Deno API for, with concrete tasks.

★ Programmatic Deploys

A CI agent ships code to Deno Deploy without the dashboard. It creates a project under the organization, creates a deployment, and reads the build logs to confirm success, redeploying with new configuration if a build fails. The deployment and app logs give the agent the feedback it needs to gate a release.

Call POST /projects/{projectId}/deployments to deploy, then GET /deployments/{deploymentId}/build_logs to confirm the build

Custom Domains and TLS

An agent wires a custom domain to a deployment end to end. It adds the domain to the organization, attaches it to the deployment, verifies ownership, and provisions TLS certificates so the deployment serves traffic on the domain over HTTPS without manual certificate handling.

Call PUT /deployments/{deploymentId}/domains/{domain} to attach the domain, then POST /domains/{domainId}/verify to confirm ownership

KV Database Provisioning

An agent sets up storage for a new service by provisioning a KV database under the organization and enabling backups for it. It can list the organization's databases and inspect a backup's details, keeping the data layer configured alongside the deployment it serves.

Call POST /organizations/{organizationId}/databases to create a KV database, then POST /databases/{databaseId}/database_backups to enable backups

AI Agent Integration via Jentic

An AI agent reaches the Deno API through Jentic without wiring the bearer token itself. It searches by intent, receives the matching operation and its input schema, and executes with the credential injected at run time, chaining project creation, deployment, and log inspection in one release workflow.

Search Jentic for 'deploy a project', load the POST /projects/{projectId}/deployments schema, and execute it with Jentic-managed credentials

Key Endpoints

32 endpoints — the deno api manages the deno deploy platform for an organization.

METHOD

PATH

DESCRIPTION

GET

/organizations/{organizationId}/projects

List projects of an organization

POST

/organizations/{organizationId}/projects

Create a project

POST

/projects/{projectId}/deployments

Create a deployment

GET

/deployments/{deploymentId}/app_logs

Get execution logs of a deployment

POST

/organizations/{organizationId}/databases

Create a KV database

PUT

/deployments/{deploymentId}/domains/{domain}

Attach a domain to a deployment

POST

/domains/{domainId}/verify

Verify ownership of a domain

GET

/projects/{projectId}/analytics

Retrieve project analytics

GET

/organizations/{organizationId}/projects

List projects of an organization

POST

/organizations/{organizationId}/projects

Create a project

POST

/projects/{projectId}/deployments

Create a deployment

GET

/deployments/{deploymentId}/app_logs

Get execution logs of a deployment

POST

/organizations/{organizationId}/databases

Create a KV database

PUT

/deployments/{deploymentId}/domains/{domain}

Attach a domain to a deployment

POST

/domains/{domainId}/verify

Verify ownership of a domain

GET

/projects/{projectId}/analytics

Why Jentic?

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

Setup

Wiring Deno by hand means sending its bearer token to api.deno.com/v1, threading organization and project ids through nested paths, and polling deployment logs yourself. Through Jentic you install once, import Deno from the API Directory, store the token once, and your agent calls it.

Permission scoping

Deno puts the organization and project ids in the URL path, so a rule can pin your agent to one organization or project and the operations you pick. Destructive actions like deleting a project, deployment, or domain are not included unless you add them.

Credential isolation

Your Deno 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 'deploy a project' or 'read deployment logs', and Jentic returns the matching Deno operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Deno API through Jentic.

What authentication does the Deno API use?

The Deno API authenticates with a bearer token in the Authorization header per its OpenAPI spec. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's context.

Can I deploy a project with the Deno API?

Yes. Create a deployment under a project, optionally redeploy with new configuration, and read the build and execution logs to confirm it. The logs come back as structured responses an agent can parse to gate a release.

Can I manage KV databases with the Deno API?

Yes. Provision a KV database under an organization, enable backups for it, and list the databases and backup details. This keeps the storage layer configured alongside the deployments it serves.

How do I deploy a project through Jentic with the Deno API?

Search Jentic for 'deploy a project', and it returns the Deno deployment-creation operation with its input schema. Load the schema and execute POST /projects/{projectId}/deployments with the credential 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 Deno API?

Yes. Deno puts the organization and project ids in the URL path, so a rule can pin your agent to one organization or project and the operations you pick, such as creating deployments and reading logs. Destructive actions like deleting a project, a deployment, or a domain stay out of reach unless you grant them, and every call runs through your own instance where it is logged.

Deno API

AI ReadinessAI-Aware (B+)68/100

See full scorecard

Official vendor OpenAPI document · agent-readyCloud InfrastructureServerlessbearer32 EndpointsREST

For Agents

Create projects and deployments, read build and execution logs, manage KV databases and backups, attach domains, provision TLS certificates, and read analytics on Deno Deploy. Authenticated with a bearer token across 32 operations.

Use for: Create a new project in my organization, Deploy code to a project on Deno Deploy, Get the execution logs for a deployment, Provision a KV database for an organization

Not supported: Does not handle package publishing, the Deno runtime CLI, or billing management. Use for managing Deno Deploy projects, deployments, KV databases, and domains only.

The Deno API manages the Deno Deploy platform for an organization. It creates projects and deployments, redeploys with new configuration, and reads build and execution logs for each deployment. It provisions and backs up KV databases, attaches custom domains to deployments, verifies domain ownership, and provisions TLS certificates, and it reports organization and project analytics over a chosen time window.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

96%

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

60%

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: BSignals: 4

16%

Example Density

How richly the API is illustrated with examples.

93%

Example Validity

Percentage of examples that conform to their schemas.

51%

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: C-Signals: 4

45%

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.

62%

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

78%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Deno API to your agent

Capabilities

Start building with Deno API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Deno API

Jentic AI Readiness Score

Deno 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