Apache Samza

Apache Samza is a distributed stream processing framework that provides a simple API for building stateful stream processing applications. It integrates with Apache Kafka for messaging and supports both stream and batch processing.

Apache Samza publishes 3 API contracts indexed on the APIs.io network: Checkpoints API, Jobs API, and Tasks API. Tagged areas include Big Data, Hadoop, Kafka, Stream Processing, and Streaming.

The Apache Samza catalog on APIs.io includes 1 JSON-LD context and 2 Spectral governance rulesets.

Apache Samza’s developer surface includes documentation, engineering blog, and 11 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

27.2/100 thin ▬ flat Agent 17/100 agent aware Heartbeat 0/100 dormant Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessFreemium

1 published contract 6 Features 4 Use Cases

Big Data Hadoop Kafka Stream Processing Streaming Apache Open Source

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 27.2/100 · thin

Contract Quality 9.0 / 19

Developer Ergonomics 1.8 / 15

Access Clarity 1.2 / 15

Operational Transparency 2.1 / 10

Contract Governance 2.5 / 9

Discoverability 4.3 / 8

Regulatory Posture 2.5 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 17/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 0 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/apache-samza/"><img src="https://apis.io/badge/apache-samza/card.svg" alt="Apache Samza on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Machine-Readable Auth +10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey)
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

10 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 7.9 — up to +18.4 composite points
Developer Ergonomics scores 11.9 — up to +17.6 composite points
Contract Quality scores 47.9 — up to +13.0 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/apache-samza/apis.yml: open an issue on github.com/api-evangelist/apache-samza to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 3

Individual APIs this provider publishes, each with its own machine-readable definition.

Apache Samza Checkpoints API

The Checkpoints API from Apache Samza — 1 operation(s) for checkpoints.

Apache Samza Jobs API

The Jobs API from Apache Samza — 4 operation(s) for jobs.

Apache Samza Tasks API

The Tasks API from Apache Samza — 1 operation(s) for tasks.

Open Collections 3

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Apache Samza REST Checkpoints API

OPEN COLLECTION

Apache Samza REST Checkpoints Jobs API

OPEN COLLECTION

Apache Samza REST Checkpoints Tasks API

OPEN COLLECTION

Apache Samza API pricing

Not yet checked against Apache Samza's own pricing page. Compiled by API Evangelist on 2026-05-04; confirm before you rely on a figure. A free plan or tier is listed.

Plan	Price
Free freemium	Free
Professional paid	Free
Enterprise enterprise	—

Plan details, limits and sources →

Rate limits

Free Tier Default: 10 requests per minute
Free Tier Monthly Quota: 1000 requests per month
Professional Tier Default: 100 requests per minute

Compiled by API Evangelist, not yet checked against Apache Samza's documentation. All 5 limits →

Pricing Plans 1

Published pricing tiers and plan structures.

Apache Samza Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Apache Samza Rate Limits

5 limits

RATE LIMITS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Apache Samza

SLA

FinOps 1

Cost, billing, and metering signals for API financial operations.

Apache Samza Finops

FINOPS

Features 6

Notable capabilities this provider offers.

Kafka Integration

Native Apache Kafka consumer/producer for stream processing

YARN Execution

Runs on Apache YARN for resource management and fault tolerance

Stateful Processing

Local state stores with RocksDB for low-latency stateful computations

Exactly-Once Processing

Transactional state stores for exactly-once semantics

Flexible Deployment

Run on YARN, Kubernetes, or standalone

High Level API

Fluent API and SQL support for stream transformations

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Apache Samza Context

8 classes · 17 properties

JSON-LD

Spectral Rules 2

Spectral governance rulesets for linting and validating these APIs.

Apache Samza — jsonschema rules

5 rules · 3 warnings 2 info

SPECTRAL

Apache Samza API Rules

13 rules · 5 errors 7 warnings 1 info

SPECTRAL

JSON Schema 8

Standalone JSON Schema definitions for this provider's data models.

CheckpointList

Recommended x-agentic-access execution contracts for AI agents.

Apache Samza Agentic Access

6 operations · 2 acting · 1 human-in-the-loop

6 operations · 2 acting

AGENTIC

Use Cases 4

What developers build with this provider.

Event Stream Processing

Real-time processing of Kafka event streams

Stateful Aggregations

Windowed aggregations over streaming data

Stream Joins

Join multiple Kafka streams for enrichment

Change Data Capture

Process CDC events from databases in real time

Integrations 4

Pre-built integrations with other platforms and tools.

Apache Kafka

Primary messaging system for Samza input and output streams

Apache YARN

Resource management and job scheduling on Hadoop

Apache Hadoop

HDFS integration for checkpoint storage

RocksDB

Embedded state store for local stateful processing

Resources

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

SpectralRules

SpectralRules

Vocabulary

Vocabulary

JSONLD

JSONLD

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 2

Authentication, authorization, and security posture

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

RateLimits

RateLimits

Commercial 2

Pricing, plans, and the legal terms of use

Plans

Plans

FinOps

FinOps

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: apache-samza
name: Apache Samza
description: Apache Samza is a distributed stream processing framework that provides a simple API for building stateful stream
  processing applications. It integrates with Apache Kafka for messaging and supports both stream and batch processing.
type: Index
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - openapi
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Freemium
  confidence: low
  source:
  - plans
  - security
  generated: '2026-11-06'
  method: derived
position: Consuming
access: 3rd-Party
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/apache-samza.png
tags:
- Big Data
- Hadoop
- Kafka
- Stream Processing
- Streaming
- Apache
- Open Source
tags_raw:
- Big Data
- Hadoop
- Kafka
- Stream Processing
- Streaming
- Apache
- Open Source
- Open-Source
created: '2026-03-16'
modified: '2026-05-19'
url: https://raw.githubusercontent.com/api-evangelist/apache-samza/refs/heads/main/apis.yml
specificationVersion: '0.23'
apis:
- aid: apache-samza:apache-samza-checkpoints-api
  name: Apache Samza Checkpoints API
  description: The Checkpoints API from Apache Samza — 1 operation(s) for checkpoints.
  humanURL: https://samza.apache.org/learn/documentation/latest/
  tags:
  - Checkpoints
  properties:
  - type: OpenAPI
    url: openapi/apache-samza-checkpoints-api-openapi.yml
  - type: Documentation
    url: https://samza.apache.org/learn/documentation/latest/
  - type: Documentation
    url: https://samza.apache.org/learn/documentation/
- aid: apache-samza:apache-samza-jobs-api
  name: Apache Samza Jobs API
  description: The Jobs API from Apache Samza — 4 operation(s) for jobs.
  humanURL: https://samza.apache.org/learn/documentation/latest/
  tags:
  - Job
  tags_raw:
  - Jobs
  properties:
  - type: OpenAPI
    url: openapi/apache-samza-jobs-api-openapi.yml
  - type: Documentation
    url: https://samza.apache.org/learn/documentation/latest/
  - type: Documentation
    url: https://samza.apache.org/learn/documentation/
- aid: apache-samza:apache-samza-tasks-api
  name: Apache Samza Tasks API
  description: The Tasks API from Apache Samza — 1 operation(s) for tasks.
  humanURL: https://samza.apache.org/learn/documentation/latest/
  tags:
  - Task
  tags_raw:
  - Tasks
  properties:
  - type: OpenAPI
    url: openapi/apache-samza-tasks-api-openapi.yml
  - type: Documentation
    url: https://samza.apache.org/learn/documentation/latest/
  - type: Documentation
    url: https://samza.apache.org/learn/documentation/
maintainers:
- FN: Kin Lane
  email: info@apievangelist.com
common:
- type: Plans
  url: plans/apache-samza-plans-pricing.yml
- type: RateLimits
  url: rate-limits/apache-samza-rate-limits.yml
- type: FinOps
  url: finops/apache-samza-finops.yml
- type: Website
  url: https://www.apache.org/
- type: AgenticAccess
  url: agentic-access/apache-samza-agentic-access.yml
- type: VulnerabilityDisclosure
  url: security/apache-samza-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/apache-samza-domain-security.yml
- type: GitHubOrganization
  url: https://github.com/apache/samza
- type: Documentation
  url: https://samza.apache.org/
- type: SpectralRules
  url: rules/apache-samza-spectral-rules.yml
- type: Vocabulary
  url: vocabulary/apache-samza-vocabulary.yaml
- type: JSONLD
  url: json-ld/apache-samza-context.jsonld
- type: Features
  data:
  - name: Kafka Integration
    description: Native Apache Kafka consumer/producer for stream processing
  - name: YARN Execution
    description: Runs on Apache YARN for resource management and fault tolerance
  - name: Stateful Processing
    description: Local state stores with RocksDB for low-latency stateful computations
  - name: Exactly-Once Processing
    description: Transactional state stores for exactly-once semantics
  - name: Flexible Deployment
    description: Run on YARN, Kubernetes, or standalone
  - name: High Level API
    description: Fluent API and SQL support for stream transformations
- type: UseCases
  data:
  - name: Event Stream Processing
    description: Real-time processing of Kafka event streams
  - name: Stateful Aggregations
    description: Windowed aggregations over streaming data
  - name: Stream Joins
    description: Join multiple Kafka streams for enrichment
  - name: Change Data Capture
    description: Process CDC events from databases in real time
- type: Integrations
  data:
  - name: Apache Kafka
    description: Primary messaging system for Samza input and output streams
  - name: Apache YARN
    description: Resource management and job scheduling on Hadoop
  - name: Apache Hadoop
    description: HDFS integration for checkpoint storage
  - name: RocksDB
    description: Embedded state store for local stateful processing
- type: Blog
  url: https://samza.apache.org/blog/

Apache Samza API — frequently asked questions

Does Apache Samza have an API?

Yes. APIs.io lists 3 APIs from Apache Samza, including Apache Samza Checkpoints API, Apache Samza Jobs API and Apache Samza Tasks API.

Is there an OpenAPI specification for the Apache Samza API?

Yes. APIs.io indexes 3 OpenAPI specifications for Apache Samza, each linked for download from this page.

How much does the Apache Samza API cost?

APIs.io lists 3 pricing plans for Apache Samza, with each plan's price, limits and inclusions under Pricing on this page.

Is the Apache Samza API ready for AI agents?

Apache Samza has a Kin Score of 27.2 out of 100 (thin) and an Agent Readiness score of 17.2 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/apache-samza"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/apache-samza/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/apache-samza/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.