Reference & Lookup Data · Integration
Nearmap
Add Nearmap to your product for your customers, and give your AI agents governed access to it.
Embed a Nearmap integration so your product can put current aerial imagery and derived property data in front of users without you building an imagery pipeline. Nearmap captures high resolution aerial surveys and exposes them through APIs for coverage, map tiles and static images, along with AI derived features such as roofs, surfaces, solar panels and vegetation for a given location. Each customer connects their own Nearmap subscription, so imagery and feature requests run under their entitlement and their usage is attributable to them rather than pooled through one key you have to meter. fastn owns the credential storage, retries, throttling and API upkeep, and the same governed connection is what your AI agents query.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Show current aerial imagery for a property inside your product, with each customer's own Nearmap subscription used for the request.
Check coverage and capture dates for a location before your workflow relies on the imagery, so users know how current what they see is.
Read AI derived features for a parcel, such as roof and surface detail, so an assessment in your product starts from measured data rather than a site visit.
Keep imagery usage attributable per tenant, so each customer's entitlement and volume are their own rather than an aggregate you have to divide up later.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent pulls the latest imagery and capture date for an address as part of a property review, with the read audited.
An agent reads derived roof and surface features for a location and summarises what it found for an assessor.
An agent checks whether a location has recent coverage before it commits to an answer, using only that tenant's subscription.
Example prompt
What is the most recent Nearmap capture for this address, and what does the roof detail show?
Set up Nearmap in 4 steps
- 01Enable the Nearmap connector in your fastn dashboard.
- 02Have each customer supply their own Nearmap API key so requests run against their subscription.
- 03Map the coverage, tile and feature requests your product needs, per customer, as configuration.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Nearmap integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Nearmap integration without building it. Your customers connect their own Nearmap account inside your product and work their lookups, results and reports there, with no per-customer code on your side.
- Handle the part that actually costs time: these are metered read sources, so an uncached lookup on every page view burns the customer's allowance. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Nearmap update is not your on-call problem.
- One integration serves your product and your agents. The same governed Nearmap connection powers in-product features and gives AI agents scoped, audited access, so you answer questions from an authoritative outside source without holding that data yourself without wiring it twice.
Used by these teams
Compare with
OneMap Singapore
Weather APIWorks well with
Google Cloud VisionOften used alongside
Tools the same teams tend to run next to Nearmap, across other categories.
Salesforce
HubSpot
Notion
SnowflakeNearmap integration FAQ
How do I add a Nearmap integration to my product?
Enable the Nearmap connector in your fastn dashboard, then let each customer authenticate their own Nearmap account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Nearmap client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Nearmap account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Nearmap account and only ever sees their own lookups, results and reports. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Nearmap integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent pulls the latest imagery and capture date for an address as part of a property review, with the read audited.
Who maintains the Nearmap integration?
fastn does. When Nearmap changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose credentials does a Nearmap lookup run under?
Each customer's own. Quota and cost land on the customer that caused them rather than on a shared key you have to meter and re-bill, and one heavy customer cannot exhaust another's allowance.
How should Nearmap results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. Nearmap is a read source rather than a system of record, so the same query returns the same answer until the source changes, and caching is the difference between a sustainable integration and one that exhausts a customer's allowance on a busy page.
What can I build with the Nearmap integration?
A common starting point: show current aerial imagery for a property inside your product, with each customer's own Nearmap subscription used for the request. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Nearmap integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Nearmap does not change your per-connector cost. You can start free with 3 connected accounts.
Add Nearmap to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.