canonical: https://jentic.com/apis/scalr.io/scalr

# Scalr API

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.

## For AI agents

Programmatically create access policie, list access policies. Covers 74 operations with bearer authentication.

## Scope

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

## Capabilities

- Create access policie
- List access policies
- Get access policie
- Update access policie
- Delete access policie

## Use cases

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

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

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

Example prompt: Search Jentic for 'create access policie', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/access-policies` | Create access policie |
| GET | `/access-policies` | List access policies |
| GET | `/access-policies/{id}` | Get access policie |
| PATCH | `/access-policies/{id}` | Update access policie |
| DELETE | `/access-policies/{id}` | Delete access policie |
| POST | `/access-tokens` | Create access token |
| GET | `/access-tokens` | List access tokens |
| GET | `/access-tokens/{id}` | Get access token |

## Key resources

- **Access Policies** — Operations for access policies
- **Access Tokens** — Operations for access tokens
- **Applies** — Operations for applies
- **Environments** — Operations for environments
- **Permissions** — Operations for permissions

## 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:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 74 / 100
  - Developer Experience & Jentic Compatibility: 62 / 100
  - AI-Readiness & Agent Experience: 51 / 100
  - Agent Usability: 90 / 100
  - Security: 60 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/scalr.io/scalr/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 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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Asana** — Alternative productivity API
- **Monday** — Alternative productivity API
- **Clickup** — Complementary productivity API

## FAQ

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