Recipe

Read and render the loyalty ladder

Render the loyalty ladder from the public loyalty/tiers endpoint (or the MCP loyalty_tiers tool). It carries tier names, thresholds and benefits only — no customer data — and is cacheable.

2 min read

loyalty/tiersPublic read

CacheableConfig only

No PIIVocabulary

Read the ladder

curl -s https://hub.credicorp.co.uk/public/v1/loyalty/tiers

You get each tier's name, threshold, headline benefit and cooldown — the loyalty endpoint. Agents can read the identical data via loyalty_tiers.

Cache it

The ladder is config vocabulary with no customer data, so it is explicitly safe to cache. Read it periodically rather than hard-coding the tiers, so a config change flows to your UI on the next fetch. Do not attempt to show a specific customer's tier from this endpoint — that is behind authentication in the portal.

Render honestly

Present the thresholds and benefits exactly as published — this is single-sourced so it reconciles with the Credicorp site. If you run a comparison, pair it with the product listing for a complete, accurate picture.

Frequently asked questions

Can I show a customer their own tier?

Not from this public endpoint — it returns only the ladder vocabulary. A customer's own tier lives behind authentication in the borrower portal, not on the public ring.

Is the ladder safe to cache?

Yes. It is config vocabulary with no PII, explicitly cacheable. Refresh periodically so a config change reaches your UI without a redeploy.