Provider terms
When using Gateway, your requests are routed to third-party AI providers and execution hosts. You are responsible for complying with the terms of service and usage policies of each provider that serves your requests.
The table below lists the vendors Gateway routes to. Country / Region indicates where the vendor’s serving infrastructure is located, which feeds geo-location routing on each org.
It is maintained by hand, so GET /v1/vendors is the authoritative list of vendors serving traffic right now, and a vendor can appear there before its row lands here. A vendor is also a different thing from a model author: Llama, Qwen, and DeepSeek models reach you through the vendors below rather than through their authors, so read the vendors block on a model in GET /v1/models to see whose terms apply to a given route.
It is your responsibility to ensure that your use of models through Gateway complies with the applicable provider’s terms. Merge does not assume liability for violations of third-party provider policies.
Region-based routing
Use the Country or Region columns to drive vendor allow / deny lists for data-sovereignty requirements:
- Country codes are ISO-3166 alpha-2 (for example
US,FR,CA) - Regions are coarse buckets used by Gateway:
NA,EU,APAC,CN
For example, to restrict your org to EU-hosted vendors only, add EU to your org’s allowed_regions. See Geo-location routing for the full configuration model.
Zero data retention
Vendor eligibility for ZDR is tracked dynamically in Gateway’s catalog. Call GET /v1/models and read each model’s zero_data_retention field to see exactly which routes qualify under your org’s ZDR toggle. See Zero data retention for the full feature description.