How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Regrid Metadata API

Coverage, usage, and data quality endpoints

Regrid Metadata API is one of 9 APIs that Regrid publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Metadata. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 4 operations across 4 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against a single base URL, https://app.regrid.com.

4 operations 4 paths 3 schemas 3 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://app.regrid.com
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

Regrid Metadata API declares 1 security scheme for authenticating requests. An API key is passed in the query as token (apiToken). By default, every request must be authenticated.

  • apiToken — API token obtained from your Regrid account profile

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 3 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Metadata 4

Coverage, usage, and data quality endpoints

GET
/verse
County Coverage Metadata
getVerse 1 param → 200401
GET
/usage
API Usage Summary
getUsage 1 param → 200401
GET
/usage/detailed
Detailed API Usage
getDetailedUsage 3 params → 200401
POST
/report
Submit Data Quality Report
submitDataReport body → 200400401

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are CountyCoverage (6 properties), UsageSummary (6 properties), DetailedUsage (1 property). Each schema is shown below with its type and property counts.

UsageSummary
object
API usage summary against plan limits
6 properties
CountyCoverage
object
County-level coverage metadata record
6 properties
DetailedUsage
object
Granular usage breakdown by endpoint and date
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

regrid-metadata-api-openapi.yml Raw ↑

Other APIs Regrid publishes across the network.

Regrid Tile API
Regrid Matched Building Footprints API
Regrid Standardized Zoning API
Regrid Daily Ownership Updates API
Regrid Parcel Query API
Regrid Parcel Search API
Regrid Schemas API
Regrid Typeahead API
Where this information came from

This is an independent, third-party profile of Regrid Metadata API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.