Skip to main content
For partner data access, endpoint details, authentication, allowlisting, and response contracts, contact contact@superearn.io.

​
1. Integration surfaces

SuperEarn integrations have two separate surfaces:
  • Write path via Kaia contracts, primarily through SuperEarnRouter
  • Read/data path via SuperEarn-supported data surfaces made available to approved integrations
The public docs describe the on-chain write path and the concepts an integrator should understand. They intentionally do not publish backend API routes, internal indexing details, authentication requirements, or response schemas.

​
2. Write path

For deposits and withdrawals, use the Kaia contract flow documented in: At a high level:
  1. Users deposit Kaia USDT through SuperEarnRouter.
  2. The router mints or redeems EarnUSDT / Super Vault shares.
  3. Redemptions create a cooldown request before USDT is claimable or delivered.
  4. Integrations should quote through the router and apply explicit minSharesOut / minAssetsOut protection.
Do not call CooldownVault deposit or redeem entrypoints directly from user-facing integrations. Those flows are restricted to protocol contracts. Claims are permissionless, but are normally handled by protocol keepers.

​
3. Read/data path

Most integrations need read-side data such as:
  • vault discovery and display metadata
  • current and historical yield information
  • user or wrapper-contract position views
  • pending redemption status
  • transaction and earnings history
  • allocation or reporting data for partner dashboards
Subgraph-backed data can include vault metadata, share price updates, account share positions, position changes, deposit and redemption lifecycle events, strategy reports, vault updates, fee reports, and token metadata. The public docs do not publish subgraph endpoints, entity schemas, query documents, or deployment identifiers. The exact supported data surface depends on the integration type, environment, access model, and operational requirements. Contact contact@superearn.io with your integration details to receive the current endpoint contract and access instructions.

​
4. Token model

Keep these token concepts separate in your product and accounting model:
ConceptDecimalsBuilder usage
USDT6Asset users deposit and expect to see in portfolio totals.
seCDV / CooldownVault shares6Intermediate vault token used inside the protocol flow.
EarnUSDT / Super Vault shares6Shares representing the user’s Super Vault position.
KAIA18Native gas token for Kaia transactions.
Use a USDT-centric user experience. Users deposit USDT and hold an EarnUSDT position whose value changes with the Super Vault share price.

​
5. Before launch

Before shipping a production integration:
  1. Confirm current contract addresses and supported write methods.
  2. Confirm whether your read/data access is approved and which surface you should use.
  3. Confirm authentication, allowlisting, rate limits, and data freshness expectations.
  4. Confirm how endpoint changes, deprecations, and incident notices will be communicated.
  5. Test deposit, redeem, cooldown, and data reconciliation flows with the SuperEarn team.