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

# Sirv REST API

Sirv is an image management and CDN platform. The REST API provides programmatic access to account management, file operations, image processing, statistics, and more. Authentication uses JWT bearer tokens obtained via client credentials. The API exposes 30 endpoints secured with bearer authentication.

## For AI agents

Programmatically get API token, update account settings. Covers 30 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- Get API token
- Update account settings
- Create sub-account
- Query and filter Sirv REST API records by parameters
- Monitor Sirv REST API operational status and events

## Use cases

### Identity and Authentication Operations

Use the Sirv REST API to perform identity auth operations programmatically. The API provides 30 endpoints covering core functionality including get API token, update account settings, get account information.

Example prompt: Call POST /token to get API token

### Automated Authentication Management

Automate authentication operations by combining multiple Sirv REST API endpoints. Agents can update account settings and then get account information in a single workflow.

Example prompt: Call POST /account to update account settings, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Sirv REST 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 'get API token', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /token | Get API token |
| POST | /account | Update account settings |
| GET | /account | Get account information |
| GET | /account/limits | Get API rate limits |
| GET | /account/storage | Get storage usage |
| GET | /account/users | Get account users |
| POST | /account/sub-account | Create sub-account |
| DELETE | /account/sub-account | Close sub-account |

## Key resources

- **Authentication** — Token management
- **Account** — Account management operations
- **Billing** — Billing and plan information
- **User** — User management
- **Files** — File operations (upload, download, search, manage)

## Why Jentic

- **Setup:** Wiring the Sirv REST API by hand means exchanging your client credentials for a bearer token at /token and carrying that token across every account call yourself. Through Jentic you install once, import Sirv from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** Sirv scopes calls to the account behind the token rather than a resource id in the URL path, so scope the agent by operations: limit it to the operations it needs, such as reading account limits, storage, or users, and leave out changes like deleting a sub-account unless you add them.
- **Credential handling:** Your Sirv credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get an API token' or 'check account storage', and Jentic returns the matching Sirv operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the Sirv REST API use?

The Sirv REST 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 get API token with the Sirv REST API?

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

### What are the rate limits for the Sirv REST 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 get API token through Jentic?

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

### How many endpoints does the Sirv REST API have?

The Sirv REST API exposes 30 endpoints covering authentication, account, billing operations.

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

Yes. Because Sirv scopes calls to the account behind your bearer token rather than a resource id in the URL, you control access at the operation level in your self-hosted Jentic One instance, where your own rules decide which Sirv operations and credentials the agent may use. Limit the agent to just the operations it needs, such as reading account limits, storage usage, or account users, and leave out changes like updating account settings or closing a sub-account unless you explicitly grant them.