API vs. Snowflake (Bulk)
The same fund-returns data is available two ways. Pick based on how you access it and whether you need redistribution.
This API — metered REST + MCP
Best when you want specific returns on demand: look up a fund, pull a watchlist, or wire fund
performance into an app or an AI assistant. You integrate over HTTP (or MCP), pay by tier, and get
point lookups — latest, a specific as_of date, or a specific calendar year.
Snowflake Marketplace — bulk dataset
The Fruit Stand fund-returns dataset delivers the entire history as analytic-ready tables directly in your Snowflake account: full daily trailing-returns history (100M+ rows) and all calendar years, queryable with SQL and joinable to your own data. Flat $250/month, and licensed for redistribution.
Side by side
| This API (REST + MCP) | Snowflake dataset | |
|---|---|---|
| Access pattern | Point lookups (latest / as_of / year) | Full history, arbitrary SQL |
| Best for | Apps, assistants, on-demand lookups | Analytics, backtests, bulk joins |
| Full daily history / date ranges | Not exposed (point lookups only) | ✅ Complete |
| Integration | HTTP + bearer key, or MCP | Snowflake share (no ETL) |
| Pricing | Free → Business tiers (Pricing) | $250/mo flat, unlimited |
| Redistribution | Business plan only (Licensing) | ✅ Included |
Rule of thumb
- Need a fund's returns inside your product or an AI workflow? → this API.
- Need the whole dataset for analysis, backtesting, or to redistribute? → the Snowflake dataset (or the Business plan, which adds redistribution to the API).
Many customers use both: the API for live product features, the Snowflake share for offline research.