Grammarly
Grammarly is an AI writing-assistance company whose enterprise developer platform exposes a set of REST APIs that bring Grammarly's writing intelligence into an organization's own applications, business-intelligence systems, and IT tooling. The Grammarly APIs cover writing-quality scoring, AI generated-content detection, plagiarism detection, communication analytics, and license management, all secured with OAuth 2.0 client credentials and scoped permissions against the base URL https://api.grammarly.com/ecosystem/api/. Certified Readability Score and Tone Analysis APIs are announced as coming soon. Grammarly was surfaced as a portfolio company of IVP.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Grammarly the way a machine reads it — 10 machine-readable artifacts across 5 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 — Grammarly scores 39.0/100 (thin), with a separate agent-readiness read of 16/100 (agent aware). 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
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Grammarly
Each block below is one kind of artifact we hold for Grammarly. 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 5
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.
Grammarly Analytics API
Programmatic access to Grammarly usage and communication-performance analytics for integration into business-intelligence systems.
Grammarly License Management API
Allocate and reallocate Grammarly licenses from software asset management / IT-governance tooling.
Grammarly Writing Score API
Score content on correctness, engagement, clarity, and delivery for organizational content governance (Beta).
Grammarly AI Detection API
Detect AI-generated content and help demonstrate original authorship (Beta).
Grammarly Plagiarism Detection API
Detect plagiarism against published sources to help teams produce original work (Beta).
Security Posture 4
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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for Grammarly — 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 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 8
Authentication, authorization, and security posture
Scroll within the panel for all 8 ·
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/grammarly · machine-readable index on apis.io