Environments
Sandbox vs production: environment-specific API keys, base URLs, and usage guidelines.
Overview
Dark Matter provides two environments: production for live operations and sandbox for development and testing. Each environment has its own API keys, base URLs, and data isolation. Use sandbox for integration development and production for real transactions.
Production environment
The production environment hosts live ownership data and executes real transfers. All mutations are permanent and auditable. Production requires full KYC/AML and compliance onboarding. Use production only when you are ready for live operations.
Sandbox environment
The sandbox environment provides a safe space for development and integration testing. It supports the full API surface with in-memory SQLite, pre-seeded with Appendix E data (Megalith Frontier 2026 fund, 10 portfolio positions, 6 participants).
What sandbox supports today:
- Full API surface — all endpoints functional
- In-memory SQLite — fast, reset between sessions
- Pre-seeded data — Appendix E entities ready to use
POST /v1/reset— reset the database to initial seed state- Rights Engine evaluation with all 18 compliance checks
Not yet available:
- Persistent storage between deployments
- Production API keys (sandbox uses demo keys)
- Webhook delivery
- Multi-tenant isolation
Environment-specific API keys
API keys are scoped to a single environment. A production key cannot access sandbox, and vice versa. Generate separate keys for each environment in the DMTR console. Never use production keys in development or CI.
Base URLs
Production and sandbox use different base URLs. Production: https://api.dmtr.ai (or your configured production domain). Sandbox: https://sandbox-api.dmtr.ai (or equivalent). All API calls must target the correct base URL for the environment you are using.