Credentials

The trading surface is consumer-only: you bring your own keypairs and the SDK signs trades with them. Two self-service paths generate those keypairs and register them on-chain — both emit the same canonical TRIA_TRADE_* .env block, so your downstream config never changes.

What each credential is

How to obtain them

A. In-app — Settings → API Keys (recommended)

Turnkey-signed; no seed phrase. In the Tria web wallet:

1. Go to Settings → API Keys and pick a venue (Hyperliquid and/or Decibel), set a name + expiry (default 90 days, max 180, or "No expiry").
2. Confirm — Turnkey signs the on-chain setup (builder-fee approval + agent / delegate registration).
3. A one-time modal shows the keys. Click "Copy as … .env block" — already in canonical TRIA_TRADE_* form:

# Decibel block (HL block is the analogous TRIA_TRADE_HL_* set)
TRIA_TRADE_NETWORK=mainnet
TRIA_TRADE_DECIBEL_DELEGATE_KEY=0x…
TRIA_TRADE_DECIBEL_APTOS_OWNER_ADDRESS=0x…
TRIA_TRADE_DECIBEL_SUBACCOUNT_ADDRESS=0x…   # informational; SDK re-derives
TRIA_TRADE_DECIBEL_NODE_API_KEY=geomi-…

The keys are shown once — copy them then. The page also lists your existing agents / delegates (with expiry) and lets you revoke any of them.

B. CLI wizard — npx tria-trade-provision

Derives keys from a seed phrase. Interactive walkthrough with two personas:

• Tria user — paste your seed phrase from Settings → Account → Recover from Turnkey. The wizard derives HL (secp256k1) + Aptos (Ed25519) keys via standard BIP-44 paths and never touches your existing in-app agents.
• Fresh user — bring your own master keys; the wizard walks through Geomi signup, gas-station setup, and Aptos USDC bridging.

npx tria-trade-provision

It mints the agent / delegate, approves the Tria builder, funds collateral, and emits a ready-to-use .env.

Importing the keys

However you generated the block, it imports the same way — the names match the SDK and MCP exactly.

import { TriaClient } from '@tria-sdk/api-trading'

const client = new TriaClient({
  network: process.env.TRIA_TRADE_NETWORK as 'mainnet',
  hl: {
    agentPrivateKey: process.env.TRIA_TRADE_HL_AGENT_KEY!,
    accountAddress: process.env.TRIA_TRADE_HL_ACCOUNT_ADDRESS!,
  },
  decibel: {
    delegatePrivateKey: process.env.TRIA_TRADE_DECIBEL_DELEGATE_KEY!,
    aptosOwnerAddress: process.env.TRIA_TRADE_DECIBEL_APTOS_OWNER_ADDRESS!,
    nodeApiKey: process.env.TRIA_TRADE_DECIBEL_NODE_API_KEY!,
  },
})

Expiry

Both venues support an expiry. The wizard and the in-app flow default to 90 days; pass a custom window 1–180, or none/0 for no expiry.

• Decibel — --decibel-delegate-ttl-days <1–180 | none>. An explicit timestamp on delegate_trading_to.
• Hyperliquid — --hl-agent-ttl-days <1–180 | none>. HL has no expiry field on approveAgent; the expiry is encoded in the agent name as <name> valid_until <unix-seconds>.

You can always revoke early from Settings → API Keys.