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

# Staatic API documentation

This is the Staatic API. You can find out more about Staatic at [https://staatic.com](https://staatic.com). The API exposes 43 endpoints secured with apiKey, oauth2 authentication.

## For AI agents

Programmatically creates a new deployment, gets a collection of deployments. Covers 43 operations with apiKey, oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Creates a new deployment
- Gets a collection of deployments
- Updates an existing deployment
- Uploads a deployment file
- Monitor Staatic API documentation operational status and events

## Use cases

### Developer Tools Operations

Use the Staatic API documentation to perform developer tools operations programmatically. The API provides 43 endpoints covering core functionality including creates a new deployment, gets a collection of deployments, gets a deployment by id.

Example prompt: Call POST `/v1/deployments` to creates a new deployment

### Automated deployment Management

Automate deployment operations by combining multiple Staatic API documentation endpoints. Agents can gets a collection of deployments and then gets a deployment by id in a single workflow.

Example prompt: Call GET `/v1/deployments` to gets a collection of deployments, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Staatic API documentation 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 apiKey, oauth2 tokens manually.

Example prompt: Search Jentic for 'creates a new deployment', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v1/deployments` | Creates a new deployment |
| GET | `/v1/deployments` | Gets a collection of deployments |
| GET | `/v1/deployments/{id}` | Gets a deployment by ID |
| PATCH | `/v1/deployments/{id}` | Updates an existing deployment |
| GET | `/v1/sites/{id}/files` | Gets a collection of deployment files for the specified site |
| PUT | `/v1/deployments/{id}/files/{path}` | Uploads a deployment file |
| POST | `/v1/forms` | Creates a new form |
| GET | `/v1/forms` | Gets a collection of forms |

## Key resources

- **deployment** — Deployment operations
- **file** — File operations
- **form** — Form operations
- **form-notification** — Form notification operations
- **form-submission** — Form submission operations

## 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:** 60 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 57 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 47 / 100
  - Agent Usability: 94 / 100
  - Security: 55 / 100
  - AI Discoverability: 60 / 100
- **View full report:** https://jentic.com/apis/staatic.com/staatic/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 the Staatic API by hand means choosing between its API key and OAuth 2.0 auth on api.staatic.com and managing deployment and file-upload calls yourself. Through Jentic you install once, import the Staatic API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Staatic puts the deployment id in the URL path (`/v1/deployments/{id}`), so a rule can pin your agent to reading and updating a single deployment. You choose the operations it may call, so ones like uploading deployment files are not included unless you add them.
- **Credential handling:** Your Staatic 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.
- **Discovery method:** Agents search Jentic by intent such as 'create a new deployment' or 'list a site's files', and Jentic returns the matching Staatic API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Staatic API documentation use?

The Staatic API documentation uses apiKey, 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 creates a new deployment with the Staatic API documentation?

Yes. Use the POST `/v1/deployments` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Staatic API documentation?

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 creates a new deployment through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'creates a new deployment'. Jentic returns the matching Staatic API documentation operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Staatic API documentation have?

The Staatic API documentation exposes 43 endpoints covering deployment, file, form operations.

### Can I limit what my agent is allowed to do with the Staatic API?

Yes. Because you run Jentic One yourself, your own rules decide which Staatic operations and credentials the agent may use. Staatic puts the deployment id in the URL path (`/v1/deployments/{id}`), so you can pin the agent to reading and updating a single deployment while leaving operations like uploading deployment files or creating forms out unless you explicitly add them. Only the operations you choose are exposed to the agent.