Nearmap

Nearmap provides high‑resolution aerial imagery and property intelligence platforms, delivering up‑to‑date geospatial data, AI‑driven analytics, and APIs for developers to integrate mapping, analytics, and workflow applications across insurance, architecture, government, and other industries. Their services cover 97% of the U.S. population and 95% of U.S. buildings, with frequent updates and a suite of tools for property decision‑making.

Nearmap is listed with 2 APIs on the APIs.io network: Coverage API and Tiles API. Tagged areas include Company, Aerial Imagery, Geospatial, and Property Intelligence.

The Nearmap catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

Nearmap’s developer surface includes authentication, support, engineering blog, API reference, documentation, and 18 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

24.7/100 emerging ▼ -5.2 Agent 15/100 agent aware Heartbeat 64/100 slowing Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

2 APIs

Company Aerial Imagery Geospatial Property Intelligence

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 24.7/100 · emerging

Contract Quality 4.3 / 19

Developer Ergonomics 4.7 / 15

Access Clarity 0.8 / 15

Operational Transparency 2.1 / 10

Contract Governance 2.0 / 9

Discoverability 4.9 / 8

Regulatory Posture 2.8 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 15/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 0 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/nearmap/"><img src="https://apis.io/badge/nearmap/card.svg" alt="Nearmap on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)

12 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 22.9 — up to +19.3 composite points
Access Clarity scores 5.3 — up to +18.9 composite points
Developer Ergonomics scores 31.0 — up to +13.8 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/nearmap/apis.yml: open an issue on github.com/api-evangelist/nearmap to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

Nearmap Coverage API

The Coverage API from Nearmap — 6 operation(s) for coverage.

Nearmap Tiles API

The Tiles API from Nearmap — 2 operation(s) for tiles.

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Nearmap Context

7 classes · 7 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Nearmap API Rules

13 rules · 11 errors 1 warnings 1 info

SPECTRAL

JSON Schema 6

Standalone JSON Schema definitions for this provider's data models.

GetCoverageV2CoordZXYResponse

4 properties

JSON SCHEMA

GetCoverageV2PointCoordResponse

4 properties

JSON SCHEMA

GetCoverageV2PolyPolygonResponse

4 properties

JSON SCHEMA

GetCoverageV2V2IdBoundariesFileformatResponse

2 properties

JSON SCHEMA

PostCoverageV2AoiRequest

1 properties

JSON SCHEMA

PostCoverageV2AoiResponse

4 properties

JSON SCHEMA

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Nearmap Authentication

1 scheme

SECURITY

Nearmap Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Documentation 2

Reference material describing how the API behaves

APIReference

APIReference

Documentation

Documentation

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

WellKnown

WellKnown

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Spectral

JSONLD

Vocabulary

DataModel

Conformance

Build 3

SDKs, sample code, and the tooling you integrate with

SDKs

SDKs

Packages

Packages

GitHubOrganization

GitHubOrganization

Access & Security 3

Authentication, authorization, and security posture

Authentication

Authentication

SecurityTxt

SecurityTxt

DomainSecurity

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

Support

Support

StatusPage

StatusPage

Commercial 1

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

Newsroom

Newsroom

Blog

Blog

Website

Website

Other 2

Properties that don't map to a standard resource type

Hosts

Hosts

Vendors

Vendors

Source (apis.yml)

aid: nearmap
name: Nearmap
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  probe_state: unreadable
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://a-us.storyblok.com/f/1018982/2400x1260/3348039c64/nearmap-property-intelligence.png
description: Nearmap provides high‑resolution aerial imagery and property intelligence platforms, delivering up‑to‑date geospatial
  data, AI‑driven analytics, and APIs for developers to integrate mapping, analytics, and workflow applications across insurance,
  architecture, government, and other industries. Their services cover 97% of the U.S. population and 95% of U.S. buildings,
  with frequent updates and a suite of tools for property decision‑making.
url: https://raw.githubusercontent.com/api-evangelist/nearmap/refs/heads/main/apis.yml
x-type: company
x-source: harvest:tag-qc
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-13 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-10-13'
modified: '2026-10-13'
x-docs-platform: readme
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-17
tags:
- Company
- Aerial Imagery
- Geospatial
- Property Intelligence
tags_raw:
- Company
- AerialImagery
- Geospatial
- PropertyIntelligence
- APIs
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Spectral
  url: rules/nearmap-rules.yml
- type: JSONLD
  url: json-ld/nearmap-context.jsonld
- type: Vocabulary
  url: vocabulary/nearmap-vocabulary.yml
- type: DataModel
  url: data-model/nearmap-data-model.yml
- type: Authentication
  url: authentication/nearmap-authentication.yml
- type: Conformance
  url: conformance/nearmap-conformance.yml
- type: LLMsTxt
  url: llms/nearmap-llms.txt
- type: SecurityTxt
  url: well-known/nearmap-status-security.txt
- type: WellKnown
  url: well-known/nearmap-well-known.yml
- type: Hosts
  url: hosts/nearmap-hosts.yml
- type: Vendors
  url: vendors/nearmap-vendors.yml
- type: SDKs
  url: packages/nearmap-packages.yml
- type: Packages
  url: packages/nearmap-packages.yml
- type: Support
  url: https://help.nearmap.com
- type: StatusPage
  url: https://status.nearmap.com/
- type: PrivacyPolicy
  url: https://www.nearmap.com/legal/privacy-policy
- type: Newsroom
  url: https://www.nearmap.com/newsroom
- type: Blog
  url: https://www.nearmap.com/blog
- type: APIReference
  url: https://developer.nearmap.com/reference
- type: Documentation
  url: https://developer.nearmap.com/
- type: GitHubOrganization
  url: https://github.com/nearmap
- type: DomainSecurity
  url: security/nearmap-domain-security.yml
- type: Website
  url: https://www.nearmap.com/
apis:
- aid: nearmap:nearmap-coverage-api
  name: Nearmap Coverage API
  description: The Coverage API from Nearmap — 6 operation(s) for coverage.
  humanURL: https://developer.nearmap.com/reference/tiles
  baseURL: https://api.nearmap.com
  tags:
  - Coverage
  properties:
  - type: OpenAPI
    url: openapi/nearmap-coverage-api-openapi.yml
  - type: JSONSchema
    url: json-schema/nearmap-post-coverage-v2-aoi-response-schema.json
  - type: JSONSchema
    url: json-schema/nearmap-get-coverage-v2-point-coord-response-schema.json
  - type: JSONSchema
    url: json-schema/nearmap-get-coverage-v2-v2-id-boundaries-fileformat-response-schema.json
  - type: JSONSchema
    url: json-schema/nearmap-post-coverage-v2-aoi-request-schema.json
  - type: JSONSchema
    url: json-schema/nearmap-get-coverage-v2-coord-zxyresponse-schema.json
  - type: JSONSchema
    url: json-schema/nearmap-get-coverage-v2-poly-polygon-response-schema.json
- aid: nearmap:nearmap-tiles-api
  name: Nearmap Tiles API
  description: The Tiles API from Nearmap — 2 operation(s) for tiles.
  humanURL: https://developer.nearmap.com/reference/tiles
  baseURL: https://api.nearmap.com
  tags:
  - Tiles
  properties:
  - type: OpenAPI
    url: openapi/nearmap-tiles-api-openapi.yml
  - type: JSONSchema
    url: json-schema/nearmap-post-coverage-v2-aoi-response-schema.json
  - type: JSONSchema
    url: json-schema/nearmap-get-coverage-v2-point-coord-response-schema.json
  - type: JSONSchema
    url: json-schema/nearmap-get-coverage-v2-v2-id-boundaries-fileformat-response-schema.json
  - type: JSONSchema
    url: json-schema/nearmap-post-coverage-v2-aoi-request-schema.json
  - type: JSONSchema
    url: json-schema/nearmap-get-coverage-v2-coord-zxyresponse-schema.json
  - type: JSONSchema
    url: json-schema/nearmap-get-coverage-v2-poly-polygon-response-schema.json
x-coverage:
  state: unreadable
  reason: no-machine-readable-spec
  detail: Developer portal provides API reference but no OpenAPI/Swagger spec was found.
  evidence:
  - url: https://developer.nearmap.com/openapi.json
    status: 404
  - url: https://api.nearmap.com/openapi.json
    status: 404
  checked: '2026-10-13'
x-enrichment:
  date: '2026-10-13'
  status: enriched
  artifacts_added: 22
  pass: modular-v1
  engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local

Nearmap API — frequently asked questions

Does Nearmap have an API?

Yes. APIs.io lists 2 APIs from Nearmap, including Nearmap Coverage API and Nearmap Tiles API.

Is there an OpenAPI specification for the Nearmap API?

Yes. APIs.io indexes 2 OpenAPI specifications for Nearmap, each linked for download from this page.

How do I authenticate with the Nearmap API?

Nearmap uses bearer-token authentication (1 scheme). The details are profiled on APIs.io as Nearmap Authentication.

Is the Nearmap API ready for AI agents?

Nearmap has a Kin Score of 24.7 out of 100 (emerging) and an Agent Readiness score of 15.1 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/nearmap"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/nearmap/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/nearmap/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.