Request and response
Every conversation with an API has two parts: what you ask for and what you get back.
Explained simply
An API is a “door” through which one program asks another program for something and gets an answer, without knowing how the other one works inside. Below it is explained step by step, without technical terms.
An analogy
You sit at a table and choose from the menu. You do not walk into the kitchen: you tell the waiter what you want, and the waiter brings the food. The waiter is the API.
The menu is the list of what you can ask for. At Lumos API the menu has operations such as “calculate a sole proprietor’s taxes” or “check whether a message is a scam”.
Step by step
For example: “how much does a sole proprietor (PFA) keep from an income of 120,000 lei and expenses of 30,000 lei?”
The request carries a key, like an access card. Without a key, or without credits, the request does not go through.
The calculation is done on our side, with up-to-date tax rules. Your app does not need to know them.
The app receives the result (28,035 lei in taxes, 61,965 lei left) and shows it to the user.
The request and the response, in brief
→ POST /v1/taxaro/calculations
{ "form": "pfa_real", "annual_income": 120000, "expenses": 30000 }
← { "total_taxes": 28035, "net_take_home": 61965 }The figures are calculated by TaxaRO. The full example is on the home page.
Words
There are only a few. Each has a one-sentence explanation.
Every conversation with an API has two parts: what you ask for and what you get back.
Where you send the request. Each address does one thing, for example “calculate the taxes”.
A long password, yours alone, that shows who is making the request. It is kept secret.
The format the data travels in: plain text, with names and values, that any program understands.
The unit you pay in at Lumos API. Each operation costs a fixed number of credits.
A kind of API made for AI assistants: an assistant, such as Claude, can ask for what it needs by itself.
Why
Rules and data change. With an API you redo nothing: the answer comes with today’s rules.
The heavy calculations and checks are already done and tested. You ask for them instead of writing them again.
Your program asks for the answer when it needs it, without anyone opening a website and copying figures.
Examples
FAQ
Usually a developer connects the API to your app. If you only need the results, you find them free on the Lumos websites, for example on TaxaRO. Later you will also be able to use the services from an AI assistant, without writing code.
You pay in credits that you buy in advance, and you get a few free ones every month. The price of a credit has not been set yet.
We do not save the content of your requests. We keep only who made the call, which operation it was, what it cost and how long it took.
They are indicative: they do not replace an accountant, a lawyer or a consultant. Every response shows which rules it used and how recent the data is.
Not yet. Lumos API is in preparation; you can join the waiting list and we will write to you once, when it opens.
Leave us your email address and we will let you know when you can start.