For the CardSavvy API and Model Context Protocol (MCP) server.
Last updated: 2026-07-30
These API Terms govern access to the CardSavvy API, including the MCP server at card-savvy.com/mcp (together, the "API"). They supplement the Terms of Service and the Privacy Policy. Where the Terms of Service restrict use of website materials to personal, non-commercial viewing, these API Terms control instead for the API.
You accept these API Terms when you create an API token or when you make a request to the API, whichever happens first. If you are accepting on behalf of an organization, you represent that you are authorized to bind it, and "you" refers to that organization.
Subject to these API Terms, Mount Si Labs LLC grants you a non-exclusive, non-transferable, revocable license to call the API and to display its responses within your own product or workflow, including for commercial purposes.
There is no fee for this today, for personal or commercial use. We are not describing a free tier of a paid product; there is no paid product.
We do reserve two things. Mount Si Labs may require a separate written agreement for high-volume use, or for redistributing API responses at scale, and may decline to enter one. And these API Terms can change.
If we make a material change to these terms, holders of an active API token get at least 30 days' notice by email before it takes effect for them. That is the practical reason to create a token even where the tools you use do not require one: it is how we reach you.
You may not:
as_of, source_url, or disclaimer fields when redisplaying card terms. Those fields are how an end user can tell how fresh a number is and where it came from.Where you display card terms or optimization results obtained from the API to end users, attribute them to CardSavvy and preserve the verification date returned with the data. Attribution does not imply that CardSavvy endorses your product.
Card terms change. Responses carry an as_of verification date, and a null value means the record has not been verified rather than that it is current. The API is provided as-is, and you are responsible for verifying terms with the issuer before your users act on them.
We publish current rate limits on the API documentation page and may change them. We may suspend or revoke a token, or terminate your access, at any time and without notice, for a breach of these API Terms, for abuse, or to protect the stability of the service. You may stop using the API at any time and revoke your own tokens from your profile.
This section is about a specific token or a specific user. Changes to these terms generally are covered by section 14, which carries a notice period.
Requests may include your users' card holdings and spending by category. CardSavvy does not log API request arguments. Usage records capture the tool name, a hash of the inputs, and timing only. See the Privacy Policy for detail. You are responsible for having the rights and disclosures necessary to send us any data about your users.
CardSavvy receives no affiliate or advertising compensation today, and API rankings reflect computed value only. Outbound links in API responses point at the card issuer. If that ever changes, we will disclose it, and it will not change the math.
The API is provided on an "as is" and "as available" basis. Mount Si Labs disclaims all warranties, express or implied, including implied warranties of merchantability, fitness for a particular purpose, non-infringement, and any warranty of uninterrupted or error-free operation.
To the maximum extent permitted by law, Mount Si Labs will not be liable for any indirect, incidental, special, consequential, or exemplary damages, or for lost profits, revenue, or data, arising out of your use of the API, even if advised of the possibility. Our total aggregate liability arising out of or relating to the API will not exceed one hundred US dollars (US$100), which reflects that the API is provided free of charge.
You will indemnify and hold harmless Mount Si Labs from claims arising out of your use of the API, your product, or your breach of these API Terms.
We may assign these API Terms to a successor in interest in connection with a merger, acquisition, reorganization, or sale of assets. You may not assign them without our prior written consent.
These API Terms are governed by the laws of the State of Washington, without regard to its conflict-of-law rules, and any dispute will be brought exclusively in the state or federal courts located in King County, Washington.
We may update these API Terms and will revise the date above when we do. Continuing to call the API after a change takes effect means you accept the revised terms.
For a material change, holders of an active API token get at least 30 days' notice by email first, as described in section 2. That notice period is about changes to these terms. It does not limit our ability to suspend or revoke a specific token for abuse or to protect the service, which section 6 covers and which can happen immediately.
Questions about these API Terms should be sent to support@card-savvy.com.