If you've been searching for a "Sapling API," you've probably noticed something unusual: unlike Grammarly or ProWritingAid, Sapling actually has one. The Edits API at api.sapling.ai accepts text and returns structured grammar corrections — the exact thing developers keep discovering the big consumer assistants won't sell them.
That makes Sapling the closest architectural match to what we build at AmberPen, so this article is an honest look at both. We benchmark grammar engines on public datasets and publish the results, and Sapling is one of the strongest competitors we've measured. Where it wins, we'll say so. Where it doesn't, we'll show the numbers.
What the Sapling API actually is
Sapling's developer offering centers on a handful of REST endpoints, the core one being Edits (POST /api/v1/edits). You send text and an API key; you get back a list of edits, each with a start offset, end offset, replacement string, and an error type. That is the right shape for building your own UI — underlines, hover cards, accept/reject buttons — which is why Sapling shows up on the shortlist for every team that outgrows embedding someone else's widget.
Around Edits, Sapling also offers autocomplete, rephrasing, tone scoring, and an AI-content detector. The API is documented, the Python SDK on GitHub is maintained, and there's a free tier for low-volume evaluation. As developer experiences go in this category, it's one of the real ones.
The honest caveats come in three places: correction quality on noisy text, latency, and per-character pricing at volume.
Correction quality: strong on fluency, looser on web text
We measure every engine we can against two public benchmarks: JFLEG (fluency on learner English, scored with GLEU) and CWEB (grammar errors on real web text, scored with precision/recall against human annotations). Full methodology and reproducible scripts are on our benchmarks page.
Sapling's July 2026 numbers, run over identical inputs:
| Metric | Sapling | AmberPen |
|---|---|---|
| JFLEG fluency (GLEU, 754 sentences) | 0.470 | 0.561 |
| CWEB precision (6,845 sentences) | 23.6% | 37.4% |
| CWEB recall | 49.1% | 65.5% |
| CWEB ERRANT F0.5 | 26.3 | 40.9 |
Read the precision row carefully: on CWEB, 23.6% precision means more than three of every four edits Sapling proposed didn't match a human annotation. On learner-style fluency text (JFLEG) Sapling is the strongest of the non-AmberPen engines we tested — a genuine strength — but on messy production text (web pages, user-generated content, support tickets) the suggestion stream gets noisy. If your users will see every proposed edit in an as-you-type UI, that noise is user experience.
To be fair: Sapling's recall of 49.1% is solid — better than LanguageTool's 18.3% and Harper's 13.8% on the same corpus. This is a real neural engine, not a rules wrapper. The question is whether the precision/latency/price trade-off fits your product.
Latency: fine for batch, noticeable as-you-type
Median per-sentence latency over our benchmark runs:
| Latency | Sapling | AmberPen |
|---|---|---|
| p50 | 620 ms | 217 ms |
| p95 | 1,086 ms | 1,024 ms |
| p99 | 1,646 ms | 1,413 ms |
Sapling's median is roughly 3× AmberPen's. For a nightly batch job over documents, 620 ms is irrelevant. For checking while someone types — where the median request is the experience — it's the difference between suggestions that feel instant and suggestions that arrive after the next keystroke. Our streaming architecture post covers why we optimized so hard for the median case.
Pricing: per-character, with a language multiplier
Sapling bills the Edits API per character with volume tiers. Rates for English as of July 2026 (check sapling.ai/docs/api/pricing for current numbers):
- $0.025 per 1K characters at entry ($25 per 1M)
- $0.020 per 1K from 10M characters
- $0.015 per 1K from 50M characters
- Chinese, Japanese, and Korean are billed at 2.5× the English rate
AmberPen is a base subscription with included characters and flat overage: Starter €5/month with 500K characters included (then €9 per 1M), Pro €49/month with 9M included (then €6 per 1M), no per-language multiplier.
What that means in practice, before currency conversion:
| Characters / month | Sapling | AmberPen |
|---|---|---|
| 1M | $25 | €9.50 (Starter) |
| 5M | $125 | €49 (Pro) |
| 10M | $250 | €55 (Pro + overage) |
| 50M | $1,050 | €295 (Pro + overage, or Scale) |
At low volumes the difference is a coffee; at 10M+ characters it's a line item. If you're projecting volume, our grammar checker API pricing article models the billing math across seven APIs, including per-token LLM options.
Where Sapling genuinely wins
Two honest wins worth stating:
- The API exists and is self-serve. In a category where Grammarly offers scores-but-not-corrections and ProWritingAid offers no public correction endpoint at all, Sapling sells the actual thing: text in, structured edits out. If you're evaluating today, you can have a key in minutes.
- The feature surface is broad. Autocomplete, rephrasing, tone, AI detection, plus turnkey SDKs and CRM integrations. If your roadmap needs more than grammar correction — say, suggested replies for a support console — one vendor covering several language features has real integration value.
The two-minute test
Benchmark tables are a starting point, not a decision. The only evaluation that matters is your own text: your product's error distribution, your users' tolerance for false positives, your latency budget.
Both APIs make this easy. Sapling has a free tier; AmberPen's Starter plan is €5/month with 500K characters included, and a free test key returns real corrections in about two minutes. Send both APIs the same fifty sentences from your actual product and count the edits you'd be proud to render.
If you want the head-to-head numbers first, the AmberPen vs Sapling comparison has the full benchmark tables, and the grammar checker API roundup puts both in context against LanguageTool, GrammarBot, Harper, and the rest of the category.