Sirv REST API

Name: Sirv REST API
Brand: Sirv REST API
Availability: InStock

✓ Official Vendor SpecIdentity AuthAuthenticationbearer30 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the Sirv REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Sirv REST 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

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

Capabilities

What an agent can do with Sirv REST API.

Get API token

Update account settings

Create sub-account

Query and filter Sirv REST API records by parameters

GET STARTED

Start building with Sirv REST API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Sirv REST API for, with concrete tasks.

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

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.

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.

Search Jentic for 'get API token', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

30 endpoints — sirv is an image management and cdn platform.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

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.

Intent-based discovery

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.

Time to first call

FAQs

Specific to using Sirv REST API through Jentic.

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.

Sirv REST API

Connect the Sirv REST API to your agent

Capabilities

Start building with Sirv REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs