The Easting API
Send a recorded document, get back every course with the words it was read from, a recomputed traverse, and a verdict that says whether to trust it. Integrating is an afternoon.
Most document-AI APIs return an answer. This one returns an answer and a
judgement about the answer, because on a boundary a confident wrong
number is worse than no number. The model transcribes and deterministic
code decides: the traverse is recomputed from the extracted bearings and
distances, closure is measured, and the computed area is compared
against the acreage the document states. Two independent signals have to
agree before anything is called PASS.
It reads deeds, recorded easements, plats and utility as-builts. One
route for a single document (/v1/extract), one that submits
and polls for anything that might run long (/v1/extracts),
and a batch endpoint for volume (/v1/batches). Out the
other side: the extraction itself, a signed certificate, DXF and
GeoPackage. Built for pipelines reading county records at volume, and
for anyone who would rather call an endpoint than click.
# One document, synchronously. Good for a small deed and a first try.
curl -X POST https://api.easting.ai/v1/extract \
-H "authorization: Bearer $EASTING_KEY" \
-H "content-type: application/pdf" \
-H "x-document-name: forsyth_3210_350.pdf" \
--data-binary @deed.pdf
The documentation
The working documentation lives at docs.easting.ai:
- The guide — authentication, and choosing between sync, async and batch.
- The reference — every route and field, generated from the schema the server validates against.
- Errors — every type the service returns, and what to do about each.
- Artifacts — the certificate, DXF and GeoPackage, the signature on them, and the serialization rule that keeps it verifying.
- Concepts — what PASS, REVIEW and FAIL mean, and the checks that earn them.
openapi.json is stable enough to generate a client from, and an interactive console lives at api.easting.ai/docs.
Pricing
Metered is $0.50 a document: nothing included, no
seats, card on file, billed monthly from usage. It slopes with volume,
to $0.35 above 2,000 documents a month and $0.25 above 10,000 through
/v1/batches. That is per document, not per page — a
recorded instrument runs a median of three pages in our evaluation
corpus, so per-page credit prices are charged several times over on
every one. If a human is reviewing the results, a
$10 seat with 50 documents a month is almost
certainly cheaper.
Start free: signup takes an email and no card, and the key it mints carries three documents that never expire.
Reading documents by hand in QGIS instead? The plugin and the browser app sit on this same API.