> For the complete documentation index, see [llms.txt](https://docs.zirodelta.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zirodelta.com/modules/fiat-rails.md). # Fiat rails Fiat rails connect balances to the regular money world: getting money in, and spending it. ## What it is designed to do * **On-ramps:** turn bank or card payments into USDC. * **Card spending:** a card that pays straight from a balance, at the moment of purchase, so the balance can keep working until it is spent. * **Local rails:** in each country, payments in the local currency through licensed local partners. ## How coverage works Fiat rails depend on licensed partners, and each partner covers some countries and not others. Coverage will be published per country when integrations go live. Where no partner covers a country, the rails are not available there. ## Status In development. On-ramp and card integrations are being built and are not live. --- # 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.zirodelta.com/modules/fiat-rails.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.