One API, many models
Customers point the OpenAI or Anthropic SDK they already use at our base URL and keep their code. The gateway speaks both wire formats, streaming included, over a canonical request it maps to whichever upstream serves the model.
CareersBuild the billing layer
Build the billing layer
for AI in India.
Top Billing is an AI API gateway billed from prepaid rupee credits. It is early and it is small, and the two engineers we are looking for will shape most of what it becomes.
At a glance
- Open roles
- 2, both engineering
- Where
- Remote, anywhere in India
- Team
- A handful of people
- Operated by
- VD Enterprises, a sole proprietorship in Tiruvarur, Tamil Nadu
- Applications
- careers@topbilling.in
No recruiters, no take-home assignment farm, no funding announcement to put here.
What we are buildingAn AI API
An AI API
that bills in rupees.
Using a frontier model from India usually means a foreign card, a dollar invoice and a subscription you cannot meter. We sell the same models on prepaid INR credits, through the SDKs teams already have in their code. The documentation and the prices are public; read them before you apply.
Prepaid credits, in rupees
No subscription and no card on file. You top up in INR, each request reserves an estimate and settles on the tokens the model reports. Every rupee moves inside SQL functions with row locks and idempotency keys, never in application code.
Built for Indian teams
Payment by UPI, a GST invoice after every top-up, prices quoted in rupees rather than converted at checkout. The things a developer in India has to work around everywhere else.
Remote, small,
written down.
- 01
Remote, across India
There is no office to come to. Work from wherever you are in India, with a few hours of overlap with IST so questions do not wait a day.
- 02
Very small, and honest about it
This is an early company, not a startup with a floor of engineers. You will be one of a handful of people, and the thing you ship is the thing customers get.
- 03
Written down, not meetings
Decisions live in specs and commit messages. The money rules, the protocol spec and the build plan are all written before the code and updated with it.
- 04
You own what you ship
The same person designs a change, writes its tests, migrates the database and watches it in production. Nothing is thrown over a wall.
What this is not: there is no HR department, no published salary band, no equity programme and no investors to name. Compensation is agreed directly with the proprietor, in writing, before you start.
Open rolesTwo roles,
Two roles,
both hands-on.
Both are remote within India and both are engineering. If neither is quite you but the work is, write anyway — the list below is what we know we need today, not the limit of it.
Backend / platform engineer
Engineering · Remote (India)The gateway and the ledger: the request path that reserves credit, calls an upstream provider, streams the answer back and settles the charge on real usage.
What you would work on
- Provider adapters — the one place an upstream SDK or URL is allowed to appear.
- The reserve / finalize / release path, and the reconciliation that follows when usage is unknown.
- Protocol work against the official OpenAI and Anthropic SDKs, including streaming and tool calls.
- Load and failure behaviour: what happens when a provider is slow, wrong, or down.
What we are looking for
- TypeScript and Postgres in production, and comfort reading and writing real SQL.
- Care about concurrency and money: you have debugged something that double-charged, or taken pains so it could not.
- You write tests for the thing you are afraid of before you write the thing.
Full-stack / frontend engineer
Engineering · Remote (India)The surfaces people actually touch: the customer console, the admin console behind it, and this public site and its documentation.
What you would work on
- Billing, usage and key-management screens in the customer console.
- The admin console: providers, models, pricing versions, refunds and audit trails.
- This public site and the docs — Next.js App Router, plain CSS, no component framework.
- Making numbers legible: a usage chart or an invoice is a financial document, not decoration.
What we are looking for
- Next.js and TypeScript, and CSS you write yourself rather than configure.
- You notice when an interface feels wrong, and you can say why and fix it.
- Accessible by default: keyboard paths, focus states, both colour themes.
- Happy to write the server half of your own feature.
One email.
Read by a person.
Send it to careers@topbilling.in. It goes to the proprietor directly; there is nobody else for it to go to.
What to send
A short note saying which role and why, and the two or three things you have built that you would want us to look at — a repository, a shipped product, a write-up of something you debugged. A CV is welcome but it is not what we read first.
What happens next
A reply from the proprietor, then a conversation about the work itself: the code you sent, the problems above, how you would approach one of them. No panel rounds, no unpaid project, no puzzles unrelated to the job. We will not promise a turnaround we cannot keep, but you will hear back.
If nothing fits
Write anyway and say what you do. We keep a short list and come back to it before we post anything new. Contract and part-time arrangements are possible for the right person.
Read the docs first.
Then write to us.
The best applications we get have already used the product. Create an account, send a request through the SDK you know, and tell us what you would change.