Temporal
Temporal is an open-source durable execution platform for building reliable long-running distributed workflows and microservices.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles Temporal the way a machine reads it — 86 machine-readable artifacts across 7 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Temporal scores 73.0/100 (exemplar), with a separate agent-readiness read of 60/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Temporal
Each block below is one kind of artifact we hold for Temporal. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 7
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Temporal Server Frontend API
The Temporal Server Frontend API provides gRPC services for interacting with the Temporal Server, including WorkflowService for managing workflow executions, OperatorService for...
Temporal API Keys API
The API Keys API from Temporal — 2 operation(s) for api keys.
Temporal Async Operations API
The Async Operations API from Temporal — 1 operation(s) for async operations.
Temporal Namespaces API
The Namespaces API from Temporal — 3 operation(s) for namespaces.
Temporal Regions API
The Regions API from Temporal — 1 operation(s) for regions.
Temporal Service Accounts API
The Service Accounts API from Temporal — 2 operation(s) for service accounts.
Temporal Users API
The Users API from Temporal — 2 operation(s) for users.
Scroll within the panel for all 7 ·
Postman Collections 1
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Temporal Cloud Operations API
OPEN COLLECTIONArazzo Workflows 11
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Temporal Audit API Keys for an Owner
List a Service Account's API keys and load the detail of one of them.
ARAZZOTemporal Delete a Namespace and Confirm Removal
Verify a Namespace exists, delete it, then confirm it is gone.
ARAZZOTemporal Deprovision a User and Confirm Removal
Read a User to confirm it exists, delete it, then verify it is gone.
ARAZZOTemporal Find a Namespace by Name and Load Its Details
Page through Namespaces to find one by name, then load its full detail record.
ARAZZOTemporal Issue an API Key for a New Service Account
Create a Service Account, read it back, then issue an API key owned by it.
ARAZZOTemporal Provision a Namespace in a Validated Region
Confirm a region is available, create a Namespace there, then poll until provisioning finishes.
ARAZZOTemporal Provision a Namespace and Wait Until Ready
Create a Temporal Cloud Namespace and poll its async operation until it finishes.
ARAZZOTemporal Provision a User and Verify Membership
Create a User, then page Users to confirm the new account appears.
ARAZZOTemporal Rotate an API Key for an Owner
Read the owner of an existing key, mint a replacement key, then revoke the old one.
ARAZZOTemporal Track an Async Operation to Completion
Poll a Temporal Cloud async operation until it leaves the pending state, branching on outcome.
ARAZZOTemporal Update a Namespace With Optimistic Concurrency
Read a Namespace, update its spec using the current resourceVersion, then confirm the change.
ARAZZOScroll within the panel for all 11 ·
Agent Skills 1
An agent skill packages the how-to for driving these APIs from an assistant — the prompts, the sequence, the guardrails — so the knowledge to use the API travels with it.
Packaged agent skills for driving this provider's APIs from an AI assistant.
temporal-developer
AGENT SKILLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Temporal Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Temporal Finops
FINOPSFeatures 8
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Durable Execution
Automatically persists workflow state and resumes execution after failures, ensuring long-running processes complete reliably.
Namespace Management
Create and manage isolated namespaces for organizing workflows with independent retention policies and access controls.
User and Access Management
Manage users, service accounts, and API keys for fine-grained access control to Temporal Cloud resources.
Multi-Region Deployment
Deploy workflows across multiple cloud regions for low-latency execution and disaster recovery.
Workflow Versioning
Safely deploy workflow code changes with built-in versioning that prevents breaking running executions.
Visibility and Search
Query and filter workflow executions using custom search attributes for operational visibility and debugging.
mTLS Authentication
Secure namespace communication with mutual TLS certificate-based authentication and codec server encryption.
Async Operations
Track the status of long-running control plane operations like namespace creation and configuration changes.
Scroll within the panel for all 8 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Cloud Ops Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Temporal API Rules
SPECTRALTemporal API Rules
SPECTRALJSON Schema 12
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
ApiKey
JSON SCHEMAAsyncOperation
JSON SCHEMACreateApiKeyRequest
JSON SCHEMACreateNamespaceRequest
JSON SCHEMACreateNamespaceResponse
JSON SCHEMACreateServiceAccountRequest
JSON SCHEMACreateUserRequest
JSON SCHEMANamespace
JSON SCHEMARegion
JSON SCHEMAServiceAccount
JSON SCHEMAUpdateNamespaceRequest
JSON SCHEMAUser
JSON SCHEMAScroll within the panel for all 12 ·
JSON Structure 12
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Cloud Ops Api Key Structure
JSON STRUCTURECloud Ops Async Operation Structure
JSON STRUCTURECloud Ops Create Api Key Request Structure
JSON STRUCTURECloud Ops Create Namespace Request Structure
JSON STRUCTURECloud Ops Create Namespace Response Structure
JSON STRUCTURECloud Ops Create Service Account Request Structure
JSON STRUCTURECloud Ops Create User Request Structure
JSON STRUCTURECloud Ops Namespace Structure
JSON STRUCTURECloud Ops Region Structure
JSON STRUCTURECloud Ops Service Account Structure
JSON STRUCTURECloud Ops Update Namespace Request Structure
JSON STRUCTURECloud Ops User Structure
JSON STRUCTUREScroll within the panel for all 12 ·
Examples 12
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Cloud Ops Api Key Example
EXAMPLECloud Ops Namespace Example
EXAMPLECloud Ops Region Example
EXAMPLECloud Ops User Example
EXAMPLEScroll within the panel for all 12 ·
Security Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Microservice Orchestration
Coordinate complex multi-service transactions with automatic retries, compensation logic, and timeout handling.
Data Pipeline Processing
Build reliable ETL and data processing pipelines that handle failures gracefully and resume from the last checkpoint.
Order Fulfillment Workflows
Automate end-to-end order processing including payment, inventory, shipping, and notification steps with guaranteed completion.
Infrastructure Provisioning
Orchestrate cloud infrastructure deployment and configuration management with durable state tracking.
Subscription and Billing Management
Manage recurring billing cycles, subscription renewals, and payment processing with long-running timer-based workflows.
Integrations 5
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Go SDK
Native Go client library for building Temporal workflows and activities with full type safety.
TypeScript SDK
TypeScript/JavaScript SDK for building Temporal workflows in Node.js with async/await patterns.
Python SDK
Python SDK for building Temporal workflows with native async support and type hints.
Java SDK
Java SDK for building Temporal workflows with annotation-based workflow and activity definitions.
.NET SDK
.NET SDK for building Temporal workflows in C# with strong typing and async patterns.
Resources
Every other property we hold for Temporal — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 6
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 12
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 12 ·
Build 6
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/temporal · machine-readable index on apis.io