@tileflow/routing 0.0.0-stage → 0.1.0-alpha.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/LICENSE ADDED
@@ -0,0 +1,201 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "[]"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright [yyyy] [name of copyright owner]
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200
+ See the License for the specific language governing permissions and
201
+ limitations under the License.
package/README.md CHANGED
@@ -1,3 +1,338 @@
1
- # Temporary Holding Version
1
+ # @tileflow/routing
2
2
 
3
- This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
3
+ Routes, isochrones, travel-time matrices, map matching and nearest-road lookups for driving,
4
+ walking, cycling and trucks, computed by Tileflow on a routable network built from the same
5
+ OpenStreetMap data as Tileflow World. Routes follow the streets the map draws and use the names it
6
+ shows. The client uses `fetch` and has no renderer or global state.
7
+
8
+ > Related packages and guides: [documentation index](https://raw.githubusercontent.com/tileflow/tileflow-sdk/main/llms.txt).
9
+
10
+ ## Install
11
+
12
+ ```sh
13
+ npm install @tileflow/routing@alpha
14
+ ```
15
+
16
+ Use Node.js 22, a browser or another runtime with `fetch`.
17
+
18
+ Live requests require Tileflow Routing to be enabled for your Team and a credential with the
19
+ Routing permission. Installing this package does not enable the service or grant access.
20
+
21
+ ## Calculate a route
22
+
23
+ <!-- docs:check -->
24
+
25
+ ```ts
26
+ import {route} from '@tileflow/routing';
27
+
28
+ const apiKey = process.env.TILEFLOW_API_KEY;
29
+ if (!apiKey) throw new Error('Set TILEFLOW_API_KEY on the server.');
30
+
31
+ const answer = await route(
32
+ {
33
+ locations: [
34
+ [-80.2195, 25.7655],
35
+ [-80.1312, 25.7795],
36
+ ],
37
+ mode: 'driving',
38
+ alternatives: 1,
39
+ },
40
+ {apiKey},
41
+ );
42
+
43
+ const [fastest] = answer.routes;
44
+ console.log(fastest?.distance, fastest?.duration, answer.usage.units);
45
+ for (const step of fastest?.legs[0]?.steps ?? []) console.log(step.instruction);
46
+ ```
47
+
48
+ **Request:**
49
+
50
+ - `locations`: two to five `[longitude, latitude]` positions: an origin, optional stops and a
51
+ destination. Each stretch between consecutive positions is a leg.
52
+ - `mode`: `driving`, `walking`, `cycling` or `truck`.
53
+ - `alternatives` (optional, 0–2): only between two positions. Fewer come back when no distinct
54
+ alternative exists.
55
+ - `language` (optional): writes the instructions in one of `routingLanguages`.
56
+ - `vehicle`, `avoid` and `traffic` (optional): see
57
+ [Route a truck around tolls](#route-a-truck-around-tolls).
58
+
59
+ **Answer:** routes, fastest first. Each route has:
60
+
61
+ - `distance` in metres and `duration` in seconds;
62
+ - `hasTolls`, `hasHighways` and `hasFerries`: whether the route uses a toll road, a highway or a
63
+ ferry;
64
+ - a GeoJSON `LineString` `geometry`;
65
+ - `legs` of `steps`. Each step has a `maneuver`, an `instruction`, the street `names` and, on
66
+ highways, the `exit` number and the destinations it is signed `toward`.
67
+
68
+ Durations are estimates without traffic; see [Travel times and traffic](#travel-times-and-traffic).
69
+
70
+ ## Route a truck around tolls
71
+
72
+ <!-- docs:check -->
73
+
74
+ ```ts
75
+ import {route} from '@tileflow/routing';
76
+
77
+ const apiKey = process.env.TILEFLOW_API_KEY;
78
+ if (!apiKey) throw new Error('Set TILEFLOW_API_KEY on the server.');
79
+
80
+ const answer = await route(
81
+ {
82
+ locations: [
83
+ [-80.2878, 25.8195],
84
+ [-80.1918, 26.1224],
85
+ ],
86
+ mode: 'truck',
87
+ vehicle: {heightMeters: 4.1, weightTonnes: 18, axleCount: 3, hazardousMaterials: false},
88
+ avoid: ['tolls'],
89
+ },
90
+ {apiKey},
91
+ );
92
+
93
+ const [fastest] = answer.routes;
94
+ if (fastest?.hasTolls) console.log('No reasonable route avoids every toll road.');
95
+ ```
96
+
97
+ `vehicle` describes the truck. It is accepted only with `mode: 'truck'`, and every field is
98
+ optional:
99
+
100
+ | Field | Unit and range |
101
+ | -------------------- | -------------- |
102
+ | `heightMeters` | 1–10 metres |
103
+ | `widthMeters` | 1–5 metres |
104
+ | `lengthMeters` | 1–40 metres |
105
+ | `weightTonnes` | 0.5–100 tonnes |
106
+ | `axleLoadTonnes` | 0.5–40 tonnes |
107
+ | `axleCount` | whole, 2–20 |
108
+ | `hazardousMaterials` | `true`/`false` |
109
+
110
+ The route respects these dimensions where OpenStreetMap records a limit. A road without a recorded
111
+ height, weight or hazardous-materials restriction is treated as unrestricted, so check clearances
112
+ that matter on the ground.
113
+
114
+ `avoid` lists `tolls`, `highways` and `ferries`, each at most once, in any mode. **Avoidance is a
115
+ strong preference, not an exclusion:** when no reasonable route avoids a road kind, the answer
116
+ still uses it. Check `hasTolls`, `hasHighways` and `hasFerries` on each route rather than assuming
117
+ the avoidance held.
118
+
119
+ Isochrones and matrices take the same `vehicle`, `avoid` and `traffic` options. Map matching takes
120
+ `vehicle` only.
121
+
122
+ ## Calculate an isochrone
123
+
124
+ <!-- docs:check -->
125
+
126
+ ```ts
127
+ import {isochrone} from '@tileflow/routing';
128
+
129
+ const apiKey = process.env.TILEFLOW_API_KEY;
130
+ if (!apiKey) throw new Error('Set TILEFLOW_API_KEY on the server.');
131
+
132
+ const answer = await isochrone(
133
+ {location: [-80.1918, 25.7617], mode: 'walking', minutes: [5, 10, 15]},
134
+ {apiKey},
135
+ );
136
+
137
+ for (const area of answer.isochrones.features)
138
+ console.log(area.properties.minutes, area.geometry.type);
139
+ ```
140
+
141
+ `minutes` holds one to four whole minutes from 1 to 60, rising. The answer is a GeoJSON
142
+ `FeatureCollection` with one `Polygon` or `MultiPolygon` per time, in the same order.
143
+
144
+ ## Calculate a travel-time matrix
145
+
146
+ A matrix gives the duration and distance from every source to every target, for example to find
147
+ the nearest of several depots or to feed your own route optimizer.
148
+
149
+ <!-- docs:check -->
150
+
151
+ ```ts
152
+ import {matrix} from '@tileflow/routing';
153
+
154
+ const apiKey = process.env.TILEFLOW_API_KEY;
155
+ if (!apiKey) throw new Error('Set TILEFLOW_API_KEY on the server.');
156
+
157
+ const depots: [number, number][] = [
158
+ [-80.2878, 25.8195],
159
+ [-80.3698, 25.6866],
160
+ ];
161
+ const stops: [number, number][] = [
162
+ [-80.1312, 25.7795],
163
+ [-80.1918, 25.7617],
164
+ [-80.2683, 25.942],
165
+ ];
166
+
167
+ const answer = await matrix({sources: depots, targets: stops, mode: 'driving'}, {apiKey});
168
+
169
+ answer.durations.forEach((row, depot) => {
170
+ row.forEach((seconds, stop) => {
171
+ const minutes = seconds === null ? 'no route' : `${Math.round(seconds / 60)} min`;
172
+ console.log(`depot ${depot} → stop ${stop}: ${minutes}`);
173
+ });
174
+ });
175
+ ```
176
+
177
+ **Request:** one to 25 `sources` and one to 25 `targets`, a `mode`, and optionally `vehicle`,
178
+ `avoid` and `traffic`. The straight-line distance between every source and every target must be
179
+ within the mode's limit: 200 km for `driving` and `truck`, and 10 km for `cycling` and `walking`
180
+ (`routingLimits.maximumMatrixDistanceMeters`).
181
+
182
+ **Answer:** `durations` in seconds and `distances` in metres, with one row per source and one
183
+ column per target, in request order: `durations[source][target]`. A cell is `null` when no route
184
+ was found for that pair: none exists, or the service could not find one in time. Request a single
185
+ route for a pair you still need. The client rejects an answer whose rows or columns do not match the
186
+ request.
187
+
188
+ ## Match a GPS trace to roads
189
+
190
+ Map matching snaps a recorded trace to the roads it most likely followed and describes each road,
191
+ including its speed limit where OpenStreetMap records one.
192
+
193
+ <!-- docs:check -->
194
+
195
+ ```ts
196
+ import {match} from '@tileflow/routing';
197
+
198
+ const apiKey = process.env.TILEFLOW_API_KEY;
199
+ if (!apiKey) throw new Error('Set TILEFLOW_API_KEY on the server.');
200
+
201
+ const answer = await match(
202
+ {
203
+ trace: [
204
+ [-80.1327, 25.7808],
205
+ [-80.1324, 25.784],
206
+ [-80.1318, 25.7922],
207
+ ],
208
+ timestamps: [1760000000, 1760000012, 1760000031],
209
+ accuracy: 10,
210
+ mode: 'driving',
211
+ },
212
+ {apiKey},
213
+ );
214
+
215
+ for (const road of answer.roads) {
216
+ const name = road.names[0] ?? road.class;
217
+ const limit = road.speedLimit ? `${road.speedLimit.kmh} km/h` : 'no tagged speed limit';
218
+ console.log(`${name}: ${Math.round(road.length)} m, ${limit}`);
219
+ }
220
+ ```
221
+
222
+ **Request:**
223
+
224
+ - `trace`: 2 to 100 positions in the order they were recorded. Consecutive positions must be within
225
+ 2 km of each other, and the straight-line distance through them may not exceed 200 km.
226
+ - `timestamps` (optional): seconds since the Unix epoch, one per position, never decreasing.
227
+ - `accuracy` (optional): GPS accuracy in metres, 1–100. The default suits a phone outdoors.
228
+ - `mode` and, for `truck`, an optional `vehicle`.
229
+
230
+ **Answer:**
231
+
232
+ - `distance`, `duration` and the matched `geometry`;
233
+ - `points`: one entry per trace position, in order, with the matched `location` and its `distance`
234
+ in metres from the recorded position, or `null` when that position was not matched;
235
+ - `roads`: the roads of the matched path, in order, with consecutive pieces of one road merged.
236
+
237
+ Each road has its `names`, OpenStreetMap `wayId`, `class` (from `routingRoadClasses`), `surface`,
238
+ `lanes`, `toll`, `bridge`, `tunnel`, `roundabout`, `length` in metres and `speedLimit`.
239
+
240
+ **Speed limits are the values tagged in OpenStreetMap, or `null`.** A limit is
241
+ `{kmh, source: 'tagged'}` only where OpenStreetMap records one; otherwise it is `null`. The service
242
+ does not infer limits from the road class or the country's defaults. A tagged value can be missing,
243
+ outdated or different from the signs on the ground.
244
+
245
+ ## Find the nearest road
246
+
247
+ <!-- docs:check -->
248
+
249
+ ```ts
250
+ import {nearest} from '@tileflow/routing';
251
+
252
+ const apiKey = process.env.TILEFLOW_API_KEY;
253
+ if (!apiKey) throw new Error('Set TILEFLOW_API_KEY on the server.');
254
+
255
+ const answer = await nearest({location: [-80.1312, 25.7795], mode: 'driving'}, {apiKey});
256
+
257
+ console.log(answer.road.names[0] ?? answer.road.class, answer.distance, answer.location);
258
+ console.log(answer.road.speedLimit?.kmh ?? 'no tagged speed limit');
259
+ ```
260
+
261
+ The request takes one `location` and a `mode`. The answer has the nearest point of a road that
262
+ mode can use as `location`, its `distance` in metres from the requested position, and the `road`
263
+ with the same attributes as map matching, including the tagged `speedLimit` or `null`.
264
+
265
+ ## Travel times and traffic
266
+
267
+ **Durations and ETAs do not include traffic.** They are estimated from the road network alone, so
268
+ they do not reflect congestion, incidents or the time of day.
269
+
270
+ Every answer states this in `traffic: 'none'`. Route, isochrone and matrix requests accept an
271
+ optional `traffic` field, and `'none'` is its only accepted value (`routingTrafficKinds`).
272
+
273
+ ## Draw a route on a map
274
+
275
+ Routes and isochrones are plain GeoJSON, so any map can draw them. With MapLibre:
276
+
277
+ <!-- docs:check -->
278
+
279
+ ```ts
280
+ import type {RoutingRouteResponse} from '@tileflow/routing';
281
+
282
+ // The two MapLibre map methods this example uses; pass your maplibregl.Map.
283
+ type RouteMap = {
284
+ addSource(id: string, source: object): unknown;
285
+ addLayer(layer: object): unknown;
286
+ };
287
+
288
+ export function showRoute(map: RouteMap, answer: RoutingRouteResponse) {
289
+ const fastest = answer.routes[0];
290
+ if (!fastest) return;
291
+ map.addSource('route', {
292
+ type: 'geojson',
293
+ data: {type: 'Feature', properties: {}, geometry: fastest.geometry},
294
+ lineMetrics: true,
295
+ });
296
+ map.addLayer({
297
+ id: 'route',
298
+ type: 'line',
299
+ source: 'route',
300
+ layout: {'line-cap': 'round', 'line-join': 'round'},
301
+ paint: {'line-color': '#2563eb', 'line-width': 6},
302
+ });
303
+ }
304
+ ```
305
+
306
+ To colour the route with the map's theme and draw it on progressively, use Core's route inks and
307
+ line progress; see the
308
+ [route drawing guide](https://github.com/tileflow/tileflow-sdk/blob/main/packages/core/docs/route-drawing.md).
309
+ Keep the answer's `attribution` visible with the route. Like the map, routes come from
310
+ OpenStreetMap data.
311
+
312
+ ## Errors
313
+
314
+ Failures throw `RoutingError` with:
315
+
316
+ - `code`, from `routingErrorCodes`, when the service sent one with its documented status;
317
+ - `status`;
318
+ - `requestId`;
319
+ - `retryAfterSeconds` on rate limits.
320
+
321
+ `ROUTING_NO_ROUTE` means that no road the mode can use is near a position, or that no route
322
+ connects the positions in that mode. In a matrix answer, a pair that no route connects is a `null`
323
+ cell. The client never retries; repeat an operation only after an explicit user action.
324
+
325
+ Invalid requests are rejected before any network call. Each answer must match its request: the
326
+ requested number of legs, isochrone times, matrix rows and columns, and matched trace points.
327
+
328
+ ## Browser and app credentials
329
+
330
+ A publishable credential is restricted to your origins or app identifiers and can be used in client
331
+ code. Native apps pass `app: {id, certificateSha256}` so a publishable credential can admit them.
332
+ Server credentials must stay on your server.
333
+
334
+ ## Contract
335
+
336
+ `@tileflow/routing/contract` exports the request and answer schemas, limits, modes, avoidances,
337
+ traffic kinds, road classes and surfaces, maneuvers, languages and error codes. Use them to validate
338
+ data that crosses your own boundaries.