Teahouse Finance website screenshot

Teahouse Finance

Teahouse Finance, founded in 2021, is a multi-strategy DeFi asset-management platform that sits as a simplified layer above protocols such as Uniswap V3, removing the complexity of managing liquidity and crypto assets. It runs audited smart-contract vaults across multiple chains — LP Vaults, Portfolio Vaults, the Easy-Earn delta-neutral strategy, and Tea-REX — for both individual and enterprise clients. Teahouse exposes a public read-only Vault API (HTTP/JSON) over its permissionless vaults: the vault catalog, per-vault performance time series (TVL, fee APR, share-token APR, share price), and account/vault share transaction logs. Vaults are of type V3Pair (a single Uniswap V3 LP pair) or V3Port (a portfolio of multiple positions). Surfaced as a portfolio company of Pantera Capital and enriched into the API Evangelist network from its published developer documentation.

Teahouse Finance publishes 3 API contracts indexed on the APIs.io network: Logs API, Performance API, and Vaults API. Tagged areas include Company, Crypto, DeFi, Blockchain, and Vault.

Teahouse Finance’s developer surface includes documentation, API reference, getting-started guide, engineering blog, support, signup flow, authentication, and 13 more developer resources.

35.2/100 thin ▬ flat Agent 26/100 agent aware Front door AI 1/6 silent saas Full breakdown ↓
scored 2026-10-09 · rubric v0.23.0
1 published contract
CompanyCryptoDeFiBlockchainVaultLiquidity ManagementAsset ManagementUniswapWeb3

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-10-09 · rubric v0.23.0
Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics does not apply to this provider. The published contracts declare no write operations, and a read-only API cannot create-or-update. The facet is excluded from this provider's denominator entirely — not scored zero. A reference or data API is not deficient for being unable to upsert.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/teahouse: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 3

Individual APIs this provider publishes, each with its own machine-readable definition.

Teahouse Finance Logs API

Share transaction logs

Teahouse Finance Performance API

Vault performance time series

Teahouse Finance Vaults API

Vault catalog and metadata

Open Collections 4

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Teahouse Vault Logs API

OPEN COLLECTION

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Teahouse Vault Overlay

2 actions · update · teahouse-vault-openapi.yml

UNRECORDED

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Teahouse Authentication

apiKey · 1 scheme

SECURITY

Teahouse Domain Security

TLSv1.3 · DNSSEC · DMARC

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Company 2

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: teahouse
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-09-03'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/teahouse.png
name: Teahouse Finance
description: 'Teahouse Finance, founded in 2021, is a multi-strategy DeFi asset-management platform that sits as a simplified
  layer above protocols such as Uniswap V3, removing the complexity of managing liquidity and crypto assets. It runs audited
  smart-contract vaults across multiple chains — LP Vaults, Portfolio Vaults, the Easy-Earn delta-neutral strategy, and Tea-REX
  — for both individual and enterprise clients. Teahouse exposes a public read-only Vault API (HTTP/JSON) over its permissionless
  vaults: the vault catalog, per-vault performance time series (TVL, fee APR, share-token APR, share price), and account/vault
  share transaction logs. Vaults are of type V3Pair (a single Uniswap V3 LP pair) or V3Port (a portfolio of multiple positions).
  Surfaced as a portfolio company of Pantera Capital and enriched into the API Evangelist network from its published developer
  documentation.'
url: https://raw.githubusercontent.com/api-evangelist/teahouse/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- pantera-capital
x-tier: profiled
x-tier-reason: has-public-api
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-21'
tags:
- Company
- Crypto
- DeFi
- Blockchain
- Vault
- Liquidity Management
- Asset Management
- Uniswap
- Web3
tags_raw:
- Company
- Crypto
- DeFi
- Blockchain
- Vaults
- Liquidity Management
- Asset Management
- Uniswap
- Web3
apis:
- aid: teahouse:teahouse-logs-api
  name: Teahouse Finance Logs API
  description: Share transaction logs
  humanURL: https://docs.teahouse.finance/docs/vault-api
  baseURL: https://vault-content-api.teahouse.finance
  tags:
  - Logs
  properties:
  - type: OpenAPI
    url: openapi/teahouse-logs-api-openapi.yml
  - type: Documentation
    url: https://docs.teahouse.finance/docs/vault-api
  - type: Authentication
    url: authentication/teahouse-authentication.yml
- aid: teahouse:teahouse-performance-api
  name: Teahouse Finance Performance API
  description: Vault performance time series
  humanURL: https://docs.teahouse.finance/docs/vault-api
  baseURL: https://vault-content-api.teahouse.finance
  tags:
  - Performance
  properties:
  - type: OpenAPI
    url: openapi/teahouse-performance-api-openapi.yml
  - type: Documentation
    url: https://docs.teahouse.finance/docs/vault-api
  - type: Authentication
    url: authentication/teahouse-authentication.yml
- aid: teahouse:teahouse-vaults-api
  name: Teahouse Finance Vaults API
  description: Vault catalog and metadata
  humanURL: https://docs.teahouse.finance/docs/vault-api
  baseURL: https://vault-content-api.teahouse.finance
  tags:
  - Vault
  tags_raw:
  - Vaults
  properties:
  - type: OpenAPI
    url: openapi/teahouse-vaults-api-openapi.yml
  - type: Documentation
    url: https://docs.teahouse.finance/docs/vault-api
  - type: Authentication
    url: authentication/teahouse-authentication.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Overlay
  url: overlays/teahouse-vault-overlay.yaml
- type: DomainSecurity
  url: security/teahouse-domain-security.yml
- type: Website
  url: https://teahouse.finance/
- type: DeveloperPortal
  url: https://docs.teahouse.finance/docs
- type: Documentation
  url: https://docs.teahouse.finance/docs
- type: APIReference
  url: https://docs.teahouse.finance/docs/vault-api
- type: GettingStarted
  url: https://docs.teahouse.finance/docs/for-developers/vault-api-introduction
- type: GitHubOrganization
  url: https://github.com/TeahouseFinance
- type: Blog
  url: https://medium.com/@teahouse.finance
- type: Support
  url: https://docs.teahouse.finance/docs/other-information/contact-us
- type: SignUp
  url: https://vault.teahouse.finance/
- type: Authentication
  url: authentication/teahouse-authentication.yml
- type: ErrorCatalog
  url: errors/teahouse-problem-types.yml
- type: Conventions
  url: conventions/teahouse-conventions.yml
- type: DataModel
  url: data-model/teahouse-data-model.yml
- type: Lifecycle
  url: lifecycle/teahouse-lifecycle.yml
- type: Conformance
  url: conformance/teahouse-conformance.yml
- type: X-MCPServerCandidate
  url: mcp/teahouse-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/teahouse-llms.txt
- type: AgentSkill
  url: skills/_index.yml
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 14
  pass: local-v1

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/teahouse"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/teahouse/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/teahouse/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.