Choose your environment
Use the sandbox to explore the experience and the Partner API to connect your business.
Thesauros exposes two API contracts. Choose the contract first, then configure the matching URL, key and SDK client.
| Sandbox | Partner API | |
|---|---|---|
| Purpose | Explore the Earn lifecycle and API behavior | Integrate attribution, reporting and operations for a partner account |
| Main resources | Vaults, yield, simulated positions, users, webhooks and analytics | Partners, attributed users, activity, yield history, revenue, webhooks and reconciliation |
| Position creation | POST /positions creates a simulated position |
No public POST /positions settlement operation in this API contract |
| Assets in the contract | USDC, USDT |
USDC, USDT0 |
| Storage | In-process simulation; state can reset on restart | PostgreSQL-backed records; data depends on the deployment's connected sources |
| Connection | Sandbox base URL | Base URL assigned during partner onboarding |
| Schema | Sandbox OpenAPI | Partner OpenAPI |
A key prefix does not select the backend
tsk_test_ and tsk_live_ are key namespaces. The server URL determines which implementation receives your request. A live-prefixed key sent to the sandbox does not turn the simulator into blockchain settlement.
Configure separate environment variables and credentials for each deployment. Keep production partner credentials out of a browser-based sandbox session.
Read the source of a number
The developer console can combine operational data with sandbox views. Identify whether a value is a protocol observation, a partner-scoped calculation, or a simulated example before using it in customer reporting.
Historical APY describes recorded rates. Revenue endpoints calculate estimates from balances, APY and fee assumptions. Neither is a settlement receipt. Use the data and reporting guide to choose the right source.
Move from sandbox to an integration
- Validate the product journey using sample positions.
- Connect a partner account and its scoped reporting API.
- Agree the asset, network, vault deployment and wallet-signing flow.
- Validate transactions, customer accounting and operating controls against that configuration.
The launch guide turns these into reviewable deliverables.