Replit Agent has no fixed price: Replit bills each request by effort, and the Core plan costs $20 a month ($18 a month billed yearly) with $20 of monthly credit. A simple business tool, such as a stock checker that reads a sheet, usually fits inside that credit if you keep requests small. Set a spend limit before you start.
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowThat last point is the real answer to "how much does it cost". Nobody can tell you the dollar figure for your tool before you build it, because it depends on how many requests you make and how complex each is. What you can do is set a ceiling, measure the first few requests and extrapolate. The method, with a stock-checker as the example, follows.
What does the Replit Core plan cost and include?
Replit Core costs $20 a month, or $18 a month billed annually, and includes $20 of monthly credit that pays for Agent and other cloud services.
Replit's pricing page, read in November 2026, lists three paid-looking tiers. Core is $20 a month, or $18 a month billed annually, aimed at "personal projects and simple apps", with monthly credits of $20 towards its models. Pro is $100 a month, or $90 billed annually, for "commercial and professional builds", with $100 of credits, up to 15 collaborators and database rollback up to 28 days. Enterprise is custom. A free Starter plan exists with a daily cap on Agent use.
The credit is not only for Agent. Replit's documentation says credits cover Agent and other cloud services, including published apps, storage and databases, and that third-party AI services such as Claude, ChatGPT or Gemini models are billed at the provider's public API rate and deducted from the same credits. Production databases are billed on compute time and storage. Development databases are free. Core users get a 100 GiB outbound data allowance for published apps.
So one pot of $20 pays for three different things: building (Agent requests), running (publishing and databases) and any AI features the tool itself calls. A stock checker that uses no AI and no database spends almost nothing on the second and third, which is why it is a good first project.
How does Replit Agent's effort-based pricing work?
Replit Agent bills each completed request by the effort it took, and each request ends in a checkpoint, so there is no fixed price per request; simple fixes typically cost less than complex builds.
Under Replit's current model, Agent bills per completed request in Build Mode. Each request ends in a checkpoint, and Replit bundles complex work into one checkpoint rather than splitting it. The documentation says simple requests, like bug fixes or small changes, typically cost less than complex builds. Three further rules matter to a budget:
- Confirmation first. Replit asks you to confirm before a paid action starts, which gives you a chance to refuse.
- Plan Mode is not free by default. The documentation says Plan Mode can incur charges on the paid path even when it changes no code.
- Free Mode exists. On Core and Pro, everyday Agent work in Free Mode does not use credits within an allowance: Replit's pricing page lists up to 30 hours of chat and up to 60 projects on Free Mode for Core, and more Free Mode usage on Pro (checked 20 November 2026). Starter has a daily cap.
The documentation also points to an interactive pricing demo rather than listing per-request prices. That is why this tutorial gives you a way to measure rather than a number to copy. Be wary of third-party pages quoting precise per-checkpoint figures: pricing has changed more than once, and the dates people give for the changes do not agree.
A bookshop stock-checker: the main worked example
Say an independent bookshop keeps stock in a sheet with columns for title, author, ISBN, shelf location and quantity. The owner wants a page that staff open on a phone, type a title or author into, and see whether it is in stock and where. Nothing else: no logins beyond a shared link, no payments, no AI inside the tool.
Break the build into requests of roughly increasing size. These are illustrative requests; the cost of each is something you measure.
- Request 1, the skeleton: a single page with a search box and a results list, reading from a pasted sample of ten rows.
- Request 2, real data: load the full stock list from an uploaded file, and show title, shelf and quantity.
- Request 3, search that forgives: match part of a title, ignore capital letters, and find by author or ISBN.
- Request 4, phone layout: large tap targets and a layout that works on a narrow screen.
- Request 5, out-of-stock wording: show "Out of stock, last sold [date]" rather than a blank.
- Requests 6 to 8, repairs: fix the two or three things you only see when staff use it.
Eight requests is a reasonable allowance for a tool this small. The budget question becomes: what does an average request cost? There are two ways to find out, covered next. The step-by-step build itself is in How to use Replit Agent: build a simple stock checker from a sheet.
How do you measure Replit Agent cost before committing?
Measure Replit Agent cost in three steps: set a usage alert and a budget limit, run the first two requests and read the usage page, then estimate the rest from the larger cost with a margin for repairs.
- Set a budget limit before the first request. In Settings, open Billing, set a usage alert at a figure that would make you pause (say $5) and a budget limit as a hard cap (say $15 for the month). Replit describes alerts as notifications at spending thresholds and budgets as hard caps.
- Run requests 1 and 2 and read the usage page. Replit says usage data can take up to 30 minutes to appear, so wait before reading it. Note what each cost.
- Extrapolate with a margin. Take the larger of the two costs, multiply by the number of requests you expect, then add half again for repairs.
The sums below use assumed average costs. They are not Replit's figures; replace them with your own after step 2.
| Assumed average cost per request | Requests the $20 credit covers | Eight requests cost | Credit left for hosting and repairs |
|---|---|---|---|
| $0.25 | 80 | $2.00 | $18.00 |
| $0.50 | 40 | $4.00 | $16.00 |
| $1.00 | 20 | $8.00 | $12.00 |
| $2.50 | 8 | $20.00 | $0 |
Read the table as a map of risk. If your measured average is $1 or less, a first tool is well within the credit. If it is nearer $2.50, the whole credit goes on eight requests and nothing remains for repairs or running the published tool. Then you tighten your requests, or accept a top-up, or move the job to a spreadsheet.
How do you keep Replit Agent requests small to spend less?
Keep Replit Agent requests small by asking for one page or one change at a time and saying what not to add, because smaller requests tend to cost less.
Replit's billing documentation says paid Agent work is billed by effort, with charges generally arising at checkpoints, so smaller requests tend to cost less. Vague, sprawling prompts invite large, expensive builds that you then have to repair. Compare these two requests for the same page.
Too big:
Build me a stock management system for my shop with search, low-stock
alerts, supplier orders, reports and a login for staff.
Right-sized:
Create one page with a search box. Below it, show matching rows from the
uploaded file stock.csv with columns Title, Author, Shelf, Quantity.
Match part of a title, ignoring capitals. Do not add logins, alerts
or any other pages.
The second prompt names the file, the columns, the matching rule and, importantly, what not to build. Agents tend to add features nobody asked for, and each addition costs credit and creates something to check. A sentence beginning "Do not" is the cheapest line in the prompt.
A realistic first result is a working page that shows the right rows but misses ISBNs and treats "tolkien" and "Tolkien" differently until request 3. That is normal and cheap to fix in one more small request. Test with five real titles, including one that is out of stock and one you misspell.
Where does Replit credit disappear without anyone noticing?
Replit credit usually disappears unnoticed through repeated small cosmetic requests, production databases nobody reads and published tools nobody uses.
An illustrative removals firm builds a job-lookup page with Agent. The first four requests are cheap. Then the office manager, trying to get a layout right, sends eleven "make the buttons bigger, no, smaller" requests, each one a fresh checkpoint. She also leaves the app published with a production database that nobody reads. Three weeks later the credit is gone and the usage page shows most of it spent on small tweaks and background running, not the main build.
Three habits prevent it:
- Batch cosmetic changes. Write down five layout fixes and send them as one request.
- Use development databases while building. Replit says development databases are free; production databases bill on compute time and storage.
- Check usage weekly. Open the usage page every Friday for the first month, and delete or unpublish tools nobody uses.
Should a business tool use Replit Core or Pro?
Stay on Replit Core at $20 a month for a first tool built by one person, and move to Pro at $100 only when two months in a row end with the credit gone before the work is done, or when several people build together.
Core's $20 suits one builder making simple tools. Pro's $100 includes $100 of credit, up to 15 collaborators and database rollback up to 28 days, and Replit's billing documentation says Pro credits roll over for two months. If you will have two or three people building together, or you run several tools in production, Pro can make sense. For a first tool built by one owner, it is premature.
A practical rule: stay on Core until two consecutive months end with the credit gone before you finish the work. The $80 difference only pays off at that point. Until then, a top-up costs less than a plan jump you might not use.
Three other small tools, budgeted the same way
A florist's delivery-day list. A page that reads the day's orders from a sheet and groups them by delivery area. Four or five requests; no database; very likely inside the credit. The risk is wanting a map, which adds a third-party service and extra requests.
A photography studio's enquiry tracker. A form that writes enquiries to a database and shows a status column. This needs a database, so decide between a development database while testing and a production one when staff use it daily, and check the monthly compute and storage lines on the usage page.
A bookshop's gift-voucher balance checker. Anything touching money or customer details raises the stakes. Do not publish it before reading the vibe-coded app security checklist, and consider whether a ready-made tool is safer than a custom one.
For whether building is wise at all if you do not code, Is Replit worth it for a non-coder building a business tool? covers the judgement, and Bolt.new vs Replit for a business tool compares the credit models of two builders.
A session log you can copy, filled in
Keep a plain table while you build. It takes a minute per request and shows exactly where credit went. This one is illustrative; the costs are placeholders to show the layout, not what Replit charged.
| # | Request (one line) | Result | Cost from usage page | Running total |
|---|---|---|---|---|
| 1 | Search page with ten sample rows | Works, no styling | $[x] | $[x] |
| 2 | Load full stock.csv | Works, slow on first load | $[x] | $[x] |
| 3 | Partial, case-blind title match | Works, ISBN missed | $[x] | $[x] |
| 4 | Add ISBN search | Works | $[x] | $[x] |
| 5 | Phone layout | Buttons too small | $[x] | $[x] |
Filling in the last two columns from the usage page after each pair of requests gives you your own average within an hour. The row for request 5 is the kind that grows: "buttons too small" tempts a second and third layout request. Write the fix as one precise instruction instead, for example "make every tap target at least 48 pixels tall and add 12 pixels of space between rows", and send it once.
If you keep the session log in a spreadsheet, try The Complete Excel Course with AI Integration on Coding Liquids.
How do you word a Replit repair request so it costs less?
A Replit repair request costs less when it names one defect, gives the evidence and sets a boundary, such as changing nothing else on the page.
Repairs are where a small budget leaks, because the temptation is to describe the symptom and let Agent guess. Compare these two ways of reporting the same bug.
Vague:
The search doesn't work properly, please fix it.
Specific:
Searching "tolkien" returns no rows, but "Tolkien" returns 6.
Make title and author matching ignore capital letters.
Change nothing else on the page.
The specific version gives Agent one defect, the evidence and a boundary. A realistic outcome is a one-line change to the matching rule, with a checkpoint that costs little. The vague version risks a rewrite of the search code, which costs more and might break the part that worked. When you are unsure of the cause, ask Agent to explain what it thinks is wrong before it changes anything, then decide whether to pay for the fix. Replit's documentation notes that Plan Mode can incur billable reasoning even when no code changes, so keep explanations short and purposeful and watch the usage page after a chat that changed nothing.
Worst-case budgets for a first month
Work out the most you are prepared to spend before you start, rather than the most you expect. For the stock checker, a sensible stance has three layers:
- Planned spend: the $20 plan price, which you pay whatever happens (or $18 a month if you commit to a year, which is $216 a year).
- Expected extra: nothing, if the tool is built inside the monthly credit.
- Tolerated extra: a top-up up to a figure you choose, say $10. Your budget limit stops spending beyond the planned and tolerated amounts in total.
With those three numbers, the first month can cost at most the plan price plus the tolerated extra, and you will know it before the first request. Write the figure on a sticky note and put it where the person building will see it. Many overspends happen because the person building was never told the limit.
After the build: what keeps costing money
A finished tool still draws on the same credit if you publish it. Replit's documentation lists publishing as billed on outbound data transfer, Autoscale compute units and requests, with Core users getting 100 GiB of outbound data. A page used by three staff in a shop transfers very little, but it does run, so read the usage page after the first full week with the tool live and note the daily cost of simply having it published. Multiply by 30 to see the monthly running cost, then decide whether that is acceptable.
Two decisions come with a live tool. First, who owns it: if the person who built it leaves, someone must be able to log in, read the usage and unpublish it. Second, what data it holds: a stock list is harmless, but a tool holding customer details needs the checks in the security checklist before anyone relies on it.
When a different tool is cheaper than building
For many shops, the cheapest stock checker is a filter view on the shared sheet that staff already use, which costs nothing and needs no tool to maintain. Build with Agent when the sheet has become awkward on a phone, when several staff need a clean interface without seeing the whole sheet, or when you want the learning that comes with building. If the main motive is curiosity, a free Starter plan with its daily cap is the lowest-risk way to try. If the main motive is a result, compare the sheet route, a no-code tool and a developer's quote before spending credit; Vibe coding vs no-code vs a developer sets out how the three trade off.
Deciding whether the tool was worth building
Add up the costs at the end of the month: the plan price, any top-ups, and your own hours at a sensible hourly value. A stock checker that costs $20 plus six hours of the owner's time is not cheap if a sheet filter would do the same. It is a good deal if three staff use it twenty times a day and customers wait less. Write down the question the tool answers and who asks it, and judge it on that.
If you would rather decide what is worth building before spending credit, that is what my AI implementation consultation covers, and you can get in touch to see whether it fits.
What goes in a pre-build checklist for Replit Agent?
A pre-build checklist for Replit Agent states the job, the plan, the spend limit, the data, the planned requests, the review points and a stop rule.
- Job: staff find a book's shelf in under 10 seconds. Done when five test titles work on a phone.
- Plan: Core at $20 a month, $18 if paid yearly.
- Spend limit: alert at $5, budget limit at $15.
- Data: a copy of the stock sheet with no customer information.
- Requests: eight planned, each one sentence, each ending with what not to add.
- Review: usage page after requests 1 and 2, then weekly.
- Stop rule: if the average request costs more than $2, rewrite the prompts smaller before continuing.
Replit Agent cost: questions business owners ask
Is there a fixed price per Replit Agent request?
No. Replit's documentation says Agent uses effort-based pricing, where each completed request produces a checkpoint and simple requests such as bug fixes or small changes typically cost less than complex builds. The page lists no per-request prices, so measure your own first few requests on the usage page instead of relying on figures quoted elsewhere.
What happens when the monthly credit runs out?
Usage beyond the credit is charged on top of your plan, and you can also buy one-time top-ups. Replit's billing documentation says billing occurs monthly or once accumulated costs exceed your monthly credits. Set a budget limit on the Billing page in Settings, which Replit describes as a hard cap, so a long session cannot run past what you chose.
Does hosting come out of the same credit?
Yes. Replit's documentation says credits cover Agent and other cloud services, including published apps, storage and databases. A tool you leave running every day therefore uses credit even when you are not building. Core also includes an outbound data allowance for published apps, which a small internal tool is unlikely to approach.
Is Core enough for a business, or do I need Pro?
For one person building a small tool, Core is usually the place to start. Pro costs $100 a month with $100 of credit and up to 15 collaborators, so it suits a team or heavier building. Move up only when you hit the credit limit repeatedly or need several people working in the same project.
Further reads
- Automating a Broken Process: Why It Backfires and What to Fix — Why fixing the process first saves building twice.
- What Should a Small Business Automate First With AI? — Pick a first job that is worth a small tool.
- How to Tell If a Process Is Ready to Automate With AI — Check the process is stable before you build on it.
- How to Evaluate an AI Implementation Proposal or Quote — Weigh a developer's quote against building it yourself.
Browse all AI-for-business tutorials
Sources: Replit pricing page and Replit documentation on billing, AI billing and usage, fetched November 2026.
