# Metasearch & B2B platforms

This page covers the channel family with high-traffic, fast-response connections — primarily metasearch engines (hotel comparison sites) and B2B platforms. Different partners, different formats; for you, one operator workflow.

## What this family is

Metasearch engines and large B2B platforms behave differently from the rest of your outbound channels. They:

* **Poll at high rates** — many requests per second across many properties.
* **Compete on latency** — a result that takes 800 ms loses to one that takes 80 ms.
* **Read only** — you publish availability, rates and inventory; the partner does not write back into your inventory.
* **Want partner-specific delivery** — each partner expects its own format and timing.

These channels are read-heavy and timing-sensitive, so setup focuses on feed timing, response freshness and partner-specific formatting.

## Which partners are supported

Adrasis connects to **the most well-known metasearch engines and B2B aggregators** in the market — the ones travellers see first when they search, and the ones B2B buyers reach through aggregator networks. The connector catalog is open-ended; new partners are added as their certification clears and they are configured per organization.

For the list of partners available to your organization (your organisation account), open *Connectors → Integration*.

## What you do as an operator

For each partner in this family, the operator workflow is the same as any other outbound channel:

1. **Activate the connector** for your organization.
2. **Configure your credentials** with the partner.
3. **Bind the properties** that should appear in the feed.
4. **Curate the mapping** — your rooms, rate plans, and meal plans translated into the partner's vocabulary.
5. **Decide which rate plans go.** Same per-channel visibility overlay you use everywhere. A "members only" rate plan can stay invisible on a metasearch engine; a *Non-Refundable Europe* plan can be the one the partner sees.

You manage all of this through the channel pages — same screens, same workflow as any other connector.

## Where bookings happen

Channels in this family do not transact bookings against Adrasis directly. They show your rates and route the click somewhere else:

* **Through the partner's own booking funnel** — the booking still lands in Adrasis (through a separate booking-inbound path negotiated per partner), but the click happened on the partner's site.
* **As a redirect to your direct booking** — the click goes to your website (or a partner-owned funnel) and creates a regular direct booking.

Either way, the partner's job ends at displaying rates. Bookings are handled by your normal booking screens.

## What is the same as any other channel

These channels behave like the rest:

* **Mapping is mapping.** Same curation page, same gap detection. Adragent can fill obvious matches.
* **Channel visibility is the same.** The per-channel restriction overlay decides what shows in which feed.
* **Status and health show up the same way.** The console's channel page tells you whether the feed is healthy, when the partner last polled, and where mapping gaps remain.

For an operator, "we publish to a metasearch engine" is the same kind of work as "we publish through a channel manager" — different partner, same shape on your screen.

## Where to next

* **The other outbound family** → [Outbound overview](/console/distribution/outbound.md)
* **How channels are configured generally** → [Channels](/console/distribution/channels.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/distribution/outbound/metasearch.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.