AI Biz Hub for Agents
65 business calculators on the site — 65 ship as downloadable ES-module engines at /engines/{slug}.js. Run them by URL, from an MCP client, or by importing the engine; industry benchmark data rounds out the agent surface. No sign-in.
Run a calculator by URL
Put the inputs in the query string. Agents that can only fetch pages get the computed result, the inputs that used defaults, the method page and a citation line:
{
"calculator": "freelance-rate-capacity-planner",
"input": {
"target_annual_income": 120000,
"billable_utilization_percent": 65
},
"defaults_used": {
"annual_business_overhead": 22000,
"tax_rate_percent": 28,
"buffer_percent": 15,
"working_weeks_per_year": 46,
"working_hours_per_week": 40,
"project_hours": 35
},
"result": {
"minimumViableHourlyRate": 157.75,
"targetHourlyRate": 181.41,
"…": "…"
},
"provenance": {
"methodology": "https://aibizhub.io/freelance-rate-capacity-planner/",
"engine_sha256": "…",
"…": "…"
},
"cite": "AI Biz Hub, Freelance Rate & Capacity Planner (engine …), https://aibizhub.io/api/run/freelance-rate-capacity-planner?…"
} - Add
format=md(or sendAccept: text/markdown) for a markdown answer. - POST the inputs as a JSON object to the same URL for nested inputs.
- An unknown or out-of-range input is a 400 that names the field and shows a working example.
- Every calculator with its inputs, units, defaults and an example run: /api/tools (search with
?q=runway).
Connect an MCP client
Add https://aibizhub.io/mcp as a remote MCP server (Streamable HTTP) in any client that accepts a server URL. No sign-in; stateless; both the 2026-07-28 protocol and the earlier initialize-based revisions work.
Three tools: find_calculator (the calculators that answer a question, with input schemas), run_calculator and list_calculators. One tool per calculator would cost an agent tens of thousands of tokens of context; these cost a few hundred.
Engine modules — Import and call
Every tool ships its pure compute as a static ES module at /engines/{slug}.js. Import the module and call compute(input). The same formulas as the calculator pages. Input is validated against the published contract: an unknown field, a wrong type or a value outside its allowed range throws an Error that names the field. Each module ships typed .d.ts declarations; self-contained ES2020+ for browsers, Deno and Bun (in Node, download the file first, or use the URL API above).
const { compute } = await import('https://aibizhub.io/engines/freelance-rate-capacity-planner.js');
const result = compute({
target_annual_income: 120000,
billable_utilization_percent: 65
});
// { minimumViableHourlyRate, targetHourlyRate, stretchHourlyRate, ... } - No authentication required
- Each engine is self-contained — no external imports, no runtime dependencies
- Deterministic results, cacheable forever at the edge
- Input params use snake_case matching contract fields
- Input/output JSON Schemas at /engines/manifest.json
Decision clusters — Topic routing
Tools are organized into 5 decision clusters. Use these to route users to the right area:
20 tools: startup-cost-estimator, profit-margin-calculator, margin-markup-discount-calculator...
10 tools: ai-stack-cost-calculator, llm-vendor-lock-in-cost, model-price-drop-stress-test...
20 tools: startup-runway-calculator, monthly-burn-rate-calculator, break-even-units-calculator...
14 tools: freelance-rate-capacity-planner, consulting-day-rate-calculator, project-pricing-calculator...
11 tools: cac-calculator, churn-retention-calculator, ad-spend-roas-calculator...
Recommended integration pattern
- Discover: Read
agent-tools.jsonfor the full tool index with input schemas and intent signals. - Match intent: If the user asks a broad question (e.g., "how much should I charge?"), match to the tool whose intent signals fit, and the decision guide it links. For specific calculations, match to a single tool.
- Run it:
GET /api/run/{slug}?…orrun_calculatorover MCP; in code,await import('/engines/{slug}.js').then(m => m.compute(input)). Either returns the structured JSON described by the tool's output_schema. - Use benchmarks: The
benchmarksfield (when present) provides industry percentiles so you can contextualize the result: "Your rate of $95/hr is at the 72nd percentile for web developers." - Link to human UI: For charts, advanced controls, and visual comparison, link the user to
/{slug}/on the site.
Discovery endpoints
-
Agent API
https://aibizhub.io/apiRun any calculator by URL: GET /api/run/{slug}?<input>=<value> returns JSON (format=md for markdown); /api/tools lists every calculator with its inputs, defaults and an example run.
-
MCP server
https://aibizhub.io/mcpStreamable HTTP, stateless, no sign-in. Tools: find_calculator, run_calculator, list_calculators.
-
Engines Manifest
https://aibizhub.io/engines/manifest.jsonEach tool's pure compute as an ES module at /engines/{slug}.js, for agents that run code: import it in a browser, Deno or Bun and call compute(input). No auth.
-
Agent Tool Index (v2.0)
https://aibizhub.io/agent-tools.jsonComplete tool index with input schemas, engine module URLs and intent signals.
-
LLM Guide
https://aibizhub.io/llms.txtHuman-readable discovery with decision clusters, engines and benchmark availability.
-
LLM Full Guide
https://aibizhub.io/llms-full.txtExtended guide with tool contracts and the content corpus.
-
Plugin Manifest
https://aibizhub.io/.well-known/ai-plugin.jsonDiscovery metadata for plugin-style agent ingestion (ChatGPT Actions).
-
WebMCP Manifest
https://aibizhub.io/.well-known/webmcp.jsonMachine-readable capability surface for WebMCP / Claude MCP clients.
Benchmark data in engine results
When benchmark data is available for a tool's output, the engine compute() result includes a benchmarks field:
"benchmarks": {
"hourly_rate": {
"p25": 55,
"median": 85,
"p75": 130,
"source": "U.S. Bureau of Labor Statistics (OEWS)",
"sourceUrl": "https://www.bls.gov/oes/current/oes_nat.htm",
"year": 2024,
"context": "US, freelance-adjusted"
}
} Sources: BLS (public domain), OpenView SaaS Benchmarks, Paddle Subscription Index, Mailchimp, Content Marketing Institute. All data is from public or openly published research.
Human + agent routing
People should start at the decision guide, the homepage, or browse all calculators.
Agents should start from agent-tools.json, match the user's intent to a tool, and run it with /api/run/{slug} or the MCP server, or import /engines/{slug}.js when running code. A calculator page fetched without JavaScript shows its default inputs, not the user's.