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

# Rackoot API

Rackoot is the starting point for everything you have in the cloud. Manage rackoots (collections) and tiles (items within collections). The API exposes 13 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically authorize, get access token. Covers 13 operations with oauth2 authentication.

## Scope

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

## Capabilities

- Authorize
- Get access token
- Update user profile
- Create a new rackoot
- Access Rackoot API developer tools resources via REST API

## Use cases

### Developer Tools Operations

Use the Rackoot API to perform developer tools operations programmatically. The API provides 13 endpoints covering core functionality including authorize, get access token, update user profile.

Example prompt: Call GET /authorize to authorize

### Automated Authorize Management

Automate authorize operations by combining multiple Rackoot API endpoints. Agents can get access token and then update user profile in a single workflow.

Example prompt: Call POST /token to get access token, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Rackoot 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 oauth2 tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/authorize` | Authorize |
| POST | `/token` | Get access token |
| POST | `/profile` | Update user profile |
| GET | `/profile` | Get user profile |
| POST | `/rackoots` | Create a new rackoot |
| GET | `/rackoots` | Get all rackoots |
| GET | `/rackoots/{rackoot_id}` | Get a single rackoot |
| PUT | `/rackoots/{rackoot_id}` | Edit a rackoot |

## Key resources

- **Authorize** — Operations for authorize
- **Profile** — Operations for profile
- **Rackoots** — Operations for rackoots
- **Tiles** — Operations for tiles
- **Token** — Operations for token

## 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: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 46 / 100
  - Agent Usability: 94 / 100
  - Security: 90 / 100
  - AI Discoverability: 52 / 100
- **View full report:** https://jentic.com/apis/rackoot.com/rackoot/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 Rackoot API by hand means running its OAuth2 authorization code flow, targeting the my.rackoot.com host, and handling token refresh and retries across its profile and rackoot operations yourself. Through Jentic you install once, import Rackoot from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Rackoot puts the rackoot id in the URL path (`/rackoots/{rackoot_id}`), so a rule can pin your agent to one rackoot: it reads and updates that resource and nothing else. You choose the operations it may call, so a write like creating a rackoot is not included unless you add it.
- **Credential handling:** Your Rackoot OAuth 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 'list my rackoots' or 'update a rackoot', and Jentic returns the matching Rackoot 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 Rackoot API use?

The Rackoot API uses OAuth 2.0 for authorization. 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 authorize with the Rackoot API?

Yes. Use the GET /authorize endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Rackoot 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 authorize through Jentic?

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

### How many endpoints does the Rackoot API have?

The Rackoot API exposes 13 endpoints covering authorize, profile, rackoots operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Rackoot operations and credentials the agent may use. Since Rackoot puts the rackoot id in the URL path (`/rackoots/{rackoot_id}`), you can pin the agent to a single rackoot so it only reads and updates that one resource. You also choose the exact operations it can call, so a write such as POST /rackoots to create a new collection stays off unless you grant it.