# Introduction

Adrasis Console is the agency-side platform for pricing, contracts and multi-channel distribution. This documentation describes the platform as it operates today.

The sections below correspond to the operator workflows the platform supports. Each section is self-contained; cross-references are added where related context applies.

## Where Adrasis fits

Adrasis acts as the agency hub between accommodation supply and the channels where that supply is sold. It brings inventory in from properties, hotel chains, bedbank stock and channel managers; then it distributes curated products to online travel agencies, niche channels, B2B partners, metasearch engines and superapps.

Three things follow from that positioning:

* **Both buyer and supplier.** Your agency can consume third-party inventory and expose its own curated supply to other partners.
* **Multi-channel distribution from a single console.** Outbound traffic to OTAs, niche channels, B2B partners and superapps is managed from one contract schema.
* **Designed around the agency workflow.** Contracts, allotments, markups, multi-supplier sourcing — the platform is built around these primitives.

## Who it is for

* **Travel agencies** running multi-supplier contracts and outbound distribution.
* **Tour operators** packaging stay, transport and ancillaries across markets.
* **Tourism vendors** consolidating supply from independent and chain hotels.
* **Travel superapps** that need a programmable backend behind their booking experience.
* **Independent hotels and small chains** participating as supply-side stakeholders through onboarding contracts.

## What an agency runs from one console

| Area                                                                      | What it covers                                                                                                  |
| ------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| [Catalog & content](/console/catalog/property.md)                         | Multilingual properties, rooms, attributes, meal plans, images and locations in one shared catalog view.        |
| [Contracts & onboarding](/console/contracts-and-onboarding/contracts.md)  | Multi-supplier contracts, allotments, release periods, markups, cancellation policies, e-signature flow.        |
| [Mapping & curation](/console/mapping-and-curation/canonical-mapping.md)  | Canonical mapping across suppliers — rooms, attributes, meal plans, images.                                     |
| [Pricing & availability](/console/pricing-and-availability/rate-plans.md) | Rate plans, real-time inventory, stop-sale, promotions, day-of-week rules, audience targeting.                  |
| [Distribution](/console/distribution/overview.md)                         | Outbound to OTAs, metasearch, B2B partners, superapps; inbound from properties, suppliers and channel managers. |
| [Payments](/console/payments/overview.md)                                 | Multi-currency settlement, virtual card issuing, reconciliation, refunds, retries, chargebacks.                 |

## Adragent — the command interface

[Adragent](/console/adragent/overview.md) is the command interface for Adrasis: it operates over chat, email, WhatsApp and SMS. The operator writes the intent in natural language:

* *"Apply a 15% weekend discount to Hotel Sunrise for May."*
* *"Stop-sale Bodrum properties on July weekends."*
* *(forwarding a supplier promo)* *"Onboard this supplier and create the allotment matrix."*

Adragent prepares the operation, presents it as a structured preview, and applies it only on operator confirmation.

For repetitive work — bulk promotions, supplier price updates, content fixes, allotment reconciliation — the operator describes the job once, reviews the preview, and the action is applied.

## New channel integrations

New supplier and channel integrations typically land within days. Share the partner's connection guide and test access; the connection is released against the agreed timeline.

Every release is tested against the partner's own environment before it reaches live operations.

## How to read this documentation

* For an introduction to the platform: [Platform Overview](/console/adrasis-console/overview.md).
* For daily operator workflows: [Getting Started](/console/getting-started/getting-started.md) and the relevant sections in the navigation.
* For Adragent evaluation: [Adragent Overview](/console/adragent/overview.md) and [Confirm-before-apply](/console/adragent/confirm-before-apply.md).

## Terminology

For terminology, see the [Glossary](/console/getting-started/glossary.md) — allotment, markup, rate plan, channel visibility and the rest of the vocabulary used throughout the platform. Notable releases are tracked in the [Changelog](/console/changelog/changelog.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://adrasis.gitbook.io/console/readme.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.