Workflow · saas · workflow
Pricing the Unknown: Ref builds credit-based pricing for the first standalone paid MCP server
Ref faced the novel challenge of pricing a first-of-its-kind standalone paid MCP server in an ecosystem where nearly everything is free, while covering high web-crawling and indexing costs and supporting usage volumes ranging from individual developers making ten searches a day to agents making thousands.
How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · AI agent calls MCP tool
An AI coding agent calls ref_search_documentation or ref_read_url, each billed at 1 credit per call.
Tools used
Turbopufferref_search_documentationref_read_url
Outcome
Three months after launch, Ref has thousands of weekly users and hundreds of subscribers, with the monthly minimum covering fixed indexing costs and additional credit purchases scaling with usage.
Results
Time savedthousands of weekly users
Running since3 months ago
Grounding & classification
Source type: technical build writeup
17 fields verified against source quotes.
knowledge searchragknowledge basebuilder submittedmetric backedproduction runtime claimedtools describedworkflow describedsoftwaretechnical build writeuprag answering