The savings rate API that shows its work.
FDIC savings APYs, Treasury bill yields and DeFi staking rates as JSON, every row dated and sourced. Not open yet: say what you would build and you go first.
No card, no sales call. We email you when there is something to use. Privacy.
What a response looks like
Loading today's rates...The field names may still change. The numbers will not: they are read from the same file this site renders, so the example above is whatever the table says right now. verified_at is when that number was last confirmed against the bank's own page. expires_at is 45 days after it, and past that date the row leaves the table rather than going stale quietly.
What the rate API covers
| Endpoint | Covers | Rows | Refreshed | Source |
|---|---|---|---|---|
| /v1/savings | FDIC high-yield savings accounts | - | Twice daily | Each bank's own rate page |
| /v1/treasury | T-bill yields, 4-week to 1-year | - | Each business day | US Treasury daily curve |
| /v1/defi | Staking and stablecoin lending yields | - | Twice daily | DeFiLlama pools |
Savings is the hard one and the reason this exists. Treasury and DeFi are public feeds, normalised into the same shape so you can rank all three against each other in one pass.
Why this rate data is different
Rate data is easy to collect and hard to keep honest. A scraper that breaks does not throw an error. It returns last month's number, quietly, until someone puts it in front of a customer. Four rules exist to stop that, and they are the actual product:
- Read at the source. A rate is published only after being read from the bank's own page, anchored to the named product. Never the biggest number in a banner. Banks routinely advertise a CD or a promo more prominently than the savings rate.
- Dated on every row. You get verified_at and source_url with the number, so you can show your own users where it came from and how old it is.
- Expires at 45 days. A rate we cannot re-confirm drops out. The table gets shorter rather than wrong.
- Withheld when unsure. Banks whose pages we cannot read reliably are left off, famous ones included, until we can. A short honest list beats a long guessed one.
Ranking is by APY and is not for sale. No bank can pay to move up, be included, or delay bad news about its own rate. That policy is written down in the disclosures and it applies to the API exactly as it applies to the site.
Who asks for a savings rate API
AI agents and assistants
"What is the best savings rate right now" is a question models answer badly, because the training data is a year old and the web results are affiliate pages. A dated JSON row with a source link is something an agent can cite. An MCP server is on the list if enough people want it.
Personal finance products
Budgeting apps, cash management tools and advisors who want to tell a user their money is sitting at 0.4% while a comparable insured account pays over 4%, and show the number without promising anything they cannot back up.
Newsletters and content sites
A rate table that updates itself, so a post from March is not quoting March's rates in September. Every figure ships with the date attached, which is also what stops a stale one slipping past an editor.
Analysts and treasury teams
The gap between the deposit rates banks advertise and where Treasury actually is, tracked over time. Same shape across cash, government and on-chain yield, so the comparison is one query rather than three imports.
Access and cost
Right now
Nothing is billable and nothing is built. Requests get read by a person and answered by a person, which is the whole point of asking this early.
Tiers
There will be a free tier that is genuinely usable, and a paid tier for volume and support. The limits get set with the first few users rather than guessed at now.
Order
Access goes out in request order, and the endpoints that get built first are the ones people actually asked for. Say what you need and it counts.
Questions
What is a savings rate API?
A savings rate API returns current deposit account interest rates as structured data instead of a web page, so a product can show or compare them without a person copying numbers by hand. This one covers FDIC high-yield savings APYs, US Treasury bill yields and DeFi staking rates, and returns the date each number was verified along with a link to the page it was read from.
Is there an MCP server for AI agents?
Not yet, and it is the most asked for thing on the list. An MCP server would let Claude, ChatGPT or any compatible agent ask for current savings rates in plain English and get back a dated, sourced answer it can cite. If that is what you want, say so in your request.
When does it ship?
No date. The data pipeline behind it already runs daily, which is the expensive half. The rest is a read endpoint, keys and rate limiting. What decides the timing is whether enough people want it to be worth supporting properly, and this page is how we find out.
Can I show these rates in my own product?
That is the intended use. Terms will ask you to keep the source link and the date next to the number, because a rate without either is how people get misled. Reselling the raw feed is the one thing that will not be allowed.
Why are Amex and a few other big banks missing?
Some banks render their rate in the browser behind bot protection, so it cannot be read reliably. Those are left off rather than filled in from a third-party table that might be months old. The list of what is in and what is held back is on the status page.
Is this a rate everyone gets?
No, and the API will never claim otherwise. These are published rates for a named product. Balance tiers, minimums, promotional windows and eligibility still apply, and the fields that carry those come back with the row so you can show them too.
Do banks pay for placement?
Some bank links on the site may pay a referral fee. Ordering is by APY and no bank can buy position, inclusion, or a delay on its own rate falling. The API returns the same order the site shows, for the same reason.
What about CDs, money market accounts and credit unions?
Not covered today. Credit unions are the most requested addition and the most likely next one. If that is what you need, say so in your request and it moves up.
Get on the list
We reply to ask what you are building. That answer decides what gets built first.