Temporal Cloud Ops API

Name: Temporal Cloud Ops API
Brand: Temporal Cloud Ops API
Availability: InStock

✓ Official Vendor SpecPaymentsBilling Subscriptionsbearer45 EndpointsREST

For Agents

Programmatically update account configuration, get account details. Covers 45 operations with bearer authentication.

Install Jentic One Beta

Connect the Temporal Cloud Ops API to your agent

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

Update account configuration

Get account details

Create an API key

List API keys

GET STARTED

Start building with Temporal Cloud Ops API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Temporal Cloud Ops API for, with concrete tasks.

★ Payments Operations

Use the Temporal Cloud Ops API to perform payments operations programmatically. The API provides 45 endpoints covering core functionality including update account configuration, get account details, get current identity.

Call POST /cloud/account to update account configuration

Automated Cloud Management

Automate cloud operations by combining multiple Temporal Cloud Ops API endpoints. Agents can get account details and then get current identity in a single workflow.

Call GET /cloud/account to get account details, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Temporal Cloud Ops 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 'update account configuration', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

45 endpoints — http api for programmatic management of temporal cloud control plane resources including namespaces, users, service accounts, api keys, audit logs, and billing.

METHOD

PATH

DESCRIPTION

POST

/cloud/account

Update account configuration

GET

/cloud/account

Get account details

GET

/cloud/current-identity

Get current identity

POST

/cloud/api-keys

Create an API key

GET

/cloud/api-keys

List API keys

POST

/cloud/api-keys/{keyId}

Update an API key

GET

/cloud/api-keys/{keyId}

Get an API key

DELETE

/cloud/api-keys/{keyId}

Delete an API key

POST

/cloud/account

Update account configuration

GET

/cloud/account

Get account details

GET

/cloud/current-identity

Get current identity

POST

/cloud/api-keys

Create an API key

GET

/cloud/api-keys

List API keys

POST

Why Jentic?

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

Credential isolation

Your Temporal Cloud bearer token 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.

Intent-based discovery

Agents search Jentic by intent such as 'read account configuration' or 'list API keys', and Jentic returns the matching Temporal Cloud Ops API 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 Temporal Cloud Ops API through Jentic.

What authentication does the Temporal Cloud Ops API use?

The Temporal Cloud Ops 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 update account configuration with the Temporal Cloud Ops API?

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

What are the rate limits for the Temporal Cloud Ops 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 update account configuration through Jentic?

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

How many endpoints does the Temporal Cloud Ops API have?

The Temporal Cloud Ops API exposes 45 endpoints covering cloud operations.

Can I limit what my agent is allowed to do with the Temporal Cloud Ops API?

Yes. Because you run Jentic One yourself and self-host it, your own rules decide which Temporal Cloud Ops API operations and credentials the agent may use. Since the key id sits in the URL path (/cloud/api-keys/{keyId}), you can pin the agent to just the operations it needs, such as GET /cloud/account to read account details or GET /cloud/api-keys to list keys. Destructive calls like DELETE /cloud/api-keys/{keyId} are excluded unless you explicitly grant them.

Temporal Cloud Ops API

Connect the Temporal Cloud Ops API to your agent

Capabilities

Start building with Temporal Cloud Ops API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs