# Prudential plc > Prudential plc (LSE/HKEX/SGX/NYSE: PRU / 2378) is a life and health insurance and asset management group incorporated in England and Wales, with its principal operating office in Hong Kong and roots in London going back to 1848. Its book is almost entirely Asian and African — life protection, health and medical, savings and retirement, takaful, pensions and Hong Kong Mandatory Provident Funds, plus asset management under the Eastspring brand. It has no public API programme: no developer portal, no API reference, no OpenAPI, Swagger, AsyncAPI, GraphQL SDL or .proto document, no SDK, no sandbox and no public Postman workspace exist on any resolvable Prudential plc hostname. What its operating businesses DO publish is llms.txt — six real, first-party files across Hong Kong, Singapore, Indonesia, Vietnam, the Philippines and Malaysia (takaful). Generated by the API Evangelist enrichment pipeline on 2026-07-25 from https://github.com/api-evangelist/prudential-plc — Prudential plc publishes no llms.txt of its own on the corporate domain (https://www.prudentialplc.com/llms.txt returns HTTP 404). ## Two identity traps an agent must not fall into - **This is NOT Prudential Financial, Inc.** The working developer portal at https://developers.prudential.com/ and the partner-gated API portal at https://developer.apis.prudential.com belong to Prudential Financial, Inc. (NYSE: PRU, Newark, New Jersey) — WHOIS on prudential.com returns "Registrant Organization: The Prudential Insurance Company of America". That is a separate company with no ownership relationship to Prudential plc, catalogued separately as `prudential-financial`. Do not attribute its APIs here. - **The UK "Pru" brands are no longer this company.** Prudential plc demerged its UK and Europe business as M&G plc in October 2019 and its US business as Jackson Financial in September 2021. pru.co.uk, pruadviser.co.uk and Prudential Assurance Company Limited sit with M&G plc. ## What an agent can and cannot do here - There is no API to call. Every conventional developer hostname on the primary domain fails DNS resolution (developer, developers, docs, api, apis, partners, partner, portal, sandbox .prudentialplc.com — all HTTP 000) and every conventional developer path returns HTTP 404 (/developers, /api, /developer, /partners, /integrations, /en/api, /en/developers, /en/partners, /en/integrations, /graphql). - No specification of any kind is retrievable: /openapi.json, /openapi.yaml, /swagger.json, /api-docs, /spec and /redoc all return 404 on the corporate host, and /openapi.json, /swagger.json, /api-docs and /graphql all return 404 on every market consumer host probed (HK, SG, MY, ID, VN, PH). - No /.well-known/ discovery document exists anywhere: security.txt, api-catalog, ai-plugin.json, openid-configuration, oauth-authorization-server and oauth-protected-resource all return 404 on prudentialplc.com and on every market host. - There is no first-party SDK on npm, PyPI or any other registry. The `@prudential`, `@pru-rt` and `@prudential-cambodia` npm scopes are forks of community React Native libraries whose backing GitHub organizations do not exist; none is attributable to this company. - The one real first-party GitHub organization, https://github.com/PrudentialCorporationAsia, holds a single public repository — a Gradle plugin for signing files with Symantec Secure App Service. No API definitions, SDKs or client libraries. - No ACORD, AL3, ACORD XML or NGDS reference exists anywhere in the group's public estate. ## The group's own llms.txt files (harvested verbatim) - [Prudential Hong Kong](https://www.prudential.com.hk/llms.txt) — 46,557 bytes, bilingual EN/TC, ~450 titled links. Saved as `llms/prudential-plc-hk-llms.txt`. - [Prudential Singapore](https://www.prudential.com.sg/llms.txt) — 41,976 bytes, canonical H1 + blockquote + sectioned link lists. Saved as `llms/prudential-plc-sg-llms.txt`. - [Prudential Vietnam](https://www.prudential.com.vn/llms.txt) — 19,914 bytes, includes a per-user-agent Bot Access Policy. Saved as `llms/prudential-plc-vn-llms.txt`. - [Prudential BSN Takaful, Malaysia](https://www.prubsn.com.my/llms.txt) — 10,585 bytes, declares the Adobe Experience Manager platform. Saved as `llms/prudential-plc-my-prubsn-llms.txt`. - [Prudential Indonesia](https://www.prudential.co.id/llms.txt) — 7,113 bytes. Saved as `llms/prudential-plc-id-llms.txt`. - [Pru Life UK, Philippines](https://www.prulifeuk.com.ph/llms.txt) — 2,655 bytes. Saved as `llms/prudential-plc-ph-llms.txt`. Five further market hosts (prudential.com.my, prudential.co.th, pcalife.com.tw, prudential.com.mm, prudentialsyariah.co.id) answer /llms.txt with HTTP 200 but return only the 8-byte literal string `llms.txt` — an Adobe Experience Manager path echo, not a document. See `llms/_index.yml` for the full probe matrix. ## AI and agent posture - [Responsible AI at Prudential](https://www.prudentialplc.com/en/site-services/responsible-ai-at-prudential/) — the group's published AI ethics position: an AI Governance Working Group of senior leaders across customer, operations, data science and risk, applying five AI Ethics Principles (Value, Transparency and explainability, Fairness, Accountability and responsibility, Compliance) to both first-party and third-party AI systems. - [Technology and operations strategy](https://www.prudentialplc.com/en/about-us/our-strategy/technology/) — entirely inward-facing: embedding AI and data into every layer, 100+ AI use cases, a global AI Lab, a Responsible AI Framework, and investment in automation, data and cloud. It contains no mention of APIs, open APIs, developer portals, ecosystem integration or data standards. - Prudential Vietnam's llms.txt declares Allow-Training: yes and Allow-Retrieval: yes for gptbot, claudebot, google-extended, perplexitybot, neevabot, youbot, ccbot, duckduckbot, yandexbot and archive.org_bot. That is an ad-hoc vocabulary inside llms.txt, not IETF AIPREF, and it is the only per-agent consent declaration in the estate. ## Corporate surface - [Group website](https://www.prudentialplc.com/en/) - [About us — purpose and mission](https://www.prudentialplc.com/en/about-us/our-purpose-and-mission/) - [Distribution strategy](https://www.prudentialplc.com/en/about-us/our-strategy/distribution/) - [Newsroom](https://www.prudentialplc.com/en/newsroom/) - [Investors](https://www.prudentialplc.com/en/investors/overview/) - [Corporate governance policies and statements](https://www.prudentialplc.com/en/about-us/corporate-governance-and-corporate-actions/policies-and-statements/) - [Contact us](https://www.prudentialplc.com/en/contact-us/) - [Terms of use](https://www.prudentialplc.com/en/site-services/terms-of-use/) · [Privacy notice](https://www.prudentialplc.com/en/site-services/privacy-notice/) ## The real integration channel is distribution, not developers Prudential plc integrates through tied agency forces and exclusive bancassurance partnerships — Standard Chartered (25 years), CIMB Thai, MSB and SeABank in Vietnam, Yoma Bank in Myanmar, Bank Syariah Indonesia, UOB — and through commercial health and wealth partnerships onto the Pulse by Prudential app (Babylon, Tictrac, Halodoc, PAI Health, Huami, Nervotec, Smarter Health, Prive Technologies, OVO, HReasily, Google Cloud). Every one of those announcements is written in commercial terms. None describes an API, an SDK or a developer programme. Quote, bind, issue and FNOL all happen through agents, the myPrudential policyholder portals and bancassurance branch systems; none is documented as a programmable interface.