OpenStack Swift Object Storage API

Name: OpenStack Swift Object Storage API
Brand: OpenStack Swift Object Storage API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentStorageObject StorageapiKey13 EndpointsREST

For Agents

Upload, list, retrieve, and delete objects in OpenStack Swift containers using a Keystone authentication token.

Install Jentic One Beta

Connect the OpenStack Swift Object Storage API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the OpenStack Swift Object Storage 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 OpenStack Swift Object Storage API.

Upload objects of arbitrary size into a named container

List containers in an account and objects within a container

Retrieve and update container and object metadata

GET STARTED

Start building with OpenStack Swift Object Storage API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use OpenStack Swift Object Storage API for, with concrete tasks.

★ Self-hosted backup target for application data

An operations team uses an in-house OpenStack deployment as the backup target for application snapshots, writing each snapshot as a Swift object inside a per-day container. Swift's ACLs and account quotas let the team isolate backups per service without leaving the private cloud, and bulk-delete cleans up expired retention windows in one call.

PUT a tar.gz to /v1/{account}/backups-2026-06-10/{object}, then issue a bulk-delete against the previous month's container.

Static asset hosting from Swift

A platform team serves static assets out of Swift containers via a CDN, with each tenant's content in its own account/container. The metadata endpoints let the team set cache headers and ACLs per object so assets are cacheable for the public while bucket configuration stays on the storage side.

PUT an image to /v1/{account}/{container}/{object} with X-Object-Meta-CacheControl, then GET the same object and confirm the metadata.

Lifecycle cleanup with bulk delete

A data engineering team runs scheduled cleanup against a large Swift container by collecting expired object names and submitting them to /v1/{account}/{container}?bulk-delete in one call. This avoids per-object DELETE round trips and keeps cleanup jobs within their maintenance window.

POST a newline-separated list of object names to /v1/{account}/{container}?bulk-delete and verify the response reports zero errors.

Agent-driven private-cloud storage through Jentic

An AI ops agent that triages incidents archives evidence (logs, packet captures) into a Swift container via Jentic. Jentic isolates the Keystone token rotation, so the agent only ever has scoped tool access to the Swift operations rather than the long-lived auth credentials.

Search Jentic for 'upload an object to OpenStack Swift', load PUT /v1/{account}/{container}/{object}, and execute it with the evidence file.

Key Endpoints

13 endpoints — jentic publishes the only available openapi specification for openstack swift object storage api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/info

Discover cluster capabilities and limits

GET

/v1/{account}

List containers in an account

PUT

/v1/{account}/{container}

Create or update a container

GET

/v1/{account}/{container}

List objects in a container

PUT

/v1/{account}/{container}/{object}

Upload an object

GET

/v1/{account}/{container}/{object}

Download an object

DELETE

/v1/{account}/{container}/{object}

Delete an object

GET

/info

Discover cluster capabilities and limits

GET

/v1/{account}

List containers in an account

PUT

/v1/{account}/{container}

Create or update a container

GET

/v1/{account}/{container}

List objects in a container

PUT

/v1/{account}/{container}/{object}

Upload an object

Why Jentic?

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

Credential isolation

Long-lived OpenStack Keystone credentials sit in the encrypted Jentic vault. Jentic obtains a fresh X-Auth-Token per call window so the agent never holds the raw username, password, or project info.

Intent-based discovery

Agents express intents like 'upload an object to OpenStack Swift' or 'list containers in an account', and Jentic returns the matching /v1/{account}/... operation with its path parameter and metadata-header schema.

Time to first call

Direct integration: a day to wire Keystone token refresh, container ACLs, and large-object handling. Through Jentic: a few hours for the call surface — Keystone deployment topology remains a separate concern.

FAQs

Specific to using OpenStack Swift Object Storage API through Jentic.

Why is there no official OpenAPI spec for OpenStack Swift Object Storage API?

OpenStack Swift does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call OpenStack Swift Object Storage API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the OpenStack Swift API use?

Swift uses a Keystone authentication token passed in the X-Auth-Token header. Through Jentic, the long-lived Keystone credentials sit in the encrypted vault and Jentic obtains and rotates the per-request token, so the agent only handles scoped tool access.

Can I bulk-delete objects with the Swift API?

Yes. POST a newline-separated list of objects to /v1/{account}/{container}?bulk-delete and Swift returns a summary of successes and failures. This is much faster than issuing per-object DELETE calls during lifecycle cleanup.

What are the rate limits for the OpenStack Swift API?

Because Swift is self-hosted on each operator's OpenStack cluster, rate limits depend on the cluster's middleware configuration (notably ratelimit middleware) rather than a vendor quota. Inspect /info to see which limits the cluster enforces.

How do I upload an object through Jentic?

Run pip install jentic, search 'upload an object to OpenStack Swift', load PUT /v1/{account}/{container}/{object}, and execute it with the file body and the right account/container path. Jentic supplies the X-Auth-Token header from a refreshed Keystone token.

Why is the base URL a placeholder?

Swift runs as part of an operator's OpenStack deployment, so the spec uses {swift-endpoint} as a server variable. Set it to your cluster's Swift proxy URL (for example, https://swift.cloud.example.com) when configuring the operation.

OpenStack Swift Object Storage API

Connect the OpenStack Swift Object Storage API to your agent

Capabilities

Start building with OpenStack Swift Object Storage API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs