> For the complete documentation index, see [llms.txt](https://docs.nfh.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nfh.global/use-cases/portable-benefits.md). # Portable benefits & fair pricing Insurance, credit, and benefits that follow the worker across platforms — portable, verifiable, fairly priced, on NFH fabric. A delivery rider works across three apps in a year. Each holds a slice of their earnings history, their ratings, and their reliability — and none of it travels. So an insurer in Bogotá can't price a policy for them without treating them as a thin-file stranger, a lender can't extend fair credit, and the worker loses every benefit each time they switch platforms. The data that would establish their trustworthiness exists; it just isn't portable or verifiable. NFH fabric lets a worker **carry a verifiable, portable record of their own activity** across platforms — so insurers and lenders can price risk accurately, and benefits stop resetting at every employer boundary. ## What changes * An underwriter **prices policies accurately for gig workers** using verified, portable history — improving the claims ratio and lowering acquisition cost. * Benefits and reputation **follow the worker across platforms** instead of resetting each time they switch. * A microfinance officer **lends to thin-file customers** against a verifiable transaction history, reducing default risk. * The worker discloses **only what's needed** (e.g. "12 months, 98% on-time") via selective disclosure — not their entire raw record. ## Where to start Issue a portable earnings-and-reliability credential from a sandbox platform to a test worker. Publish one insurance product, have the worker present a selectively-disclosed proof, and run a quote-and-settle loop. Confirm the insurer never receives raw platform data — only the verified claim. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.nfh.global/use-cases/portable-benefits.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.