JSR-303

JSR-303 (Bean Validation) is a Java specification that defines a metadata model and API for JavaBean validation. It provides a standard way to define validation constraints on Java objects using annotations, enabling developers to enforce business rules and data integrity at the object level. Now standardized as Jakarta Validation, with version 3.1 released for Jakarta EE 11 and version 4.0 under development for Jakarta EE 12.

JSR-303 publishes 1 API on the APIs.io network. Tagged areas include Annotations, Bean Validation, Java, JSR-303, and Jakarta EE.

JSR-303’s developer surface includes documentation, engineering blog, and 3 more developer resources.

🌐 Visit website 📡 Source on GitHub

13.9/100 emerging ▬ flat Agent 3/100 human only Full breakdown ↓
scored 2026-09-14 · rubric v0.22.0

AccessFreemium

1 APIs

Annotations Bean Validation JavaJSR-303Jakarta EE Validation

Kin Score

Kin Score How this is scored →
scored 2026-09-14 · rubric v0.22.0

Composite quality — 13.9/100 · emerging

Contract Quality 0.0 / 25

Developer Ergonomics 3.8 / 20

Access Clarity 3.2 / 20

Operational Transparency 1.0 / 13

Contract Governance 0.0 / 12

Discoverability 5.9 / 10

Agent readiness — 3/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 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

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

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 github.com/api-evangelist/jsr-303: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

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

Jakarta Validation

The Jakarta Validation specification (originally JSR-303, then JSR-349, JSR-380) for defining and enforcing validation constraints on Java objects. Provides object level constra...

Pricing Plans 1

Published pricing tiers and plan structures.

Jsr 303 Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Jsr 303 Rate Limits

5 limits

RATE LIMITS

FinOps 1

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

Jsr 303 Finops

FINOPS

Security Posture 1

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

Jsr 303 Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

Specification

Specification

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: jsr-303
name: JSR-303
description: JSR-303 (Bean Validation) is a Java specification that defines a metadata model and API for JavaBean validation.
  It provides a standard way to define validation constraints on Java objects using annotations, enabling developers to enforce
  business rules and data integrity at the object level. Now standardized as Jakarta Validation, with version 3.1 released
  for Jakarta EE 11 and version 4.0 under development for Jakarta EE 12.
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:
  - none
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Freemium
  confidence: medium
  source:
  - plans
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/jsr-303.png
tags:
- Annotations
- Bean Validation
- Java
- JSR-303
- Jakarta EE
- Validation
url: https://raw.githubusercontent.com/api-evangelist/jsr-303/refs/heads/main/apis.yml
created: '2025-01-01'
modified: '2026-04-28'
specificationVersion: '0.23'
apis:
- aid: jsr-303:bean-validation
  name: Jakarta Validation
  description: The Jakarta Validation specification (originally JSR-303, then JSR-349, JSR-380) for defining and enforcing
    validation constraints on Java objects. Provides object level constraint declaration and validation facilities, plus a
    constraint metadata repository and query API. Current version 3.1 aligns with Jakarta EE 11.
  humanURL: https://jakarta.ee/specifications/bean-validation/
  tags:
  - Annotations
  - Bean Validation
  - Java
  - Jakarta EE
  properties:
  - type: Documentation
    url: https://jakarta.ee/specifications/bean-validation/
  - type: Specification
    url: https://jakarta.ee/specifications/bean-validation/3.1/
  - type: Reference
    url: https://beanvalidation.org/
common:
- type: DomainSecurity
  url: security/jsr-303-domain-security.yml
- type: Website
  url: https://jakarta.ee/specifications/bean-validation/
- type: Documentation
  url: https://jakarta.ee/specifications/bean-validation/
- type: Specification
  url: https://jakarta.ee/specifications/bean-validation/3.1/
- url: https://jakarta.ee/blogs/index.xml
  type: Blog
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

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/jsr-303"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/jsr-303/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

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.