Blindfold operates PII processing nodes in multiple regions. You can select a region to ensure data residency compliance and minimize latency.Documentation Index
Fetch the complete documentation index at: https://docs.blindfold.dev/llms.txt
Use this file to discover all available pages before exploring further.
Available Regions
| Region | Endpoint | Location |
|---|---|---|
| EU (default) | https://eu-api.blindfold.dev | Europe |
| US | https://us-api.blindfold.dev | United States |
| Global (default) | https://api.blindfold.dev | Routes to EU |
If no region is specified, requests are routed to the EU region by default.
Selecting a Region
Python SDK
JavaScript / TypeScript SDK
CLI
MCP Server
Set theBLINDFOLD_REGION environment variable:
Direct API Calls (cURL)
Data Residency
When you select a region, your text data is processed entirely within that region:- EU region: PII detection and processing occurs on EU-based servers.
- US region: PII detection and processing occurs on US-based servers.
Your API key works across all regions. You do not need separate API keys per region.
Priority Order
The region is resolved in this order (highest priority first):- Explicit base URL (
base_url/baseUrl/--base-url) - always takes precedence - Region parameter (
region/--region/BLINDFOLD_REGION) - Default - routes to EU via
api.blindfold.dev
Default Behavior
| Configuration | Result |
|---|---|
| No region, no base URL | Routes to api.blindfold.dev (EU) |
region="eu" | Routes to eu-api.blindfold.dev |
region="us" | Routes to us-api.blindfold.dev |
base_url="https://custom.dev" + region="us" | Routes to https://custom.dev (base URL wins) |