Credits / usage pricing
The route loop is free. Paid infrastructure costs credits.
Capture a route, find it again, and replay it locally without consuming credits. A balance moves only when Unbrowse invokes an explicitly metered server service or acquires a route whose owner has enabled compensation.
Public cost ledger
What each action costs
Every metered response uses amount_credits. No client-side conversion is required.
Capture, index, publish
0 credits
Learn and share a route.
Internal-route search and resolve
0 credits
Search the shared route graph.
Local cached-route execution
0 credits
Replay an installed route locally.
Unmonetized shared skill
0 credits
Most shared skills are free.
Owner-monetized skill acquisition
0.01–10 credits
Dynamic; shown before the balance gate.
External web search
1 credit
Per request.
Grounded skill chat
0.5 credits
Per request.
General LLM proxy
Variable
Live model cost with a 1.5× service multiplier, returned in credits.
One example run
The receipt reads like the route.
An agent can resolve and replay known internal routes without spending credits. In this example, only the deliberate external search crosses a metered boundary.
- resolve internal route
- 0
- acquire unmonetized skill
- 0
- local replay
- 0
- external web search
- 1
- total
- 1 credit
One account balance
Added, promotional, and settled earned credits share the same account ledger across API keys.
Clear insufficient-balance response
A metered request with too few credits returns HTTP 402, its exact credit price, the current balance, and a billing URL.
Contributor accounting is still settling
Attribution is tracked today. Automatic conversion of every marketplace attribution into spendable account credits is not fully connected yet.