Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Scalr 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%2Fscalr.io%2Fscalr" | 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%2Fscalr.io%2Fscalr" | 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 Scalr API.
Create access policie
List access policies
Get access policie
Update access policie
Delete access policie
Patterns agents use Scalr API for, with concrete tasks.
GET STARTED
★ Productivity Operations
Use the Scalr API to perform productivity operations programmatically. The API provides 74 endpoints covering core functionality including create access policie, list access policies, get access policie.
Call POST /access-policies to create access policie
Automated Access Policies Management
Automate access policies operations by combining multiple Scalr API endpoints. Agents can list access policies and then get access policie in a single workflow.
Call GET /access-policies to list access policies, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Scalr 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 'create access policie', load the operation schema, and execute with Jentic-managed credentials
74 endpoints — scalr is a remote operations backend for terraform and opentofu.
METHOD
PATH
DESCRIPTION
/access-policies
Create access policie
/access-policies
List access policies
/access-policies/{id}
Get access policie
/access-policies/{id}
Update access policie
/access-policies/{id}
Delete access policie
/access-tokens
Create access token
/access-tokens
List access tokens
/access-tokens/{id}
Get access token
/access-policies
Create access policie
/access-policies
List access policies
/access-policies/{id}
Get access policie
/access-policies/{id}
Update access policie
/access-policies/{id}
Delete access policie
/access-tokens
Create access token
/access-tokens
List access tokens
/access-tokens/{id}
Get access token
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Scalr API by hand means setting up its bearer token auth, substituting your account into the host, and managing access-policy and access-token ids yourself. Through Jentic you install once, import the Scalr API from the API Directory, store the bearer token once, and your agent calls it.
Permission scoping
Scalr puts the access-policy id in the URL path (/access-policies/{id}), so a rule can pin your agent to one access policy. You choose the operations it may call, so a destructive one like deleting an access policy or creating an access token is not included unless you add it alongside the reads.
Credential isolation
Your Scalr bearer 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 'create an access policy' or 'list access tokens', and Jentic returns the matching Scalr 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 Scalr API through Jentic.
What authentication does the Scalr API use?
The Scalr 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 create access policie with the Scalr API?
Yes. Use the POST /access-policies endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Scalr 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 create access policie through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create access policie'. Jentic returns the matching Scalr API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Scalr API have?
The Scalr API exposes 74 endpoints covering access policies, access tokens, applies operations.
Can I limit what my agent is allowed to do with the Scalr API?
Yes. Because you run Jentic One yourself, your own rules decide which Scalr operations and credentials the agent may use. Scalr puts the access-policy id in the URL path (/access-policies/{id}), so a rule can pin the agent to a single access policy rather than all of them. You also choose the exact operations it can call, so a destructive action like DELETE /access-policies/{id} or creating an access token stays off limits unless you add it alongside the read endpoints.
For Agents
Programmatically create access policie, list access policies. Covers 74 operations with bearer authentication.
Use for: I need to access policie, I want to access policies, Search for access policie, Find all access policie
Not supported: Does not handle payments, communications, or crm - use for productivity only.
Scalr is a remote operations backend for Terraform and OpenTofu. The API provides management of workspaces, environments, runs, variables, policies, VCS providers, and more. The API exposes 74 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>