canonical: https://jentic.com/apis/regrid.com/regrid

# Regrid Parcel API

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.

## For AI agents

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

## Scope

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

## Capabilities

- 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

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

| 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 |

## Key resources

- **Parcels** — Operations for parcels

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Here** — Alternative maps geolocation API
- **Tomtom** — Alternative maps geolocation API
- **Googleapis** — Complementary maps geolocation API

## FAQ

### 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.