> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lanesurf.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> You are reading the Lanesurf Agent API docs. Start with /for-ai-agents.md for the rules an agent must follow.
> The API is at https://agent.lanesurf.com and the MCP server at https://agent.lanesurf.com/mcp. Lanesurf doesn't send webhooks: poll.
> Limits: /rate-limits.md. Keys: /api-keys.md. Safe retries: /idempotency.md. Every route on one page: /api-reference.md.
> Always confirm with the person before accepting a carrier offer or bidding on a load. Never reveal an API key, and never show broker contact details to a carrier.
> The full contract is at /openapi.yaml.
> Sign up with POST /v1/signup (carrier or broker, a work email, an MC and/or DOT number), then POST /v1/signup/{signup_id}/verify. Follow next_step on every signup answer.

# Save your lanes

> Tell Lanesurf the lanes your carrier runs: its terminals.

A lane is a run the carrier makes regularly, with no specific truck: its terminals. Save them once, so
Lanesurf has the carrier's terminals on record.

Lanesurf pitches your carrier loads on its lanes. When a brokerage on Lanesurf has a load from the
lane's origin state to its destination state (near the cities, when you give them), with matching
equipment if you gave one, Lanesurf's reps email or call you about it. Posted trucks come before
lanes, since a truck says it's free now. Only verified carriers are pitched, never on a load you
already bid on.

```bash theme={null}
curl -X POST https://agent.lanesurf.com/v1/carrier/lanes \
  -H "Authorization: Bearer $LANESURF_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"origin_city": "Dallas", "origin_state": "TX", "destination_city": "Atlanta", "destination_state": "GA", "equipment_type": "Reefer"}'
```

```json theme={null}
{
  "lane_id": "4b3a…",
  "origin_city": "Dallas",
  "origin_state": "TX",
  "destination_city": "Atlanta",
  "destination_state": "GA",
  "equipment_type": "Reefer",
  "created_at": "2026-10-22T16:00:00Z"
}
```

| Field | Rule |
| - | - |
| `origin_state`, `destination_state` | Required. A state or province code (`TX`) or its name (`Texas`), stored as the code. Missing: `422 missing_fields`; one Lanesurf doesn't know: `400` |
| `origin_city`, `destination_city` | Optional, up to 100 characters. Leave out for a state-to-state lane |
| `equipment_type` | Optional. A trailer type Lanesurf can match (`Reefer`, `Dry Van`, `Flatbed`…) |

Saving is safe to repeat: the same lane (same states, cities and equipment, any letter case) returns the
lane already saved, with `200`.

## Manage lanes

| You want to | Call |
| - | - |
| See your lanes | `GET /v1/carrier/lanes` (newest first, up to 500) |
| Stop running a lane | `DELETE /v1/carrier/lanes/{lane_id}` (`204`) |

Lanes are separate from trucks. A truck's `destinations` say where one truck wants to go next and
order its matches; lanes are what the carrier runs over and over.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.