In this section: Trust

Trust

Learn how the data a tool returns is maintained, why it matches what Miles' own chat reads, and where API changes are recorded.

What you are building on

Every catalog figure a tool returns, such as a card's fees, earning rates or transfer ratios, comes from a maintained dataset that records every change as a commit. Figures the member supplies, such as balances and their own point values, come from their account. How the data is maintained describes where the dataset lives, when it was last checked, what a change has to pass, and where it can still be wrong. 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 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 with that user's key or grant, through the MCP tools or a Chat API answer.
  • A tool never spends a Miles model call. It returns data and arithmetic for the agent to reason over.

Changes

Changelog lists dated API changes. Stability states what Miles promises to keep stable.