Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
42Maru website screenshot

42Maru

42Maru is a South Korean AI deep-tech company building a Deep Semantic TA (Text Analytics) and QA (Question Answering) platform that understands the true intent behind a user's question and returns a single answer drawn from large sets of unstructured documents. Its cognitive-search stack pairs document retrieval with Machine Reading Comprehension (MRC) and is delivered as enterprise chatbots (CHAT42), question-answering engines (QA42), natural-language processing (NL42), and the Platform42 SaaS. 42Maru ranked #1 on Stanford's SQuAD 2.0 machine-reading benchmark, won an AWS AI Challenge award, and is a Techstars London alumnus. It was added to the API Evangelist network from the Techstars portfolio and enriched from its public marketing site, GitHub organizations, and gitbook documentation; no public REST API, OpenAPI, first-party SDK, or /.well-known discovery surface was found — Platform42 API access appears to be provisioned per enterprise customer.

human only

Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.

Kin Score

API Evangelist profiles 42Maru the way a machine reads it — 1 machine-readable artifact, 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 — 42Maru scores 12.2/100 (minimal), with a separate agent-readiness read of 4/100 (human only). 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-07-27 · rubric v0.5
Composite quality — 12.2/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 4.8 / 20
Commercial Clarity 0.0 / 20
Operational Transparency 0.7 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Agent readiness — 4/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
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 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3

How we profile 42Maru

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

Security Posture 1

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.

42Maru Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

Every other property we hold for 42Maru — 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 1

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 1

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Company 2

The organization behind the API

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