Skip to content
easting.aidocs

Search is only available in production builds. Try building and previewing the site to test it out locally.

Suggest where an extraction's tracts sit

POST
/v1/locate
curl --request POST \
  --url https://example.com/v1/locate \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "extraction": {}, "source": "plss_corner" }'

Fill each tract’s location block, and re-sign what comes back.

A deed defines shape, not position. Today the one source that needs no input from you is plss_corner: when a description commences at a section or aliquot corner, the fabric resolves that corner and the tie chain walks to the point of beginning. Most descriptions name no such corner, and a response with every location null is the ordinary answer rather than a failure.

A suggestion, never a placement. The block carries REVIEW even when every check agreed, and pob comes back null whenever the traverse failed its own containment test, with reasons naming the corner that was tried. Confirming a position stays the operator’s click.

Stateless and free, like /v1/dxf and /v1/certificate: you post back the response you already hold, nothing here stores it, and the document was paid for once already.

The signature is the point of doing this server-side. The posted attestation is verified first, every location block that arrived is discarded before anything is computed, and only what this server worked out is signed into the response. Otherwise a coordinate typed into a text editor could ride a valid signature onto a certificate.

Authorizations

Section titled “Authorizations”

Request Bodyrequired

Section titled “Request Bodyrequired”
Media typeapplication/json
LocateRequest

A request to locate the tracts of an extraction you already hold.

object
extraction
required
Extraction

A /v1/extract response, exactly as the API returned it. Its attestation is verified before anything is computed, and any location block it carries is discarded rather than trusted.

object
key
additional properties
any
source
Source

Which method to try. “plss_corner” needs no other input.

string
default: plss_corner

Responses

Section titled “Responses”

200

Section titled “200”

Successful Response

Media typeapplication/json
LocateResponse

The posted extraction with location blocks filled, re-signed.

object
extraction
required
Extraction
object
key
additional properties
any
located
required
Located

How many tracts came back carrying an actual position. Zero is an ordinary answer: most descriptions name no corner the fabric can bind to.

integer
Examplegenerated
{
  "extraction": {},
  "located": 1
}

401

Section titled “401”

Missing, unknown, or revoked API key

Media typeapplication/json
ErrorResponse
object
error
required
ErrorDetail
object
type
required
Type
string
message
required
Message
string
key
additional properties
any
Example
{
  "error": {
    "documents_used": 200,
    "message": "Monthly document quota reached: 200 of 200 documents used this month. The cap resets on 2026-08-01. Email sales@easting.ai to raise it.",
    "monthly_cap": 200,
    "resets_on": "2026-08-01",
    "type": "quota_exceeded"
  }
}

422

Section titled “422”

The attestation is missing or does not match, or the requested source is not available

Media typeapplication/json
ErrorResponse
object
error
required
ErrorDetail
object
type
required
Type
string
message
required
Message
string
key
additional properties
any
Example
{
  "error": {
    "documents_used": 200,
    "message": "Monthly document quota reached: 200 of 200 documents used this month. The cap resets on 2026-08-01. Email sales@easting.ai to raise it.",
    "monthly_cap": 200,
    "resets_on": "2026-08-01",
    "type": "quota_exceeded"
  }
}