™2 min read
The single source
Credicorp's published figures live in one place, exposed at config/pricing. The marketing estate, the on-page calculators, the quote engine and the MCP tools all read from it. Change the config and every surface updates together — there is no second copy to drift.
What this means for you
Read figures from the API rather than hard-coding them in your integration. Then a Credicorp pricing change flows to you on your next fetch, with zero code change on your side, and your product never shows a number that disagrees with the Credicorp site. Hard-coded figures are the one reliable way to fall out of sync.
Verified end to end
The MCP product descriptions are taken verbatim from the same hub narrative the site uses, and the quote engine behind get_quote is the same one behind the REST quote. So an agent, a widget and the website will all quote the identical figure for the identical input.
Frequently asked questions
Why should I not hard-code Credicorp figures?
Because they come from a single config source that can change. Read config/pricing (or the relevant endpoint) and a pricing change reaches you automatically — hard-coded numbers silently fall out of sync.
Will the MCP quote match the website's quote?
Yes. Both use the same quote engine and the same pricing config, so for the same amount and term they return the same representative figure.
Funding for UK limited companies
Credicorp lends to your company, not to you personally — short-term working capital with no personal guarantee. See what your business could access.