Discover gtoken yield sources

Call the gtoken catalogue before configuring either a direct integration or a fee wrapper. Each row identifies a gtoken yield source and the backing vault contract used to obtain and redeem its tokens.

List the catalogue

curl https://sandbox.groundtech.co/v2/gvaults/yield-sources \
  -H "Authorization: Bearer $GROUND_API_KEY"

The response is an unpaginated integration manifest.

{
  "data": [
    {
      "id": "ground-ustb-vault",
      "name": "Ground USTB gVault",
      "chain": "ethereum_sepolia",
      "contractAddress": "0x7DB59Ed654aE4b3756eA81803Ff32528eA907DCa",
      "asset": {
        "symbol": "USDC",
        "contractAddress": "0x1c7d4b196cb0c7b01d743fbc6116a902379c7238",
        "decimals": 6
      },
      "interface": "ground_ustb_v1"
    }
  ]
}

Persist the integration fields

Store these values per environment:

Field	Use
`id`	`gVaultId` in access and fee-wrapper API calls
`chain`	Network selection and transaction validation
`contractAddress`	Direct onchain vault address
`shareTokenAddress`	Separate TIP-20 share token for `tempo_earn_v1`
`interface`	Contract-interface and operation-flow selection
`asset`	Deposit-token symbol, contract address, and decimals

Always verify asset() onchain against the manifest before requesting an ERC-20 approval.

Select by capability

Use the interface field to select the ABI for the returned contract. The gtoken contracts page links to the verified deployed contracts, where Etherscan exposes the current ABI and read methods. An USTB-style source can expose synchronous deposits and withdrawals plus queued redemptions. A Centrifuge-style source exposes request/claim lifecycles and may require the configured Ground router for deposits. A tempo_earn_v1 source uses a Tempo Earn vault and a separate TIP-20 share token. Its access permission governs share transfers and redemptions as well as deposits. Use this source for direct gVault integration; it is not a Portfolio Wallet or MicroVault allocation target. It appears in discovery only after its restricted deployment has been activated. Never copy IDs or addresses between sandbox and production. Fetch and validate the catalogue after changing API base URL or chain configuration. See the complete schema in List gtoken yield sources.

Getting Started

Integration Guides

Integration Examples

Operations

Resources

API Reference

Discover gtoken yield sources

List the catalogue

Persist the integration fields

Select by capability

​List the catalogue

​Persist the integration fields

​Select by capability

List the catalogue

Persist the integration fields

Select by capability