verapli
Sign inJoin free
Menu

Guides · devtools · Everyday developer services

Temporal Cloud

Managed Temporal service for durable workflows. Create a namespace with API key authentication and an API key (max 2-year expiry).

Researched · not yet run liveLast researched 25 October 2026 · Temporal Technologies · provider site

Researched, not yet run live. Built from the provider’s official pages (linked below). A person hasn’t walked this flow end to end yet, so check each step against the source.
Do this with verapliJSON for agents

Steps

Steps marked “human step” are ones only you can do: verapli never signs in, submits, pays or accepts terms for you.

  1. Sign in or create a Temporal Technologies account

    Sign in to Temporal Technologies. If you have no account yet, you create it yourself; verapli does not create accounts.

    • Guided by hand
    • Human step: You sign in

    Where: https://cloud.temporal.io/

  2. Create a namespace with API key auth

    Go to Namespaces > Create Namespace, enter a lowercase name (2-39 chars), cloud, region and retention (1-90 days), and select Allow API key authentication.

    • Guided by hand
    • Human step: You press submit
    • After: Sign in or create a Temporal Technologies account
    If something goes wrong (1)
    • Need API keys and mTLS on the same namespace: A namespace created with API key auth cannot add mTLS later; for both, use the regional endpoint for API keys. [2]

  3. Create an API key

    In Profile > API Keys create a key (or a Service Account key if you are an admin), set an expiry (max 2 years) and copy it at once; it is shown only once.

    • Guided by hand
    • Human step: You press submit
    • After: Sign in or create a Temporal Technologies account

    verapli captures TEMPORAL_API_KEY here by plain code: encrypted in your browser, never shown to AI.

What you end up with

Env varSecretFormatWhat it is
TEMPORAL_API_KEYsecretTemporal Cloud API key

Renewals

  • Temporal Cloud API key: every up to 2 years (expiry chosen at creation) [1]

Pricing

  • Free tier: $150 credits for 90 days.
  • Costs: From $50 per million actions, no base monthly fee.

Source [3]

For agents

The same entry as JSON: /api/v1/entries/temporal/cloud · requirements /api/v1/requirements/temporal/cloud · terms /api/v1/terms/temporal/cloud.

Remote MCP (read-only, no auth)
claude mcp add --transport http verapli https://verapli.com/mcp

> "What do I need for Temporal Cloud, and how long will it take?"
  → tools/call requirements { "provider_id": "temporal/cloud" }

Sources

  1. Temporal Cloud docs - API keys Profile > API Keys or temporal cloud apikey create-for-me; service account keys by admins; max expiration 2 years; shown only once; up to 10 user keys; TEMPORAL_API_KEY read by the CLI; namespace must allow API key authentication · accessed 25 October 2026 · official
  2. Temporal Cloud docs - Namespaces Namespaces > Create Namespace with name, cloud, region, retention (1-90 days), auth method; naming rules; endpoint <region>.<cloud_provider>.api.temporal.io:7233 · accessed 25 October 2026 · official
  3. Temporal pricing Free $150 credits for 90 days; from $50 per million actions; no base monthly fee · accessed 25 October 2026 · official

Provider rules change. This page is generated from verapli registry version 2026.1025.387; spotted something out of date? Tell us. Temporal Technologies is not affiliated with verapli.