canonical: https://jentic.com/apis/deno.com/deno

# Deno API

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.

## For AI 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.

## Scope

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

## Capabilities

- 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
- Read organization and project analytics over a chosen time window

## Use cases

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

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

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

## Key resources

- **Organizations** — Read organization details, projects, databases, domains, and analytics
- **Projects and Deployments** — Create projects, deploy, redeploy, and read build and app logs
- **KV Databases** — Provision KV databases and manage database backups
- **Domains and Certificates** — Attach domains, verify ownership, and provision TLS certificates

## 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:** 68 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 89 / 100
  - Developer Experience & Jentic Compatibility: 65 / 100
  - AI-Readiness & Agent Experience: 52 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 78 / 100
- **View full report:** https://jentic.com/apis/deno.com/deno/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 <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Vercel** — Frontend and serverless deployment platform
- **Netlify** — Web deployment and edge functions platform
- **Railway** — Container and app deployment with managed infrastructure
- **Cloudflare** — Edge network, DNS, and Workers

## FAQ

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