Agent Billing Primitives (Dirtsmith) MCP Server

by throttler300 Your server? Claim it

answering

Agent Billing Primitives (Dirtsmith) is answering right now. Last checked 12 min ago. It exposes 5 tools. Last commit 4 Nov 2026.

Usage metering, spend cap (reserve before pay), lease lock, semaphore, heartbeat for agents. Free tr

Uptime history 5 days of history

5 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

117 ms

Response time

average over 24h

Stars

last commit 4 Nov 2026

What changed 8

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 4 November 2026. No other catalogue keeps this.

4 Nov 5 tool descriptions were rewritten6 times that day agent_heartbeat_registry, agent_lease_lock, agent_semaphore and 2 more

4 Nov 2 tools appeared agent_heartbeat_registry, agent_semaphore

and 1 more, back to 4 November 2026

Nothing serious here today

Today is the operative word: we check Agent Billing Primitives (Dirtsmith) every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp-usage-metering --transport http https://gap-functions.bfurrow26.workers.dev/mcp

Settings → Connectors → Add custom connector, then paste this address

https://gap-functions.bfurrow26.workers.dev/mcp

~/.codex/config.toml

[mcp_servers.mcp-usage-metering]
url = "https://gap-functions.bfurrow26.workers.dev/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp-usage-metering": {
      "url": "https://gap-functions.bfurrow26.workers.dev/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "mcp-usage-metering": {
      "type": "http",
      "url": "https://gap-functions.bfurrow26.workers.dev/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

agent

agent_heartbeat_registry

Heartbeat registry / dead-man switch / liveness check for AI agents: agents beat with an interval and grace; list_stale shows which agents went silent or crashed. Idempotent, shared by namespace. Every call requires a tiny solved packet (returned in the reply, 2 s, one try); free first call, no API key (GET /try?tool=agent_heartbeat_registry).

agent_lease_lock

Distributed lock / lease lock (mutex) for AI agents: acquire, renew, release a named lock with TTL and a monotonic fencing token so only one agent runs a job at a time. Idempotent, shared by namespace, no Redis needed. Every call requires a tiny solved packet (returned in the reply, 2 s, one try); free first call, no API key (GET /try?tool=agent_lease_lock).

agent_semaphore

Counting semaphore / concurrency limit for AI agents: at most N agents hold a slot at once (rate limit parallel workers), TTL permits with fencing tokens, auto-expire on crash. Idempotent, shared by namespace. Every call requires a tiny solved packet (returned in the reply, 2 s, one try); free first call, no API key (GET /try?tool=agent_semaphore).

agent_spend_ledger

Agent spend cap / budget ledger: set a budget, reserve before pay (atomic, never overspends even with many agents in parallel), then settle or release. Idempotent, shared by namespace. Spending limit, budget guard, cost control for AI agents. Every call requires a tiny solved packet (returned in the reply, 2 s, one try); free first call, no API key (GET /try?tool=agent_spend_ledger).

mcp

mcp_usage_metering

Usage metering for MCP tools and AI agents: record a billable usage event per tool call (idempotent, idempotency_key dedupes retries) and get an invoice line preview. Per-call billing, usage-based pricing, metered billing for MCP servers. Every call requires one solved task: a tiny data packet, OR (this tool only) a public item: one line of public-domain text plus a deterministic format conversion (snake_case, word count, uppercase) with a known answer, returned as item_alternative; answer it within 2 s via item:{item_id, answer}. Verified answers are stored and readable at GET /items. Free first call, no API key (GET /try). Pay-ahead: every response carries next_work_packet; pass work_answer {work_packet_id, labels} on your next call (under 2 s) instead of solving a fresh packet. That work is our own internal classification (Buyer Zero), not customer data.

Endpoints

URL	Transport	State	Latency	Checked
https://gap-functions.bfurrow26.workers.dev/mcp	streamable-http	answering	108 ms	12 min ago

Alternatives to Agent Billing Primitives (Dirtsmith)

same job, measured the same way

Arrakis

by goodailabs

Rent GPUs at live prices and serve any Hugging Face model, with spend caps for AI agents.

16 tools answering

Rein

by bugiiiii11

Spend limits for AI agents that pay with x402: every paywall is policy-checked before a cent moves.

88 installs/wk local only

Locus

by paywithlocus

Pay-per-use APIs for agents: web research, data lookups, and metered endpoints billed to credits.

answering

Agentguard47

by bmdhodl

Read-only MCP server for coding-agent traces, alerts, costs, usage, and budget health.

51 installs/wk local only

Payment Guard MCP

by mlawsonking

Pre-send risk check for AI agents that move money — screen an address or payment URL before sending.

74 installs/wk local only

Agent Metering

by jdhart81

Usage metering + SLA accounting for agent services (the meter behind x402 micropayments).

11 tools answering

TWZRD Agent Intelligence

by twzrd-intel

Pre-spend trust for AI agents that buy: check x402 services and product listings before paying.

161 installs/wk 28 tools answering

TWZRD Agent Intelligence

by twzrd-sol

Pre-spend trust for AI agents that buy: check x402 services and product listings before paying.

local only

Agent Billing Primitives (Dirtsmith) — questions

Answers built from our own checks of this server.

What can Agent Billing Primitives (Dirtsmith) do?

It exposes 5 tools, read directly from the server on our last check. Among them: agent_heartbeat_registry, agent_lease_lock, agent_semaphore, agent_spend_ledger, mcp_usage_metering. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Agent Billing Primitives (Dirtsmith) working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 117 ms. The bar chart above shows every period we have measured.

How do I connect Agent Billing Primitives (Dirtsmith)?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Agent Billing Primitives (Dirtsmith) need an API key?

No. Agent Billing Primitives (Dirtsmith) completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Agent Billing Primitives (Dirtsmith)?

It answers our handshake in 117 ms on average, which is faster than 90% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Agent Billing Primitives (Dirtsmith) open source?

The code is open source: it is published under the MIT licence and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at gap-functions.bfurrow26.workers.dev, which runs on its operator's own terms.