Infinispan REST API

Name: Infinispan REST API
Brand: Infinispan REST API
Availability: InStock

✓ Official Vendor SpecStorageDatabasebasic,digest94 EndpointsREST

For Agents

Operate an Infinispan distributed cache cluster: create caches, read/write entries, manage counters, control cross-site replication, run rolling upgrades, and administer the cluster.

Install Jentic One Beta

Connect the Infinispan REST API to your agent

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

Create, modify, clear, and delete named caches via /rest/v2/caches/{cacheName} including alias assignment and rebalancing controls

Add, replace, retrieve, and delete cache entries with /rest/v2/caches/{cacheName}/{cacheKey}

Convert and compare cache configurations across templates and live caches without taking the cluster offline

GET STARTED

Start building with Infinispan REST API

Explore with Jentic

View OpenAPI Document

Use Cases

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

★ Distributed Session and Application Cache

Operate Infinispan as a session store or hot-data cache in front of a slower system of record. POST /rest/v2/caches/{cacheName} creates the cache from a template, POST /rest/v2/caches/{cacheName}/{cacheKey} writes entries, and GET /rest/v2/caches/{cacheName}/{cacheKey} reads them back. Suitable for stateless application servers that need a shared cache layer with replication and failover.

Create a cache named 'sessions' with a distributed-sync template, then POST a JSON value to /rest/v2/caches/sessions/user-123.

Cross-Site Replication and Disaster Recovery

Configure and operate Infinispan's cross-site replication, where a primary datacenter pushes cache state to one or more remote sites. The /rest/v2/cache-managers/{name}/x-site endpoints expose actions to take a remote site online or offline, push state, and inspect replication backlog. Critical for active-active deployments and DR drills where one site has to take over from another within seconds.

Take the 'NYC' remote site offline for a planned datacenter migration and confirm replication backlog clears on the source side.

Rolling Upgrade Between Infinispan Versions

Migrate an Infinispan cluster from one major version to another without downtime by running source and target clusters concurrently and routing traffic between them. The /rest/v2/cluster?action=connect-source and related rolling-upgrade endpoints orchestrate the cutover. Reduces planned-maintenance windows for caches that back live customer-facing systems.

Initiate a rolling upgrade from cluster A to cluster B, monitor the state transfer, and disconnect once the target reports a complete state.

AI Agent Operating a Cache Cluster

An ops agent administers Infinispan deployments — provisioning caches, clearing stale data, taking sites offline during incidents — through Jentic. The agent searches by intent (e.g., 'clear a cache'), loads the schema, and executes against the cluster. Useful for SRE copilots that handle cache lifecycle as part of broader incident playbooks.

List all caches with GET /rest/v2/caches, identify those with zero entries, and POST /rest/v2/caches/{cacheName}?action=clear on each to free memory.

Key Endpoints

94 endpoints — infinispan is an open-source distributed in-memory key/value data store, also used as a clustered cache and embedded data grid.

METHOD

PATH

DESCRIPTION

POST

/rest/v2/caches/{cacheName}

Create a cache from a template or configuration

GET

/rest/v2/caches/{cacheName}

Get cache details and configuration

DELETE

/rest/v2/caches/{cacheName}

Delete a cache

POST

/rest/v2/caches/{cacheName}/{cacheKey}

Add a cache entry

GET

/rest/v2/caches/{cacheName}/{cacheKey}

Retrieve a cache entry by key

POST

/rest/v2/caches/{cacheName}?action=clear

Clear all entries in a cache

POST

/rest/v2/caches?action=compare

Compare two cache configurations

POST

/rest/v2/caches/{cacheName}?action=enable-rebalancing

Enable cluster rebalancing for a cache

POST

/rest/v2/caches/{cacheName}

Create a cache from a template or configuration

GET

/rest/v2/caches/{cacheName}

Get cache details and configuration

DELETE

/rest/v2/caches/{cacheName}

Delete a cache

POST

/rest/v2/caches/{cacheName}/{cacheKey}

Add a cache entry

GET

/rest/v2/caches/{cacheName}/{cacheKey}

Retrieve a cache entry by key

Why Jentic?

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

Credential isolation

Infinispan Basic/Digest credentials are stored encrypted in the Jentic vault (MAXsystem). Because Infinispan endpoints can clear caches and take sites offline, scoping access through Jentic prevents the agent from holding cluster-admin credentials directly.

Intent-based discovery

Agents search Jentic with intents like 'create a cache', 'clear a cache', or 'take a remote site offline' and Jentic returns the matching Infinispan operations with their input schemas — the agent does not have to navigate the 94-endpoint admin surface.

Time to first call

Direct Infinispan REST integration: 1-2 days to handle authentication, configuration JSON shapes, and the action-style query parameters. Through Jentic: under an hour — schema-first execution and credential vaulting handle the boilerplate.

FAQs

Specific to using Infinispan REST API through Jentic.

What authentication does the Infinispan REST API use?

The Infinispan REST API supports HTTP Basic and HTTP Digest authentication, configurable on the server. Through Jentic, the credentials for the cluster endpoint are stored encrypted in the MAXsystem vault and injected at runtime, so the agent never holds the raw username/password pair.

Can I create caches and write entries through the REST API?

Yes. POST /rest/v2/caches/{cacheName} creates a cache from a configuration body or named template, and POST /rest/v2/caches/{cacheName}/{cacheKey} writes an entry. GET /rest/v2/caches/{cacheName}/{cacheKey} reads it back, and DELETE removes it.

What are the rate limits for the Infinispan REST API?

Infinispan is self-hosted, so there are no platform-imposed rate limits — throughput is bounded by the cluster size, network, and cache configuration. Server-side ACL roles and request quotas can be configured if you need to throttle specific principals.

How do I clear a cache through Jentic?

Search Jentic for 'clear an Infinispan cache' to find POST /rest/v2/caches/{cacheName}?action=clear. Load the schema, supply cacheName, and execute. The action removes all entries without deleting the cache itself. Get started at https://app.jentic.com/sign-up.

Does the API support cross-site replication operations?

Yes. The /rest/v2/cache-managers/{name}/x-site and related endpoints let you take remote sites online/offline, push state, and inspect replication backlog — useful for active-active deployments and DR drills.

Can I run a zero-downtime upgrade between Infinispan versions?

Yes. The rolling-upgrade endpoints (/rest/v2/cluster?action=connect-source and friends) orchestrate running source and target clusters concurrently while traffic migrates, so the cache stays available during the version cutover.

Infinispan REST API

Connect the Infinispan REST API to your agent

Capabilities

Start building with Infinispan REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs