> For the complete documentation index, see [llms.txt](https://docs.commercelayer.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.commercelayer.io/core-api-reference/vertex_accounts.md).

# Vertex accounts

The Vertex account object and the allowed CRUD operations on the related resource endpoint

Configure your [Vertex](https://www.vertexinc.com/) account to automatically compute tax calculations for the orders of the associated market.

Based on the [Vertex O Series](https://www.vertexinc.com/solutions/products/vertex-indirect-tax-o-series) type of solution you choose (set as the value of the `kind` attribute), the configuration might slightly differ, for example for what the base URL used to compose the appropriate endpoint URL to which the integration submits the request for an access token is concerned. Specifically, as detailed in the [Vertex API documentation](https://developer.vertexinc.com/oseries/docs/authentication-os#local-token-caching):

* **O Series Cloud** — Fixed URL with no base URL attached.
* **O Series On-Demand** — The base URL is a second-level domain.
* **O Series On-Premise** — You need to use your full server domain as the base URL.

{% hint style="warning" %}
Due to what was mentioned above, when creating a Vertex account, the `baseurl` attribute is optional only if the `kind` is `cloud`.
{% 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.commercelayer.io/core-api-reference/vertex_accounts.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.