# Introduction **The travel technology platform for the agency side.** One operating layer for pricing, contracts, inventory, and multi-channel distribution — built for travel agencies, tour operators, tourism vendors, and travel superapps. ## What it is Adrasis Console is the **L3 hub and aggregator on the agency side** of the travel stack. Where the well-known hub aggregators serve hotels, Adrasis serves agencies: aggregating supply upstream from L1 stock owners (hotel chains, independent properties, bedbank stock) via L2 channel managers, and distributing downstream to L4 partners (OTAs, niche channels, B2B partners, metasearch, superapps). The platform acts as both **supplier and distributor**, so an agency becomes a distribution endpoint, not just a reseller — every commercial workflow it runs is held in a single canonical schema, ready to push to any channel through one contract surface. ## 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 operating layer behind their booking experience. * **L1 stock owners** (independent hotels, small chains) participating as supply-side stakeholders through onboarding contracts. ## What is different Adrasis is built agency-first, not as a bolt-on of a hotel-side hub. Three differentiators shape the platform: ### 1. Adragent — agentic agency automation [Adragent](/adragent/overview.md) runs the operations layer of Adrasis across **chat, email, WhatsApp, and SMS**. The operator sets the intent on any channel; Adragent prepares the operation, asks for confirmation, executes — RBAC-gated like the rest of the console, with a cryptographic audit trail (every operation hashed, idempotent, replay-safe). Every API endpoint is an agent-callable tool with confirm-before-apply semantics. ### 2. Connectors ship fast New supplier and channel integrations land in **days, not months**. Every connector release includes contract tests and partner-sandbox conformance, so what reaches production has been verified against partner reality — not just against unit tests. ### 3. Multi-channel distribution from day one [Distribution](/distribution/overview.md) is included, not an afterthought. Outbound to OTAs, niche channels, B2B partners, metasearch and superapps via XML, REST, and GraphQL. Inbound from L1 stock owners and L2 channel managers via the same canonical surface. A dedicated, read-only Distribution Service serves ARI to high-traffic channels under tight latency budgets. ## Core capabilities | Area | What it covers | | --------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- | | [Catalog & content](/catalog/property.md) | Multilingual properties, rooms, attributes, meal plans, images, locations — held in a canonical schema. | | [Contracts & onboarding](/contracts-and-onboarding/contracts.md) | Multi-supplier contracts, allotments, release periods, markups, cancellation policies, e-signature flow. | | [Mapping & curation](/mapping-and-curation/canonical-mapping.md) | Canonical mapping across suppliers — rooms, attributes, meal plans, images. | | [Pricing & availability](/pricing-and-availability/rate-plans.md) | Rate plans, real-time inventory, stop-sale, promotions, day-of-week rules, audience targeting. | | [Distribution](/distribution/overview.md) | Outbound to OTAs, metasearch, B2B partners, superapps; inbound from L1 hotels and L2 channel managers. | | [Payments](https://github.com/adrasis/adrasis-console/blob/main/docs/en/payments/overview.md) | Multi-currency settlement, virtual card issuing, reconciliation, refunds, retries, chargebacks. | | [Adragent](/adragent/overview.md) | Agentic operations across chat, email, WhatsApp and SMS — confirm-before-apply, fully audited. | | [Multi-tenancy](/platform/multi-tenancy.md) | Subsidiaries, white-label brands, partner agencies under one roof — per-tenant isolation and RBAC. | ## How to read this documentation * **New to Adrasis?** Start with the [Platform Overview](/platform/overview.md) to see where the L3 layer sits, then read [Architecture](/platform/architecture.md). * **Operator role** (contracting, content, sales)? Open [Getting Started for operators](/getting-started/for-operators.md) and follow the feature sections from the navigation. * **Integrator or developer?** Jump to [Getting Started for developers](/getting-started/for-developers.md) — the API reference and connector authoring docs live on the dedicated developer portal. * **Evaluating Adragent?** Read [Adragent Overview](/adragent/overview.md) and [Confirm-before-apply](/adragent/confirm-before-apply.md). ## Terminology For terminology, see the [Glossary](/getting-started/glossary.md) — L1–L4, ARI, allotment, markup, canonical schema, and the rest of the vocabulary used throughout the platform. Notable releases are tracked in the [Changelog](https://github.com/adrasis/adrasis-console/blob/main/docs/en/changelog/README.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/readme.md?ask= ``` 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.