> For the complete documentation index, see [llms.txt](https://mercure-technologies.gitbook.io/xprem/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mercure-technologies.gitbook.io/xprem/eoas/overview.md).

# Overview

EOAS is an npm CLI for managing application updates.

Use it to:

* Deploy and republish updates.
* Roll back an update.
* Initialize a project and generate certificates.
* Audit an existing configuration.

EOAS works in a developer's local environment and in CI pipelines.

### Authentication

EOAS authenticates with `EOO_TOKEN`, an application-scoped API key.

Generate it from the dashboard, on your application's **API tokens** page. The database stores only the token hash, so the value is shown once at creation and cannot be retrieved later.

Use a separate key for each CI environment or workflow and keep every key in your CI secret store. You can scope what each key may do, branch by branch, with [Token access](/xprem/security/token-access.md).

### Pin the EOAS version in CI

{% hint style="warning" %}
Never run unversioned `npx eoas` in CI. Always use an explicit EOAS version.
{% endhint %}

An unpinned command can fetch a newer CLI release unexpectedly. This can introduce breaking changes into a pipeline.

Use the EOAS version that exactly matches the server version:

`npx eoas@<server-version> <command>`

EOAS releases stay synchronized with the server version during release publishing. Update the CLI version whenever you upgrade the server.


---

# 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://mercure-technologies.gitbook.io/xprem/eoas/overview.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.