How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Kateeva

Kateeva is a Silicon Valley capital-equipment company that builds inkjet printing systems for manufacturing advanced displays. It was co-founded in 2008 by Conor Madigan, PhD, Valerie Gassend, PhD, and Gerry Chen, PhD, on the conviction that precision inkjet deposition could make OLED displays mass-producible at cost. The company introduced its YIELDjet platform in 2013 — the display industry's first inkjet equipment solution for depositing the organic thin film encapsulation (TFE) layer of an OLED panel — and shipped the first commercial YIELDjet FLEX system a year later, which became the market-leading tool for flexible mobile OLED mass production. Its current product line is the YIELDjet Lassen, Jarvis, Tioga and Kuna printers, spanning substrate sizes and applications from TFE to OLED RGB pixel deposition and microlens planarization. Kateeva moved its global headquarters to Newark, California in 2015 and operates in China, Korea, Japan and Taiwan; it raised roughly $200 million through a 2016 Series E backed by BOE, TCL Capital, Redview Capital, Samsung Venture Investment, Sigma Partners, Spark Capital, Madrone Capital Partners, DBL Partners and Veeco. Kateeva sells machines to display panel makers, not software: it publishes no developer program, no developer portal, no SDKs and no API documentation of any kind. The only machine-readable interface it exposes is the WordPress REST content API behind its corporate website at kateeva.com, which is captured here for discovery purposes and is anonymously readable but read-only.

agent ready

Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.

Kin Score

API Evangelist profiles Kateeva the way a machine reads it — 13 machine-readable artifacts across 8 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 — Kateeva scores 33.0/100 (thin), with a separate agent-readiness read of 48/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 Kin Score How this is scored →
scored 2026-08-24 · rubric v0.12.1
Composite quality — 33.0/100 · thin
Contract Quality 12.8 / 25
Developer Ergonomics 4.3 / 20
Access Clarity 4.2 / 20
Operational Transparency 0.0 / 13
Contract Governance 3.6 / 12
Discoverability 8.2 / 10
Agent readiness — 48/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 10 / 10
Documented Reversibility 0 / 6
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8.0 / 8
Request/Response Examples documented 1.8 / 7
Rate-Limit Signaling documented 3.5 / 7
Typed Event Surface 0 / 6
Agent Skills 5 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Kateeva Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from Kateeva's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.

<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/kateeva/"
   title="Kateeva on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/kateeva.svg"
       alt="Kateeva Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile Kateeva

Each block below is one kind of artifact we hold for Kateeva. 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 8

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.

Kateeva Posts API

Public, unauthenticated read access to the Kateeva newsroom archive via the WordPress core REST API — press releases, in-the-news coverage, event notices and the Kateeva Blog. V...

Kateeva Pages API

Public, unauthenticated read access to the static pages of kateeva.com — Company, About, Leadership, History & Awards, Regions, Sustainability, Solutions, Technology, YIELDjet P...

Kateeva Media API

Public, unauthenticated read access to the media library behind kateeva.com — YIELDjet product photography, facility and event imagery, leadership headshots and press assets wit...

Kateeva Taxonomy API

Public, unauthenticated read access to the classification vocabularies behind the kateeva.com newsroom — the eight post categories (Press releases, In the news, Kateeva Blog, Sp...

Kateeva Search API

Public, unauthenticated cross-content search over kateeva.com — the newsroom archive and the static pages — returning lightweight id / title / url / type / subtype records. Veri...

Kateeva Discovery API

Public, unauthenticated discovery metadata for kateeva.com — the self-describing route index (271 routes across 17 namespaces at capture), the registered content types and taxon...

Kateeva oEmbed API

Public oEmbed 1.0 provider endpoint for kateeva.com URLs, returning embeddable rich metadata — title, author, provider, thumbnail and iframe HTML — for any post or page on the s...

Kateeva SEO Metadata API

Public Yoast SEO head endpoint returning the rendered head metadata and its parsed JSON-LD schema.org graph for any kateeva.com URL — a structured-data view of every page withou...

Scroll within the panel for all 8 ·

Pricing 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 things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.

Published pricing tiers and plan structures.

Kateeva Plans Pricing

0 plans

PLANS

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.

Kateeva Rate Limits

0 limits

RATE LIMITS

Security Posture 2

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.

Kateeva Authentication

0 schemes

SECURITY

Kateeva Domain Security

TLSv1.2 · DMARC

SECURITY

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.

Kateeva Agentic Access

21 operations

21 operations · 0 acting

AGENTIC

Resources

Every other property we hold for Kateeva — 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.

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

← All providers · Data indexed from github.com/api-evangelist/kateeva · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of Kateeva, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.