Regrid Parcel API

Name: Regrid Parcel API
Brand: Regrid Parcel API
Availability: InStock

✓ Official Vendor SpecMaps GeolocationGeocodingapiKey8 EndpointsREST

For Agents

Programmatically search parcels by coordinates, search parcels by address. Covers 8 operations with apiKey authentication.

Use for: I need to parcels by coordinates, I want to parcels by address, Search for parcels by assessor parcel number, Find all parcels by owner name

Not supported: Does not handle payments, communications, or crm - use for maps and geolocation only.

Regrid Parcel API providing nationwide parcel data searches by point/coordinates, address, assessor parcel number (APN), owner name, field queries, and area geometry. Returns GeoJSON FeatureCollections with parcel records. The API exposes 8 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Install Jentic One Beta

Connect the Regrid Parcel API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Regrid Parcel API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fregrid.com%2Fregrid" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fregrid.com%2Fregrid" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Regrid Parcel API.

Search parcels by coordinates

Query parcels by schema fields (POST)

Integrate Regrid Parcel API into automated workflows

Query and filter Regrid Parcel API records by parameters

Monitor Regrid Parcel API operational status and events

GET STARTED

Start building with Regrid Parcel API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Regrid Parcel API for, with concrete tasks.

★ Maps and Geolocation Operations

Use the Regrid Parcel API to perform maps geolocation operations programmatically. The API provides 8 endpoints covering core functionality including search parcels by coordinates, search parcels by address, search parcels by assessor parcel number.

Call GET /parcels/point to search parcels by coordinates

Automated Parcels Management

Automate parcels operations by combining multiple Regrid Parcel API endpoints. Agents can search parcels by address and then search parcels by assessor parcel number in a single workflow.

Call GET /parcels/address to search parcels by address, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Regrid Parcel API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Search Jentic for 'search parcels by coordinates', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

8 endpoints — regrid parcel api providing nationwide parcel data searches by point/coordinates, address, assessor parcel number (apn), owner name, field queries, and area geometry.

METHOD

PATH

DESCRIPTION

GET

/parcels/point

Search parcels by coordinates

GET

/parcels/address

Search parcels by address

GET

/parcels/apn

Search parcels by Assessor Parcel Number

GET

/parcels/owner

Search parcels by owner name

POST

/parcels/query

Query parcels by schema fields (POST)

GET

/parcels/query

Query parcels by schema fields (US)

POST

/parcels/area

Search parcels in area (POST with GeoJSON)

GET

/parcels/area

Search parcels in a geographic area

GET

/parcels/point

Search parcels by coordinates

GET

/parcels/address

Search parcels by address

GET

/parcels/apn

Search parcels by Assessor Parcel Number

GET

/parcels/owner

Search parcels by owner name

POST

/parcels/query

Query parcels by schema fields (POST)

GET

/parcels/query

Query parcels by schema fields (US)

POST

/parcels/area

Search parcels in area (POST with GeoJSON)

GET

/parcels/area

Search parcels in a geographic area

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Regrid Parcel API by hand means appending your token as a query parameter on every call and building your own retry handling against the app.regrid.com host. Through Jentic you install once, import the Regrid Parcel API from the API Directory, store the token once, and your agent calls it.

Permission scoping

The Regrid Parcel API exposes parcel lookup endpoints for point, address, apn, owner, query, and area with parameters in the query and body, so scoping is by operation: limit the agent to the operations it needs, such as looking up parcels by coordinates or address, rather than to a single record. Every operation the agent can run is one you have chosen to allow.

Credential isolation

Your Regrid Parcel API token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'search parcels by coordinates' or 'look up a parcel by address', and Jentic returns the matching Regrid Parcel API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Regrid Parcel API through Jentic.

What authentication does the Regrid Parcel API use?

The Regrid Parcel API uses an API key passed in the `token` query. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I search parcels by coordinates with the Regrid Parcel API?

Yes. Use the GET /parcels/point endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Regrid Parcel API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I search parcels by coordinates through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'search parcels by coordinates'. Jentic returns the matching Regrid Parcel API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Regrid Parcel API have?

The Regrid Parcel API exposes 8 endpoints covering parcels operations.

Can I limit what my agent is allowed to do with the Regrid Parcel API?

Yes. Because you run Jentic One yourself, your own rules decide which Regrid Parcel API operations the agent may call and which stored token it uses. Since the API scopes access by operation, you can allow only the lookups the agent needs, such as searching parcels by coordinates or by address, while withholding owner, APN, field query, or area operations. Every operation the agent can run is one you have chosen to permit.

Regrid Parcel API

Connect the Regrid Parcel API to your agent

Capabilities

Start building with Regrid Parcel API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs