> For the complete documentation index, see [llms.txt](https://docs.shredpay.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shredpay.xyz/developers/getting-started/environments.md).

# Environments

ShredPay provides production endpoints for external developers. Credentials are environment-specific and not portable.

| Environment | Purpose                             | API base                         | MCP endpoint                         | Console                        |
| ----------- | ----------------------------------- | -------------------------------- | ------------------------------------ | ------------------------------ |
| **Prod**    | Production. Real funds. SLA-backed. | `https://agent-api.shredpay.xyz` | `https://agent-api.shredpay.xyz/mcp` | `https://console.shredpay.xyz` |

## Chain availability

Prod operates on the following mainnet chains: Ethereum, Base, Arbitrum, Polygon, Optimism, BNB Chain. There is currently no testnet support.

Always query `GET /api/wallet/chains` for the authoritative list — chains may be added without a documentation update.

## Status and uptime

Subscribe to the status page at [status.shredpay.xyz](https://status.shredpay.xyz) for incident notifications.

## Per-environment configuration

When deploying your integration:

1. Create a sub-wallet in the [Console](https://console.shredpay.xyz).
2. Issue an API key bound to that sub-wallet.
3. Register your webhook endpoint and store the signing secret.
4. Update your application config.

API keys are scoped to a single sub-wallet group and cannot be reused across wallets.