Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Staatic API documentation, 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%2Fstaatic.com%2Fstaatic" | 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%2Fstaatic.com%2Fstaatic" | 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 Staatic API documentation API.
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
GET STARTED
Patterns agents use Staatic API documentation API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'creates a new deployment', load the operation schema, and execute with Jentic-managed credentials
43 endpoints — this is the staatic api.
METHOD
PATH
DESCRIPTION
/v1/deployments
Creates a new deployment
/v1/deployments
Gets a collection of deployments
/v1/deployments/{id}
Gets a deployment by ID
/v1/deployments/{id}
Updates an existing deployment
/v1/sites/{id}/files
Gets a collection of deployment files for the specified site
/v1/deployments/{id}/files/{path}
Uploads a deployment file
/v1/forms
Creates a new form
/v1/forms
Gets a collection of forms
/v1/deployments
Creates a new deployment
/v1/deployments
Gets a collection of deployments
/v1/deployments/{id}
Gets a deployment by ID
/v1/deployments/{id}
Updates an existing deployment
/v1/sites/{id}/files
Gets a collection of deployment files for the specified site
/v1/deployments/{id}/files/{path}
Uploads a deployment file
/v1/forms
Creates a new form
/v1/forms
Gets a collection of forms
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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.
Alternatives and complements available in the Jentic catalogue.
Specific to using Staatic API documentation API through Jentic.
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.
For Agents
Programmatically creates a new deployment, gets a collection of deployments. Covers 43 operations with apiKey, oauth2 authentication.
Use for: I need to creates a new deployment, I want to gets a collection of deployments, Search for gets a deployment by id, Find all updates an existing deployment
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
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.
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>