# What Adragent is

Adragent is how you operate Adrasis Console from chat, email, WhatsApp and SMS — wherever your team already works. You describe a job in your own words; Adragent prepares the operation, shows you a preview, and applies it on your *Confirm*. The same change lands that a console click would produce.

Adragent does not run a parallel system. Same APIs, same role checks, same audit trail. Nothing changes without your approval.

{% hint style="info" %}
**No special syntax to learn.** Type a sentence in your own words, paste a promo email, forward a contract PDF, send a WhatsApp screenshot — Adragent reads what you give it.
{% endhint %}

<figure><img src="/files/OKaXgZMVdna8ij65VaWy" alt="Channels you operate from → Adragent → the same console APIs, role checks and audit trail"><figcaption><p>Adragent reads from any channel and applies through the same console machinery — same APIs, same role checks, same audit trail.</p></figcaption></figure>

***

## What you can ask Adragent to do

Adragent's reach spans every operator workflow in the console. Read operations are broad and immediate; write operations always go through preview and confirm.

### Catalog and content

***

`Operator-side`

Properties, rooms, attributes, meal plans, images, descriptions — query and bulk-update.

* *"Find all properties in Antalya without images and queue them for content review."*
* *"Update Hotel Sunrise's English description with what I'm pasting below."*
* *"List the properties waiting on a content editor's approval."*

Open the [catalog reference](/catalog/property.md) [→](/catalog/property.md)

***

### Rates, inventory and promotions

***

`Operator-side`

Rate plans, allotments, stop-sale, promotions, day-of-week rules — search the calendar and apply changes in bulk.

* *"Apply a 15% weekend discount to Hotel Sunrise rooms for May."*
* *"Stop-sale Bodrum properties on July weekends."*
* *"List properties that have a non-refundable rate plan but no BAR defined."*

Open the [rate plan guide](/pricing-and-availability/rate-plans.md) [→](/pricing-and-availability/rate-plans.md)

***

### Distribution

***

`Operator-side`

Outbound channel exposure and inbound reservation tracking.

* *"Publish Hotel Sunrise on the niche channel we onboarded last week."*
* *"Show me the channels that received zero bookings in the last seven days."*
* *"Show me when the last rate update went to channel X for Hotel Sunrise."*

Open the [distribution overview](/distribution/overview.md) [→](/distribution/overview.md)

***

### Contracts and onboarding

***

`Operator-side`

Supplier onboarding, allotment matrices, release periods, markup setup.

* *(forwarded contract email)* *"Onboard the supplier in this contract and create the allotment matrix."*
* *"List the allotments whose release period expires this week."*
* *"Draft a markup rule for the new supplier for May, ready for my approval."*

Open the [contracts guide](/contracts-and-onboarding/contracts.md) [→](/contracts-and-onboarding/contracts.md)

***

### Payments

***

`Operator-side`

Settlement, virtual card issuing, refund and chargeback status.

* *"Prepare last month's reconciliation report for virtual card transactions."*
* *"Show pending refunds for cancelled bookings."*
* *"Summarise Hotel Sunrise's March settlement by currency."*

Open the [payments overview](/payments/overview.md) [→](/payments/overview.md)

***

### Users and access

***

`Operator-side`

User creation, role assignment, permission queries — within your organization.

* *"Create `foo@adrasis.com` with the content-editor role on the white-label organization."*
* *"List the users who changed a rate in the last seven days."*
* *"Summarise what permissions the finance role carries."*

Open the [security and RBAC guide](/adrasis-console/security-rbac.md) [→](/adrasis-console/security-rbac.md)

***

## How an Adragent operation runs

{% stepper %}
{% step %}

#### Capture intent

You write a request in chat, paste a promo email, forward a supplier message, send a WhatsApp screenshot, or text an SMS. The channel does not change what Adragent does next.
{% endstep %}

{% step %}

#### Adragent prepares the operation

Adragent reads your input, resolves scope (which properties, which dates, which rate plans), and drafts the operation. If anything is ambiguous — a date range that could mean two things, a property name that matches three records — it asks back with a clarifying question.
{% endstep %}

{% step %}

#### You see the preview

Adragent shows the operation as a preview card: what changes, where (counts of affected properties, rate plans, dates), and what stays the same. The preview is bound to your request — once shown, it cannot be tampered with.
{% endstep %}

{% step %}

#### You confirm; Adragent applies

Tap **Confirm**. Adragent applies the operation through the same APIs the console uses, with the same role checks. The action lands in your audit trail with your name on it.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**Read-only requests skip preview and confirm.** Listing properties, checking a rate cell, summarising bookings — anything that does not change state — returns immediately.
{% endhint %}

{% hint style="warning" %}
**No auto-execute.** Adragent never applies a state-changing operation without your *Confirm*. If you walk away from a preview, the operation expires.
{% endhint %}

***

## What Adragent does not do

* **Does not bypass your role.** Adragent runs under your RBAC scope. A finance role can settle but cannot change rates; a content role can edit images but cannot view payments. The same gates the console enforces apply to Adragent.
* **Does not maintain a parallel system.** No separate catalog, no separate audit log, no second source of truth. A change made through Adragent is indistinguishable from a console change in your audit trail, except for the channel of origin.
* **Does not run scheduled rules on its own.** Adragent acts on your intent, on demand. If you want recurring automation — *"apply a markup every Monday"* — set the rule in the console; Adragent helps you set it up but does not become the schedule.
* **Does not read what is not yours.** Organization isolation extends to Adragent. The same organization boundary that hides another agency's contracts in the console hides them from Adragent.

## Where to next

* **The channels Adragent runs on** → [Channels](/adragent/channels.md)
* **Why every write waits for your approval** → [Confirm-before-apply](/adragent/confirm-before-apply.md)
* **What gets recorded for an Adragent operation** → [Audit trail](/adragent/audit-trail.md)
* **The operations Adragent can do for you** → [Tools](/adragent/tools.md)


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.adrasis.com/adragent/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.