> Fetch https://askmiles.ai/llms.txt first: it indexes every public Miles capability. This file is the markdown twin of https://askmiles.ai/docs/trust.

# Trust

Where the data comes from, how it is maintained, and how Miles makes money, for a developer deciding whether to build on it.

## What you are building on

Every number a tool returns comes from a maintained dataset with a recorded review history. [How the data is maintained](https://askmiles.ai/how-the-data-is-maintained) describes the sources, the review cadence, and what a change looks like. [How Miles makes money](https://askmiles.ai/how-miles-makes-money) describes the referral model and why a referral link is never an input to a recommendation.

## What that means for an integration

- A card, transfer partner or valuation you read today is the same one Miles' own chat reads; there is no separate developer copy.
- The keyless [catalog API](https://askmiles.ai/docs/catalog/endpoints) returns the free schema, which is the same for every caller. Account-level figures, such as a user's own multipliers and ongoing value, come only through the MCP tools on that user's grant.
- A tool never spends a Miles model call, so what an agent gets back is data and arithmetic, with the reasoning left to the agent.

## Changes

[Changelog](https://askmiles.ai/docs/trust/changelog) lists dated changes to the APIs. [Stability](https://askmiles.ai/docs/trust/stability) is the promise about what will not change.