API & MCP
Everything a person can do on Slow Web Resource Budget, a program or AI agent can do with the same inputs and get the identical result.
HTTP API
POST https://signalhouseresourcebudget.usefulweb.app/api/v1/calculate– run Slow Web Resource BudgetGET https://signalhouseresourcebudget.usefulweb.app/api/v1/tool– inputs, output schema, examples- OpenAPI 3.1: /openapi.json · /openapi.yaml
- Errors:
application/problem+json;422includes per-fielderrors.
Slow Web Resource Budget
Compare a resource list or HAR in sequential and shared-link modes with explicit throughput assumptions, cache effects and a baseline waterfall.
| Field | Type | Default | Description |
|---|---|---|---|
bandwidth | number | 5 | Bandwidth (Mbit/s) |
rtt | number | 100 | Round-trip latency (ms) |
loss | number | 0 | Packet loss (%) |
mode | select (sequential, shared) | "sequential" | Transfer model |
connections | number | 6 | Concurrent resources in shared-link mode |
resources | table | [{"name":"index.html","host":"example.test","bytes":25000,"cached":false},{"name | Resources |
Example request
Try an example
curl -X POST https://signalhouseresourcebudget.usefulweb.app/api/v1/calculate -H 'content-type: application/json' -d '{}'
Every result contains
inputs (normalised, defaults applied), summary, result (validated against the published schema), units, assumptions, sources, warnings, computedAt and links.
MCP (Model Context Protocol)
- Streamable HTTP endpoint:
https://signalhouseresourcebudget.usefulweb.app/mcp– protocol revisions 2026-07-28 (stateless) and 2025-11-25 / 2025-06-18 / 2025-03-26 (initialize handshake). - Tools:
signalhouse_resource_budget - Local stdio connector:
node src/mcp-stdio.ts --tool=signalhouse-resource-budget
{
"mcpServers": {
"signalhouse-resource-budget": { "type": "http", "url": "https://signalhouseresourcebudget.usefulweb.app/mcp" }
}
}