™2 min read
Static: read at build time
Call ListProducts and ProductDetails in your build step and bake the results into the page. Rebuild when you want to refresh.
Dynamic: read behind a cache
For a page that must always be current, read at request time through a short server-side cache so you stay under the rate limit. See caching.
Label quotes as indicative
If you include a GetQuote figure, mark it as an example — see indicative quote.
Choosing build-time or request-time
The right approach depends on how often your comparison must change. A statically built page — reading the products and details during your build step — is the simplest and fastest to serve, and is ideal when a periodic rebuild is acceptable. A dynamic page that reads at request time, behind a short server-side cache, is better when accuracy must be near-instant, for example if you surface indicative quotes that people expect to be current. Either way the data comes from the MCP server, so both stay faithful to the real offering; the only difference is how quickly a change on Credicorp’s side reaches your visitors. Whichever you pick, label any quote as indicative and keep a clear route to a real application.
Frequently asked questions
Static build or live fetch — which is better?
Static build is simplest and fastest; live fetch behind a short cache is best when the page must always be current. Both read from MCP so both stay accurate.
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.