---
name: "xpay-mapbox-directions-tool"
description: "Fetches directions from Mapbox API based on provided coordinates and direction method."
version: "1.0.0"
price: "$0.01/call"
provider: "Mapbox"
---

# Directions Tool

Fetches directions from Mapbox API based on provided coordinates and direction method.

**Provider:** Mapbox
**Price:** $0.01/call
**Pricing model:** Flat rate per call

## When to Use

Use this tool when you need to fetches directions from mapbox api based on provided coordinates and direction method.. This is part of the Mapbox provider on xpay✦.

## MCP Connection

Connect to xpay✦ to access this tool (and 8+ others):

```json
{
  "mcpServers": {
    "xpay": {
      "url": "https://mcp.xpay.sh/mcp?key=YOUR_API_KEY"
    }
  }
}
```

For Claude Code:
```bash
claude mcp add --transport http xpay "https://mcp.xpay.sh/mcp?key=YOUR_API_KEY"
```

## How to Execute

Use the xpay✦ meta-tools to run this tool:

1. **`xpay_details`** — Get full input schema: `xpay_details("mapbox/directions_tool")`
2. **`xpay_run`** — Execute: `xpay_run("mapbox/directions_tool", { ...inputs })`

## Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `max_width` | number | No | The max vehicle width, in meters. The Directions API will compute a route that includes only roads with a width limit greater than or equal to the max vehicle width. Must be between 0 and 10 meters. The default value is 1.9 meters. Only available for driving and driving-traffic profiles. |
| `depart_at` | string | No | The departure time in ISO 8601 format (YYYY-MM-DDThh:mm:ssZ, YYYY-MM-DDThh:mmss±hh:mm, or YYYY-MM-DDThh:mm). This parameter is only available for the driving and driving-traffic profiles. The travel time will be calculated based on historical and real-time traffic data. |
| `max_weight` | number | No | The max vehicle weight, in metric tons (1000 kg). The Directions API will compute a route that includes only roads with a weight limit greater than or equal to the max vehicle weight. Must be between 0 and 100 metric tons. The default value is 2.5 metric tons. Only available for driving and driving-traffic profiles. |
| `routing_profile` | string | No | Routing profile for different modes of transport. Options:  - driving-traffic (default): automotive with current traffic conditions - driving: automotive based on typical traffic - walking: pedestrian/hiking - cycling: bicycle |
| `geometries` | string | No | The format of the returned geometry. Options:  - none (default): no geometry object is returned at all, use this if you do not need all of the intermediate coordinates. - geojson: as GeoJSON LineString (might be very long as there could be a lot of points) |
| `coordinates` | array | Yes | Array of [longitude, latitude] coordinate pairs to visit in order. Must include at least 2 coordinate pairs (starting and ending points). Up to 25 coordinates total are supported. |
| `alternatives` | boolean | No | Whether to try to return alternative routes (true) or not (false, default). Up to two alternatives may be returned. |
| `max_height` | number | No | The max vehicle height, in meters. The Directions API will compute a route that includes only roads with a height limit greater than or equal to the max vehicle height. Must be between 0 and 10 meters. The default value is 1.6 meters. Only available for driving and driving-traffic profiles. |
| `arrive_by` | string | No | The desired arrival time in ISO 8601 format (YYYY-MM-DDThh:mm:ssZ, YYYY-MM-DDThh:mmss±hh:mm, or YYYY-MM-DDThh:mm). This parameter is only available for the driving profile and is not supported by other profiles, not even driving-traffic. The travel time will be calculated based on historical and real-time traffic data. |
| `exclude` | string | No | Whether to exclude certain road types and custom locations from routing. Multiple values can be specified as a comma-separated list. Available options: - All profiles:  ferry, cash_only_tolls - Driving/Driving-traffic profiles only: motorway, toll, unpaved, tunnel, country_border, state_border or point(<lng> <lat>) For custom locations you can use Point exclusions (note lng and lat are space separated and at most 50 points are allowed) Note: country_border excludes all controlled country borders; borders within the Schengen Area are not excluded. |

## Pricing

- **Cost:** $0.01/call
- **Balance check:** Use `xpay_balance` to check remaining credits
- Get your API key at [xpay.tools](https://xpay.tools/account/settings/api-keys/) — $5 free credits included

## Related Skills

- [Mapbox (all tools)](https://xpay.tools/skills/mapbox/SKILL.md) — 9 tools
- [Version Tool](https://xpay.tools/skills/mapbox/version-tool/SKILL.md) — $0.01/call
- [Category Search Tool](https://xpay.tools/skills/mapbox/category-search-tool/SKILL.md) — $0.01/call
- [Forward Geocode Tool](https://xpay.tools/skills/mapbox/forward-geocode-tool/SKILL.md) — $0.01/call
- [Isochrone Tool](https://xpay.tools/skills/mapbox/isochrone-tool/SKILL.md) — $0.01/call
- [Matrix Tool](https://xpay.tools/skills/mapbox/matrix-tool/SKILL.md) — $0.01/call

## Links

- Tool page: https://xpay.tools/mapbox/directions-tool/
- Provider: https://xpay.tools/mapbox/
- All tools: https://xpay.tools/explore