For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
Resources
Log inGet a demo
GuidesModelsAPI reference
GuidesModelsAPI reference
    • Get started
    • Install skills
  • Features
    • Projects
    • Management API keys
    • Cost governance and savings
    • Tool calling
    • Web search
    • Context compression
  • Security & Compliance
    • Customer blocklist
    • Geo-location routing
    • Prompt injection protection
    • Data loss prevention
    • Audit trail
    • Roles and permissions
    • Zero data retention
    • Provider terms

Get started

  • Overview
  • Introduction
  • Unified API
  • Linked Account
  • Merge Link
  • Use cases

Implementation

  • Sandboxes
  • SDKs
  • API access
  • Syncing data
  • Writing data
  • Data minimization
  • Supplemental data
  • Errors
  • Integration metadata

API reference

  • ATS
  • HRIS
  • Accounting
  • Ticketing
  • CRM
  • File Storage
  • Knowledge Base
  • Chat

Resources

  • Help Center
  • Merge.dev
  • Changelog
© Merge 2026Terms of usePrivacy policy
UnifiedAgent HandlerGateway
UnifiedAgent HandlerGateway
Resources
Log inGet a demo
On this page
  • Region-based routing
  • Zero data retention
Security & Compliance

Provider terms

Review the terms of service and hosting region for each AI provider available through Gateway
Was this page helpful?
Previous

Zero data retention

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 every provider Gateway can route to today. Country / Region indicates where the vendor’s serving infrastructure is located, which feeds geo-location routing on each org.

ProviderCountry / RegionTerms of Service
OpenAIUS / NAServices Agreement
AnthropicUS / NACommercial Terms
Google (Gemini)US / NAGemini API Terms
AWS BedrockUS / NAService Terms
Azure OpenAIUS / NAProduct Terms
xAIUS / NAEnterprise Terms of Service
CohereCA / NATerms of Use
Fireworks AIUS / NATerms of Service
ParasailUS / NATerms of Service
MistralFR / EUTerms of Service
Moonshot AICN / CNKimi OpenPlatform Terms
Z.AICN / CNTerms of Service
MinimaxCN / CNTerms of Service

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.