> ## Documentation Index
> Fetch the complete documentation index at: /llms.txt
> Use this file to discover all available pages before exploring further.

# Environment setup

> Staging and production hosts, chains, and staging contracts for integration.

Use **staging** for Protocol V2 integration today (Base Sepolia). Production hosts exist in infra; settlement and contract addresses are issued when your account is cut over. Do not point payment traffic at production until SohoPay confirms cutover.

> [!NOTE]
>
> Do not use `api-sandbox.sohopay.xyz`. That host is not the current API.

> [!WARNING]
>
> Production settlement (Protocol V2 on Base mainnet) is **not** enabled for general integrators yet. The production column below is for hostnames and future cutover planning only.

## Hosts

Edit hostnames in `config/hosts.json` in this repo, then run `node deploy/sync-hosts.mjs` so MDX variables and the OpenAPI server list stay in sync.

> [!NOTE]
>
> Staging API DNS is **`staging.api.sohopay.ai`** (`staging` before the service label), not `api.staging.sohopay.ai`. The facilitator base is `https://staging.api.sohopay.ai/api/v1/facilitator`.

| Surface | Staging | Production |
| - | - | - |
| API | `https://staging.api.sohopay.ai` | `https://api.sohopay.ai` |
| MCP | `https://staging.mcp.sohopay.ai/mcp` | `https://mcp.sohopay.ai/mcp` |
| App and consent | `https://staging.sohopay.ai` | `https://app.sohopay.ai` |
| Agent consent path | `https://staging.sohopay.ai/agent/authorize` | `https://app.sohopay.ai/agent/authorize` |
| Borrower portal | `https://staging.borrower.sohopay.ai` | `https://borrower.sohopay.ai` |
| Install | `https://staging.sohopay.ai/install` | `https://app.sohopay.ai/install` |
| Agent skills | `https://agents.sohopay.ai/skills/v1/` (staging skill suffix `-staging`) | `https://agents.sohopay.ai/skills/v1/` (production `setup.md`, `mcp-connect.md`) |
| Docs | `https://staging.docs.sohopay.ai` | `https://docs.sohopay.ai` |

Facilitator routes:

* Staging: `https://staging.api.sohopay.ai/api/v1/facilitator/`
* Production: `https://api.sohopay.ai/api/v1/facilitator/`

## Chain and token

> [tab] Staging (integrate)
>
> | | Value |
> | - | - |
> | Network | Base Sepolia |
> | Chain id | `84532` |
> | CAIP-2 | `eip155:84532` |
> | Asset | USDC (protocol mock) `0xa5807998c65c16d92048Cbf50E98955d0c85C700` |
> | Settlement | `SohoSettlementV2` `0xd4C9919cbaa3Cd9D21F7a251CBA4DFFfe2E77c44` |
> | Merchant registry | `SohoMerchantRegistry` `0x1a7AAfEE379F249e9D86Ef7fc4cE401c5516a264` |
> | Lender vault | `SohoVault` `0x817a2e8A167E46926C449c527B818d511Aa23ef8` |
>
> Protocol V1 `SohoSettlement` is not deployed on staging. Explorer: [sepolia.basescan.org](https://sepolia.basescan.org).

> [tab] Production (cutover)
>
> | | Value |
> | - | - |
> | Network | Base mainnet |
> | Chain id | `8453` |
> | CAIP-2 | `eip155:8453` |
>
> Mainnet settlement contract addresses are not published here until production V2 is enabled for your merchant or borrower. SohoPay issues them at cutover.

## What you install

Agents need a host that speaks remote MCP (Cursor, Claude, or another OAuth-capable client) and, for signing, [`@sohopay/agent-signer`](/sdks/agent-signer). Merchants need an HTTP client that can `POST` the capture body and poll status. Neither path needs a SohoPay REST SDK.

## Next steps

> [card] [Authentication](/authentication.md)
>
> OAuth scopes and merchant API keys.

> [card] [Quickstart](/quickstart.md)
>
> Run the agent or merchant track.
