Reference & Lookup Data · Integration
Trimble
Add Trimble to your product for your customers, and give your AI agents governed access to it.
Trimble is a portfolio rather than one system, spanning construction, agriculture, geospatial survey and transportation, and its construction and field platforms are separate products with their own accounts. What an embedded integration reaches here is the location side: routing and mileage for commercial vehicles, where a legal truck route is not the same road a car would take because height, weight, hazardous load and road restrictions all apply, plus geocoding and place lookups to turn an address into something you can route against. That is a metered read source, so two things follow. The key is the customer's own, which keeps quota and cost with whoever caused it. And the answers are stable, so a route or a geocode should be cached rather than requested again on every page view. fastn holds each key per tenant and follows the API.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Have each customer bring their own key, so routing and lookup usage is billed to whoever caused it rather than metered against an account you own.
Route for the vehicle that is actually driving, so height, weight and restricted roads are respected instead of assumed.
Turn an address into coordinates your product can use, and cache the answer, since an address does not move.
Show distance and estimated time inside your product without sending anyone to a separate mapping tool.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent works out whether a stop is reachable within a driver's remaining time and explains what it assumed.
An agent compares two routes and reports the difference in distance for the vehicle in question.
An agent resolves an ambiguous address before anything downstream depends on the wrong location.
Example prompt
How far is this delivery from the depot for a heavy vehicle, and does the route avoid any restricted roads?
Set up Trimble in 4 steps
- 01Enable the Trimble connector in your fastn dashboard.
- 02Have each customer supply their own key, so lookups run against their allowance rather than a shared one.
- 03Decide which lookups your product makes and set a cache window per tenant that matches how rarely the answers change.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Trimble integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Trimble integration without building it. Your customers connect their own Trimble 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 Trimble update is not your on-call problem.
- One integration serves your product and your agents. The same governed Trimble 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
Nearmap
OneMap Singapore
Weather APIOften used alongside
Tools the same teams tend to run next to Trimble, across other categories.
Salesforce
HubSpot
Notion
SnowflakeTrimble integration FAQ
How do I add a Trimble integration to my product?
Enable the Trimble connector in your fastn dashboard, then let each customer authenticate their own Trimble account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Trimble client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Trimble account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Trimble 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 Trimble 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 works out whether a stop is reachable within a driver's remaining time and explains what it assumed.
Who maintains the Trimble integration?
fastn does. When Trimble 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 Trimble 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 Trimble results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. Trimble 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 Trimble integration?
A common starting point: have each customer bring their own key, so routing and lookup usage is billed to whoever caused it rather than metered against an account you own. 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 Trimble integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Trimble does not change your per-connector cost. You can start free with 3 connected accounts.
Add Trimble to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.