Tychi Wallet API integration (Web3 multi-chain OpenData)

Deliverables checklist

• OpenAPI 3.1 specification of every Tychi-derived endpoint
• Protocol report covering Tychi's multi-chain RPC, indexer, and UGF flows
• Runnable source for balance, transaction, swap, and gas APIs (Python and Node.js)
• Webhook delivery for incoming transfers and confirmed swaps
• Automated test suite covering EVM, Solana, and Sui sample wallets
• Compliance notes (FATF Travel Rule fields, GDPR data-minimization checklist)

Two engagement models

Source-code delivery starts at $300 — you receive the runnable source plus full documentation and pay only when the build clears your acceptance tests. Pay-per-call billing is available for teams that prefer to consume our hosted Tychi-mirrored API and pay per request, with no upfront fee.

Both models keep self-custody intact: signing always happens with keys you (or the end user) control.

1. Crypto-native accounting export

A Web3 startup runs operations across Base, Solana, and Sui from one Tychi Wallet. We pull the unified transaction-history API on a daily schedule, normalize each event into double-entry rows, and post them to QuickBooks or NetSuite. Mapped fields: tx_hash, chain_id, from/to, token_symbol, amount, usd_value_at_block, gas_paid_native, gas_paid_ugf_base_eth. This is an OpenData use case: structured wallet activity flows out of Tychi and into the team's existing finance stack.

2. AML & FATF Travel Rule monitoring

A regulated VASP using Tychi as an internal operations wallet streams transactions through a webhook the moment they're confirmed. Each event is enriched with sanctions screening, risk scores, and counterparty heuristics, then forwarded to the firm's transaction-monitoring system. The Travel Rule originator/beneficiary fields are populated where counterparties are known, and edge cases are queued for analyst review — an OpenFinance pattern adapted to on-chain rails.

3. Cross-chain swap best-execution logging

A trading desk wants to compare Tychi's in-app swap routing (including TON via Omniston routing) against external aggregators. Our API records every quote and final execution with route legs, slippage, and effective price. Downstream, the desk computes implementation shortfall and audits routing decisions — a concrete OpenFinance / best-ex use case.

4. Universal Gas cost allocation

A multi-team Web3 organization shares one Universal Gas balance funded in Base ETH. We expose the gas-spend feed grouped by chain and by signing address, so finance can charge each project's gas usage back to its cost center. The feed combines UGF debits with per-chain native gas where applicable.

5. Embedded portfolio inside a partner app

A neobank or fintech wants to surface a customer's Tychi Wallet portfolio after the customer signs an authorization. Our SDK calls the balances and AI Token Analyzer endpoints on the partner's backend, while the user's keys never leave their device. The partner app shows holdings, trending tokens, and recent activity, all fed by the same data Tychi exposes natively.

1. Authorization and address binding (OAuth-style consent)

POST /api/v1/tychi/auth/bind
Content-Type: application/json
Authorization: Bearer <PARTNER_API_KEY>

{
  "user_ref": "partner-user-9931",
  "signed_message": "0x9b...c4",         // SIWE / SIWS signed payload
  "address":        "0xabc...123",
  "chain_id":       8453,                  // Base
  "scopes":         ["balances", "txs", "ugf.read"]
}

200 OK
{
  "binding_id": "bind_01HXY...",
  "expires_at": "2026-08-01T00:00:00Z",
  "scopes":     ["balances", "txs", "ugf.read"]
}

2. Multi-chain transaction statement

GET /api/v1/tychi/statement
  ?binding_id=bind_01HXY...
  &chains=ethereum,base,solana,sui,ton
  &from=2026-04-01&to=2026-04-30
  &cursor=eyJwYWdlIjoyfQ
Authorization: Bearer <PARTNER_API_KEY>

200 OK
{
  "items": [
    {
      "tx_hash":       "0x4e...91",
      "chain":         "base",
      "direction":     "out",
      "counterparty":  "0xdef...456",
      "token":         "USDC",
      "amount":        "120.50",
      "usd_value":     "120.50",
      "gas_paid_ugf":  "0.000087",
      "gas_chain":     "ETH-on-Base",
      "block_time":    "2026-04-15T09:21:11Z"
    }
  ],
  "next_cursor": "eyJwYWdlIjozfQ"
}

3. Webhook for confirmed activity

// Outbound webhook signed with HMAC-SHA256
POST https://partner.example.com/hooks/tychi
X-Tychi-Signature: t=1714..,v1=8b...
Content-Type: application/json

{
  "type":  "tx.confirmed",
  "binding_id": "bind_01HXY...",
  "chain": "solana",
  "tx_signature": "5KJp...",
  "delta": [
    { "token": "SOL",  "amount": "-0.214" },
    { "token": "JTO",  "amount": "+128.0" }
  ],
  "received_at": "2026-04-15T09:22:03Z"
}

// Verify before processing:
// hmac_sha256(secret, "t.body") == v1

4. Error handling & idempotency

// Every mutating call accepts an Idempotency-Key.
// Read endpoints return RFC 7807 problem JSON on failure:
{
  "type":    "https://errors.openfinance-lab.com/binding-expired",
  "title":   "Binding expired",
  "status":  401,
  "detail":  "Re-prompt the user to sign a fresh SIWE/SIWS message.",
  "binding_id": "bind_01HXY..."
}

// Recommended retry: exponential backoff on 5xx, never on 4xx.

Regulatory alignment

Tychi Wallet is non-custodial software, so the integration sits under the regimes that apply to your business, not Tychi's. For EU-facing deployments we align with the EBA's Markets in Crypto-Assets (MiCA) guidance on crypto-asset service providers, the FATF Travel Rule for transfers above the de minimis threshold, and GDPR data-minimization principles when persisting addresses or counterparty metadata. US deployments respect FinCEN's MSB rules where applicable; APAC deployments map to local regimes such as MAS PSN02. We never claim Tychi itself is a regulated venue — we document the regulatory surface that your use of the data triggers.

Privacy & key handling

• No mnemonics, no private keys, no seed phrases ever leave the user's device.
• SIWE / SIWS signed messages establish authorization; partners can revoke at any time.
• PII fields are stored only when contractually required and are encrypted at rest with envelope keys.
• Logs retain hashed binding identifiers — never raw addresses unless your retention policy allows it.
• All transit secured with TLS 1.3 and HSTS; webhooks signed with HMAC-SHA256.

About OpenFinance Lab

We are an independent technical studio focused on App protocol analysis, authorized API integration, and OpenData / OpenFinance / OpenBanking solutions. Our team has shipped integrations for retail banking apps, payment rails, exchanges, and Web3 wallets, with hands-on experience in self-custody flows, multi-chain RPC plumbing, and regulator-grade audit trails.

• Web3 wallet integrations across EVM, Solana, Sui, TON, TRON, and Bitcoin
• OpenBanking-style APIs for fintech and accounting platforms
• Custom Python / Node.js / Go SDKs and end-to-end test harnesses
• Full pipeline: protocol analysis → build → validation → compliance review
• Source code delivery from $300 — runnable API source plus documentation; pay after delivery upon satisfaction
• Pay-per-call API billing — access our hosted endpoints and pay only per call, no upfront cost

Contact

Send your target app and concrete requirements through our contact page; we usually reply within one business day.

Contact page

Engagement workflow

1. Scope confirmation: which Tychi-derived data you need (balances, transactions, swaps, UGF) and which chains.
2. Protocol analysis and API design (2–5 business days, complexity-dependent).
3. Build, internal validation against Tychi sample wallets, plus smoke tests on EVM, Solana, and Sui (3–8 business days).
4. Documentation, OpenAPI spec, runnable samples, and Postman collection (1–2 business days).
5. Typical first delivery: 5–15 business days; third-party approvals or custom auth flows may extend timelines.

FAQ

Does Tychi Wallet expose a public API I can call directly?

What multi-chain coverage do you support?

How do you handle private keys and self-custody?

How long does delivery take and what does it cost?