> For the complete documentation index, see [llms.txt](https://docs.terminal.africa/tship/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.terminal.africa/tship/miscallaneous/rate-card-directions.md).

# Rate Card Directions

A rate card entry carries a directions array, one entry per service direction the carrier prices for you. This section describes that object.

One carrier can price you from a different card depending on which way the shipment travels. Each entry in `directions` is one such card.

| Attribute          |            | Description                                                                                       |
| ------------------ | ---------- | ------------------------------------------------------------------------------------------------- |
| currency           | *enum*     | Currency the card is priced in.                                                                   |
| description        | *string*   | Description of the rate card. Can be empty.                                                       |
| name               | *string*   | Display name of the rate card.                                                                    |
| rate\_card\_id     | *string*   | Unique reference for the rate card. Pass this to the detail and download endpoints.               |
| service\_direction | *enum*     | Direction the card prices. Must be one of ***local***, ***export*** or ***import***.              |
| transit            | *object*   | Transit time range across the card's zones. `null` when the card has no transit times. See below. |
| updated\_at        | *datetime* | Time the rate card was last updated.                                                              |
| user\_country      | *string*   | The account country the card was resolved for.                                                    |

### The transit object

| Attribute |          | Description                                                                                  |
| --------- | -------- | -------------------------------------------------------------------------------------------- |
| max       | *number* | Slowest transit time on the card.                                                            |
| min       | *number* | Fastest transit time on the card.                                                            |
| side      | *enum*   | Which side of the shipment the times are measured on. One of ***delivery*** or ***pickup***. |
| unit      | *string* | Unit of ***min*** and ***max*** e.g. ***days***.                                             |

{% hint style="warning" %}
`transit` is a **range across every zone on the card**, not an estimate for a particular shipment. A card covering both West Africa and North America will show the fastest and slowest of the two. For a per-shipment estimate, use the delivery time returned with a rate.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.terminal.africa/tship/miscallaneous/rate-card-directions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.