Company
A currency API built by one person, meant to be kept.
Fiat Agent is a currency exchange rate API. It publishes one reference reading of the foreign exchange market — live rates, the full currency catalogue with names, symbols and flags, and every stored historical reading — as JSON over a single REST endpoint, alongside a web rate desk for looking up and converting rates by hand.
Sole creator and operator
Gurutva Murdia
Created and operated solely by Gurutva Murdia. Every part of the service — the data pipeline, the API, the rate desk and the support inbox — is one person's work.
Why it exists
Every product that quotes a price in another currency needs the same three things.
A current rate. The name and symbol of the currency. A way to look back at what the rate was last month. Almost nothing about currency data is complicated — it is just easy to get wrong, and awkward to assemble.
The usual answer is two services stitched together, a plan priced for a bank, or a spreadsheet someone updates by hand. Fiat Agent was built so a developer with an afternoon to spare could get all three from one request, and a business could keep using the same request once that afternoon turned into a product.
What it is
One reading of the market, stored, timestamped, and served from our own store.
Rates are read from a single upstream provider on a fixed cadence and written into Fiat Agent's own store. Every API response and every screen in the rate desk reads that store — never the provider directly — so a call never waits on an upstream request.
Every stored reading quotes the whole catalogue against one base currency. Any other pair is the quotient of those two quotes, so a cross rate is arithmetic you can check rather than a figure you have to trust. Each response states the base, the quotes and the moment the provider published the reading behind them.
Who runs it
One person writes it, runs it and answers the mail.
Fiat Agent is created and operated solely by Gurutva Murdia. The data pipeline, the API, the rate desk, the keys, the payments and the support inbox are all one person's work — there is no team behind the name and no outsourced support desk in front of it.
That has one practical consequence worth stating plainly: when you write to support, you are writing to the person who built the thing you are asking about. It also means the product moves only as fast as one person can make it move, which is why the surface is deliberately small.
What it is being built toward
To be the currency data source you never have to replace.
Most currency APIs are pleasant to start with and expensive to stay with: trial allowances quietly expire, pricing jumps when a project succeeds, and a schema changes at the worst moment. The ambition here is narrower and harder — to be the dependable option, at a price that survives a project becoming a business.
Concretely, that means: balances that do not expire, one response shape that is not renamed inside a version, limits that are published rather than discovered, and a reading timestamp on every answer so anyone can tell how current a figure is.
Principles
The rules the service is held to.
- One upstream provider and one stored reading — no blending, no second opinion hidden inside a number.
- Timestamps on everything, so every figure can be traced to the moment it was published.
- Keys stored only as one-way digests. A copy of the database cannot be used to call the API.
- No expiring credits and no automatic renewals. A top-up adds to a balance and stays there.
- Published limits, stated in the open rather than enforced quietly.
- Reference data, not advice: rates are indicative figures for quoting and display.
Start with one call.
The open endpoint needs no key and answers with the current reading and the full catalogue. The reference explains every field; pricing explains what a key adds.