https://agent-ledger-production-0ff8.up.railway.app/mcp/ ↗
Per-agent spend management: x402/MPP/API-key rails, budget caps, anomaly alerts, audit trails.
AgentLedger is a remote MCP server published at agent-ledger-production-0ff8.up.railway.app. It has been probed 6 times since 9/12/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 346 ms, placing it among the faster endpoints. It offers a narrow, focused set of 7 tools. On the protocol side it speaks the 2026-07-28 stateless spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
ledger_track — Ambiguous 'agent_secret' vs 'workspace_key' requirements for initial agent setup.ledger_set_budget — Unclear distinction between 'daily_cents' and 'monthly_cents' usage in budget enforcement.ledger_report — Redundant credential rules description duplicates GET /v1/report documentation.tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Tools the server advertised in the latest measurement — measured, not catalog-claimed.
ledger_trackRecord a spend entry for an AI agent on any payment rail, with optional token counts. Claiming a brand-new agent_id requires your workspace_key (get one via x402 at POST /v1/billing/x402 — no human, no login — or at /start). That first call mints an agent_secret and returns it in the response — save it, every later call for that same agent_id must pass it back (no workspace_key needed again) or the write is rejected. Amounts are capped at $100,000/entry and must be >= 0. If a budget is set for this agent, an entry that would cross the monthly/daily cap is blocked, not just logged. Include tokens_in/tokens_out + model on every LLM call so token burn shows up in the /v1/tokens report.
agent_idstringrequiredrailstringrequiredamount_centsintegerrequiredservicestringrequiredtokens_inintegertokens_outintegermodelstringagent_secretstringworkspace_keystringledger_set_budgetSet spending caps for an agent. Warns at 80%, blocks spend when exceeded — enforced: a ledger_track call that would cross the cap is rejected. Dollar caps (monthly_cents/daily_cents) and token caps (monthly_tokens/ daily_tokens) are independent dimensions: dollar caps only cover non-"tokens" rails, token caps only cover rail="tokens" bookkeeping rows (tokens_in/tokens_out). Set both if the agent uses both. Monthly cap is required; the rest are optional (0 = no limit). Overwrites any existing budget for the agent. Claiming a brand-new agent_id requires your workspace_key; that first call mints an agent_secret (returned once — save it); later calls for that agent_id must pass the agent_secret back (no workspace_key needed again).
agent_idstringrequiredmonthly_centsintegerrequireddaily_centsintegermonthly_tokensintegerdaily_tokensintegeragent_secretstringworkspace_keystringledger_reportSpend report for an agent over a rolling window. Returns total spend, breakdown by rail and by service, budget status (ok/warning/exceeded), detected anomalies, and entry count. Requires a credential: either the agent's own agent_secret or its workspace's workspace_key (same rule as GET /v1/report).
agent_idstringrequireddaysintegeragent_secretstringworkspace_keystringledger_alertsAlert history for an agent: budget warnings (80% threshold) and spending spikes. Requires a credential: either the agent's own agent_secret or its workspace's workspace_key (same rule as GET /v1/alerts).
agent_idstringrequiredagent_secretstringworkspace_keystringledger_list_agentsOwner-only: full cross-tenant listing of every agent ever claimed on this instance, with totals. Requires the operator's admin_secret — this is a portfolio-wide view, not a per-agent report (use ledger_report for that — it requires that agent's agent_secret or its workspace_key).
admin_secretstringledger_api_docsSelf-serve documentation for AgentLedger — quickstart, MCP tools, REST endpoints, budget caps, error codes, and idempotency usage, as markdown.
topicstringledger_examplesComplete, runnable Python recipe for a common AgentLedger integration pattern.
patternstringrequiredDerived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/io-github-entradox-agent-ledger)<a href="https://mcpmetrics.io/servers/io-github-entradox-agent-ledger"><img src="https://mcpmetrics.io/badge/io.github.entradox/agent-ledger/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to seeThe catalog entries whose name and description are closest to this one, found with the same index the search box uses.
WordPress MCP server: publish posts, AI images, SEO and full site management, self-hosted
1005 pay-per-result MCP/x402 APIs for web, data, Base, reliability and agent delivery.
Live USGS earthquake alerts: M2.5+ 24h, mag, depth. Register in-session — free testnet funds.
Cybersecurity news & breach alerts: hacks, patches. Register in-session — free testnet funds.
US weather alerts (NWS): warnings, watches. $0.01/query. Register in-session — free testnet funds.
Dead-man switch for AI agents & cron jobs: heartbeat with state capsule, alerts + resume links
| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-13 01:33:33 | Dual-era | 200 | 403 | 200 | 391 | 2026-07-28 |
| 2026-09-12 23:31:36 | Dual-era | 200 | 345 | 200 | 337 | 2026-07-28 |
| 2026-09-12 21:29:15 | Dual-era | 200 | 346 | 200 | 334 | 2026-07-28 |
| 2026-09-12 19:27:29 | Dual-era | 200 | 338 | 200 | 365 | 2026-07-28 |
| 2026-09-12 17:24:09 | Dual-era | 200 | 332 | 200 | 338 | 2026-07-28 |
| 2026-09-12 15:21:42 | Dual-era | 200 | 392 | 200 | 380 | 2026-07-28 |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.
Comments
Sign in to write a comment
No comments yet. Be the first.