Jitsu

Jitsu is an open-source, real-time event data pipeline and customer data platform (a Segment alternative). It collects events from websites, apps, and servers and streams them to data warehouses and other destinations. Jitsu is available as MIT-licensed self-hosted software (github.com/jitsucom/jitsu) and as a managed Jitsu Cloud (use.jitsu.com); both expose the same HTTP event ingestion API authenticated with a Write Key.

Jitsu publishes 2 API contracts indexed on the APIs.io network: Batch API and Ingestion API. Tagged areas include Event Data, CDP, Data Pipeline, Analytics, and Open Source.

The Jitsu catalog on APIs.io includes 1 Spectral governance ruleset.

Jitsu’s developer surface includes engineering blog, authentication, documentation, and 10 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

30.2/100 thin ▬ flat Agent 44/100 agent ready Front door AI 2/6 trace Heartbeat 92/100 alive saas Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

AccessFreemiumSelf serve⚡ Free to try

1 published contract 1 MCP Servers

Event Data CDP Data Pipeline Analytics Open Source Ingestion Customer Data Platform

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Product Telemetry & Experimentation Management

BC-4280

BatchIngestion

POST /v1/batch POST /api/s/s2s/{type}

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 30.2/100 · thin

Contract Quality 9.4 / 19

Developer Ergonomics 4.8 / 15

Access Clarity 1.9 / 15

Operational Transparency 1.2 / 10

Contract Governance 1.2 / 9

Discoverability 5.1 / 8

Regulatory Posture 1.6 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 44/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 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 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 6 / 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/jitsu/"><img src="https://apis.io/badge/jitsu/card.svg" alt="Jitsu 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):

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) Ask about this →
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link Ask about this →
Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks Ask about this →
Documented Reversibility +6 pts — a reversal operation in the contract, graded up when a window is documented too Ask about this →

5 more unmet checks in the Agent Readiness table above.

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

Access Clarity scores 12.8 — up to +17.4 composite points Ask about this →
Developer Ergonomics scores 32.1 — up to +13.6 composite points Ask about this →
Contract Quality scores 50.2 — up to +12.5 composite points Ask about this →

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.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

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/jitsu/apis.yml: open an issue on github.com/api-evangelist/jitsu 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 →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Data Integration (ELT connectors and data governance)	builds-on	17.2 (thin)	1	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 4

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.

Model Context Protocol (MCP)

measured — observed by APIs.io (verified)

OAuth 2.0 Protected Resource Metadata

measured — observed by APIs.io (verified)

Dynamic Client Registration

measured — observed by APIs.io (published)

OpenAPI

measured — observed by APIs.io (published)

APIs 2

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

Jitsu Batch API

The Batch API from Jitsu — 2 operation(s) for batch.

Jitsu Ingestion API

The Ingestion API from Jitsu — 2 operation(s) for ingestion.

Open Collections 3

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

Jitsu Event Ingestion Batch API

OPEN COLLECTION

Jitsu Event Batch Ingestion API

OPEN COLLECTION

Jitsu Event Ingestion API

OPEN COLLECTION

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Jitsu MCP Server

Remote MCP server at use.jitsu.com over HTTP.

MCP SERVER

Jitsu API pricing

Not yet checked against Jitsu's own pricing page. Compiled by API Evangelist on 2026-06-21 from jitsu.com/pricing; confirm before you rely on a figure. A free plan or tier is listed.

Plan	Price
Open Source (Self-Hosted) free	—
Free free	—
Business paid	—
Enterprise enterprise	—

Plan details, limits and sources →

Rate limits

Active Events Per Month (Cloud): plan-based (200k Free / 2M Business / custom Enterprise) events
Bulk Request Size: ~50,000 events per bulk HTTP request events
Ingestion Throughput (Self-Hosted): bounded by provisioned infrastructure events

Compiled by API Evangelist, not yet checked against Jitsu's documentation. All 4 limits →

Pricing Plans 1

Published pricing tiers and plan structures.

Jitsu Plans Pricing

4 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Jitsu Rate Limits

4 limits

RATE LIMITS

Compliance 1

Attestations the provider states (SOC 2, ISO 27001 and others), quoted from its own trust page. APIs.io verifies none of them.

Jitsu

2 quoted statements, read from Jitsu's own page on 2026-11-09.

COMPLIANCE

FinOps 1

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

Jitsu Finops

FINOPS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

Jitsu API Rules

65 rules · 63 error-severity 1 warn-severity 1 info-severity

SPECTRAL

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Jitsu Authentication

apiKey/http · 2 schemes

SECURITY

Jitsu Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Jitsu Trust Center

SOC 2, GDPR

SECURITY

Agentic Access (API Evangelist recommendations) 1

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

Jitsu Agentic Access

4 operations · 4 acting

AGENTIC

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

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 3

Authentication, authorization, and security posture

TrustCenter

TrustCenter

DomainSecurity

DomainSecurity

Authentication

Authentication

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 3

The organization behind the API

Blog

Blog

LinkedIn

Website

Website

Other 1

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Source (apis.yml)

aid: jitsu
url: https://raw.githubusercontent.com/api-evangelist/jitsu/refs/heads/main/apis.yml
name: Jitsu
kind: company
description: Jitsu is an open-source, real-time event data pipeline and customer data platform (a Segment alternative). It
  collects events from websites, apps, and servers and streams them to data warehouses and other destinations. Jitsu is available
  as MIT-licensed self-hosted software (github.com/jitsucom/jitsu) and as a managed Jitsu Cloud (use.jitsu.com); both expose
  the same HTTP event ingestion API authenticated with a Write Key.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Freemium · Self-serve signup
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-13'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/jitsu.png
tags:
- Event Data
- CDP
- Data Pipeline
- Analytics
- Open Source
- Ingestion
- Customer Data Platform
tags_raw:
- Event Data
- CDP
- Data Pipeline
- Analytics
- Open Source
- Ingestion
- Open-Source
- Customer Data Platform
created: '2026-06-21'
modified: '2026-10-06'
specificationVersion: '0.23'
apis:
- aid: jitsu:jitsu-batch-api
  name: Jitsu Batch API
  description: The Batch API from Jitsu — 2 operation(s) for batch.
  humanURL: https://jitsu.com/docs/sending-data/http
  baseURL: https://use.jitsu.com
  tags:
  - Batch
  properties:
  - type: OpenAPI
    url: openapi/jitsu-batch-api-openapi.yml
  - type: Documentation
    url: https://jitsu.com/docs/sending-data/http
  - type: APIReference
    url: https://jitsu.com/docs/sending-data/http
  - type: PostmanCollection
    url: collections/jitsu.postman_collection.json
  - type: OpenCollection
    url: collections/jitsu.opencollection.json
  - type: Documentation
    url: https://jitsu.com/docs
- aid: jitsu:jitsu-ingestion-api
  name: Jitsu Ingestion API
  description: The Ingestion API from Jitsu — 2 operation(s) for ingestion.
  humanURL: https://jitsu.com/docs/sending-data/http
  baseURL: https://use.jitsu.com
  tags:
  - Ingestion
  properties:
  - type: OpenAPI
    url: openapi/jitsu-ingestion-api-openapi.yml
  - type: Documentation
    url: https://jitsu.com/docs/sending-data/http
  - type: APIReference
    url: https://jitsu.com/docs/sending-data/http
  - type: PostmanCollection
    url: collections/jitsu.postman_collection.json
  - type: OpenCollection
    url: collections/jitsu.opencollection.json
  - type: Documentation
    url: https://jitsu.com/docs
common:
- url: https://jitsu.com/blog
  type: Blog
- type: CapabilityMap
  url: capabilities/jitsu-capability-edges.yml
  name: Jitsu Business Capability Map
- type: AgenticAccess
  url: agentic-access/jitsu-agentic-access.yml
- type: TrustCenter
  url: security/jitsu-trust-center.yml
- type: DomainSecurity
  url: security/jitsu-domain-security.yml
- type: Authentication
  url: authentication/jitsu-authentication.yml
- type: GitHubOrganization
  url: https://github.com/jitsucom
- type: LinkedIn
  url: https://www.linkedin.com/company/jitsu-com
- type: Website
  url: https://jitsu.com/
- type: Documentation
  url: https://jitsu.com/docs
- type: Plans
  url: plans/jitsu-plans-pricing.yml
- type: RateLimits
  url: rate-limits/jitsu-rate-limits.yml
- type: FinOps
  url: finops/jitsu-finops.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Jitsu API — frequently asked questions

Does Jitsu have an API?

Yes. APIs.io lists 2 APIs from Jitsu, including Jitsu Batch API and Jitsu Ingestion API.

Is there an OpenAPI specification for the Jitsu API?

Yes. APIs.io indexes 2 OpenAPI specifications for Jitsu, each linked for download from this page.

How do I authenticate with the Jitsu API?

Jitsu documents its authentication (apiKey/http · 2 schemes). The details are profiled on APIs.io as Jitsu Authentication.

How much does the Jitsu API cost?

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

Does Jitsu have an MCP server?

Yes. APIs.io lists 1 MCP server for Jitsu: Remote MCP server at use.jitsu.com over HTTP.

Is the Jitsu API ready for AI agents?

Jitsu has a Kin Score of 30.2 out of 100 (thin) and an Agent Readiness score of 43.9 (agent-ready), scored by API Evangelist on 2026-11-13.

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/jitsu"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/jitsu/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.