agent-metering
Server Details
Usage metering + SLA accounting for agent services (the meter behind x402 micropayments).
- Status
- Healthy
- Uptime
- 95.2% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- jdhart81/viridis-agent-fleet
- GitHub Stars
- 0
- Server Listing
- viridis-agent-fleet
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 11 tools
Each tool has a distinct resource/action: meter creation, event recording/listing, aggregation, SLA reporting, period closing, chain verification, and admin flagging are clearly separated. Reporting tools like usage_summary, usage_timeseries, and sla_report overlap in domain but have clearly differentiated outputs.
All tool names use consistent snake_case and are generally readable. Most follow a verb_noun pattern, though reporting tools such as usage_summary, usage_timeseries, and sla_report use noun phrases instead.
The server exposes 11 tools, which is well within a reasonable range for a metering and billing domain. Each tool appears to earn its place without excessive surface area.
Core lifecycle operations are covered: create/list meters, record/list events, aggregate usage, produce SLA reports, close periods, and verify integrity. Minor gaps exist around meter updates/deactivation and invoice retrieval/listing after close_period.
Available Tools
11 toolsclose_periodClose periodADestructiveInspect
Freeze all open events into an immutable invoice (exactly-once). The invoice amount is what agent-escrow-agent should settle.
Inputs: meter_id (required). Returns: result
create_meterCreate meterBInspect
Create a usage meter between a provider and a consumer agent.
unit: what is being counted (call, token, kwh, ...). Price is in minor
currency units (cents) per unit. Returns the meter_id.Inputs: unit (required), consumer (required), provider (required), price_minor_per_unit (required), +2 more. Returns: result
describe_agentDescribe this serviceARead-onlyIdempotentInspect
Describe this agent: name, version, purpose, every action it supports and the inputs each one takes. Read-only and free; call it first to learn how to use this server.
Inputs: no named parameters. Returns: result
flag_meterFlag meterAInspect
Admin: flag/unflag a meter as test/synthetic so its events are excluded from usage statistics by default. Touches meter metadata only — never events, never the hash chain, never billing accruals. Requires the server's VIRIDIS_ADMIN_TOKEN.
Inputs: is_test (required), meter_id (required), admin_token (required), note. Returns: result
list_eventsList eventsARead-onlyIdempotentInspect
Read usage events (paginated, read-only). Filter by meter, provider, consumer_class (internal|external|unknown), channel, outcome (ok|error), and ISO date range [since, until). Test-flagged events are excluded unless include_test=true. Returns events + next_cursor.
Inputs: limit, since, until, cursor, +6 more. Returns: result
list_metersList metersARead-onlyIdempotentInspect
List all meters with event/invoice counts.
Inputs: no named parameters. Returns: result
record_usageRecord usageCInspect
Record a usage event. Idempotent on event_id (safe to retry — never double-billed). outcome is 'ok' or 'error' and feeds the SLA report.
Inputs: event_id (required), meter_id (required), quantity (required), outcome, +1 more. Returns: result
sla_reportSla reportCRead-onlyIdempotentInspect
Pure SLA report: success_rate vs sla_target, breach flag. No mutation.
Inputs: meter_id (required). Returns: result
usage_summaryUsage summaryCRead-onlyIdempotentInspect
Totals for a meter: event count, total quantity, accrued minor units.
Inputs: meter_id (required). Returns: result
usage_timeseriesUsage timeseriesAInspect
Usage time series bucketed on each event's recorded_at (UTC; bucket=day|hour), grouped across meters by provider — a real time-series primitive, independent of meter creation times. Includes per-bucket breakdowns by consumer_class / channel / provider. est_accrued_minor is an estimate; authoritative billing stays with usage_summary.
Inputs: since, until, bucket, channel, +4 more. Returns: result
verify_chainVerify chainBRead-onlyIdempotentInspect
Verify the tamper-evident event hash chain for a meter.
Inputs: meter_id (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Agent-native double-entry accounting ledger with x402 micropayments
Usage metering, spend cap (reserve before pay), lease lock, semaphore, heartbeat for agents. Free tr
Governed agent execution: x402 payments, budgets, receipts, verification, and audit.
Agent memory and a signed spending ledger: pay any x402 API, keep a provable receipt.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceEnables autonomous agents to calculate deterministic profit and loss, attribute revenue and costs, and generate signed operational reports using x402 micropayments.MIT
- AlicenseNot gradedqualityDmaintenancePer-agent quota meter for the A2A network, enabling quota checks with USDC settlement on Base L2 via x402 envelopes.MIT
- FlicenseNot gradedqualityDmaintenancePer-customer API usage analytics and billing exports for small B2B APIs. Agents can sign up, get ingest snippets and read usage by customer, endpoint and plan.-
- AlicenseNot gradedqualityCmaintenanceEnables agents to list, preview, confirm, and pay for HTTP resources via x402, while providing a payment ledger and Binance account/market-data context.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.