io.github.entradox/agent-ledger

Est-ce que io.github.entradox/agent-ledger est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.entradox/agent-ledger » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 18 outils

• ledger_alerts≈ 226 tokens

  Alert 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).

  Paramètres, retour & exemple (3)

  Paramètres

  • agent_id · string · requis
    unique agent identifier
  • agent_secret · string · optionnel
    the agent's own secret (either this or workspace_key)
  • workspace_key · string · optionnel
    the owning workspace's key (either this or agent_secret)

  Exemple d'appel

  {"name": "ledger_alerts", "arguments": {"agent_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_api_docs≈ 187 tokens

  Self-serve documentation for AgentLedger — quickstart, MCP tools, REST endpoints, budget caps, error codes, and idempotency usage, as markdown.

  Paramètres, retour & exemple (1)

  Paramètres

  • topic · string · optionnel
    "quickstart" | "mcp" | "rest" | "budget" | "errors" | "idempotency" | "metering" | "events" | "all" (default "" == "all"). Unknown topics fall back to the full docs.

  Exemple d'appel

  {"name": "ledger_api_docs", "arguments": {"topic": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_approval_decide≈ 309 tokens

  Approve or deny a pending spend permit — workspace owner only. The agent's own agent_secret can REQUEST an approval but can never decide one: a credential that can approve its own requests is not a control. decision must be 'approve' or 'deny'; only pending permits can be decided. An approved permit is consumed by the agent's next ledger_track within its amount — it is a one-shot exception, not a raised cap.

  Paramètres, retour & exemple (4)

  Paramètres

  • agent_id · string · requis
    the agent that requested the permit
  • decision · string · requis
    'approve' or 'deny'
  • approval_id · string · requis
    the apr_ id from ledger_request_approval / ledger_approvals
  • workspace_key · string · requis
    the key of the workspace that owns the agent

  Exemple d'appel

  {"name": "ledger_approval_decide", "arguments": {"agent_id": "texte", "decision": "texte", "approval_id": "texte", "workspace_key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_approvals≈ 233 tokens

  List spend-approval permits — yours, or your whole workspace's.

  Paramètres, retour & exemple (4)

  Paramètres

  • state · string · optionnel
    optional filter: pending | approved | denied | consumed | expired
  • agent_id · string · optionnel
    list this agent's permits (needs agent_secret or workspace_key)
  • agent_secret · string · optionnel
    the agent's own secret (agent view)
  • workspace_key · string · optionnel
    the owning workspace's key — lists ALL its agents' permits when given alone

  Exemple d'appel

  {"name": "ledger_approvals", "arguments": {"state": "texte", "agent_id": "texte", "agent_secret": "texte", "workspace_key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_check_spend≈ 464 tokens

  Ask BEFORE you spend: may this agent spend this much right now? Returns allowed (true/false), a stable reason code (within_budget, over_monthly_cap, over_daily_cap, over_monthly_token_cap, over_daily_token_cap, no_budget_set, unpriced_model), a one-line message, the cost estimate, the price used (with its source and as_of date) and every budget window with cap, spent and remaining. Same decision the /proxy/{provider} gate enforces. Read-only: nothing is recorded or reserved, so record the spend with ledger_track afterwards. Give exactly one spend shape: amount_cents (any rail, e.g. an x402 purchase), OR model with tokens_in/tokens_out.

  Paramètres, retour & exemple (7)

  Paramètres

  • model · string · optionnel
    model id to price from tokens (instead of amount_cents)
  • agent_id · string · requis
    the agent that would spend
  • tokens_in · integer · optionnel
    expected input tokens (with model)
  • tokens_out · integer · optionnel
    expected output tokens, e.g. your max_tokens (with model)
  • agent_secret · string · optionnel
    the agent's own secret (either this or workspace_key)
  • amount_cents · ? · optionnel
    the spend in cents, if you already know it
  • workspace_key · string · optionnel
    the owning workspace's key (either this or agent_secret)

  Exemple d'appel

  {"name": "ledger_check_spend", "arguments": {"agent_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_examples≈ 149 tokens

  Complete, runnable Python recipe for a common AgentLedger integration pattern.

  Paramètres, retour & exemple (1)

  Paramètres

  • pattern · string · requis
    "python_tracking" | "budget_enforcement" | "weekly_report" | "retry_safe_writes"

  Exemple d'appel

  {"name": "ledger_examples", "arguments": {"pattern": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_price≈ 366 tokens

  What will this call cost? Priced from the same table the caps use. Exists because ledger_track requires the CALLER to supply amount_cents, so an agent whose spend is capped could under-report its own cost and stay under the cap. This returns the number the enforcement path would use, so an agent can report honestly (and plan before it spends). Cost = (tokens_in * in_rate + tokens_out * out_rate) / 1_000_000. If the model has cache rates, the standard in-rate is used, which is the conservative direction for a spend cap. Every price carries the source it came from and the date it was read, and `verified: false` means the number was NOT read off the provider's own pricing page. Treat an unverified price as an estimate, not a measurement.

  Paramètres, retour & exemple (3)

  Paramètres

  • model · string · requis
    the model id you are about to call (e.g. gpt-4o, claude-sonnet-4)
  • tokens_in · integer · optionnel
    expected input tokens
  • tokens_out · integer · optionnel
    expected output tokens, e.g. your max_tokens

  Exemple d'appel

  {"name": "ledger_price", "arguments": {"model": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_proxy_attach≈ 366 tokens

  Point your provider traffic at the proxy so budget caps are enforced BEFORE the provider is contacted, instead of being reported afterwards. This closes the gap where the brake was unreachable from MCP: an agent connected over MCP could record spend (ledger_track) but nothing could refuse a call. With this, the cap is enforced on every LLM call. Returns the base_url to use, the two headers to send, and the exact change for the OpenAI and Anthropic SDKs. Your provider credential is NOT part of this: it stays in Authorization / x-api-key and is only forwarded, never stored.

  Paramètres, retour & exemple (4)

  Paramètres

  • agent_id · string · requis
    the agent whose budget the proxied calls are billed to
  • provider · string · optionnel
    which upstream to proxy: openai or anthropic
  • agent_secret · string · optionnel
    the agent's own secret (either this or workspace_key)
  • workspace_key · string · optionnel
    the owning workspace's key (either this or agent_secret)

  Exemple d'appel

  {"name": "ledger_proxy_attach", "arguments": {"agent_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_report≈ 274 tokens

  Spend 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).

  Paramètres, retour & exemple (4)

  Paramètres

  • days · integer · optionnel
    report window in days (default 30)
  • agent_id · string · requis
    unique agent identifier
  • agent_secret · string · optionnel
    the agent's own secret (either this or workspace_key)
  • workspace_key · string · optionnel
    the owning workspace's key (either this or agent_secret)

  Exemple d'appel

  {"name": "ledger_report", "arguments": {"agent_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_request_approval≈ 420 tokens

  Ask your workspace owner for a one-shot spend exception before a ledger_track that the cap would refuse. Creates a pending permit for exactly amount_cents on the given service. The owner (a human, or a supervisor agent holding the workspace_key) approves or denies it with ledger_approval_decide. An APPROVED permit is consumed by the next ledger_track for this agent whose amount fits inside it — the budget cap itself does not change. Permits expire after 1 hour undecided. Poll with ledger_approvals to see the decision. Claiming a brand-new agent_id requires workspace_key; otherwise pass the agent's agent_secret.

  Paramètres, retour & exemple (6)

  Paramètres

  • reason · string · optionnel
    why, one line — shown to the approver
  • service · string · requis
    what the money is for (e.g. "openai:gpt-5 batch eval")
  • agent_id · string · requis
    the agent asking for the exception
  • agent_secret · string · optionnel
    the agent's own secret (either this or workspace_key)
  • amount_cents · integer · requis
    the spend to be approved, in cents
  • workspace_key · string · optionnel
    the owning workspace's key (either this or agent_secret)

  Exemple d'appel

  {"name": "ledger_request_approval", "arguments": {"service": "texte", "agent_id": "texte", "amount_cents": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_revoke_secret≈ 234 tokens

  Invalidate an agent_id's agent_secret WITHOUT deleting its spend history. Use when a credential may have leaked, or to stop an agent writing. Subsequent writes to that agent fail with agent_secret_mismatch until you rotate a new secret in. The agent_id stays claimed, so no other workspace can claim it and inherit the ledger. Requires the workspace_key that owns agent_id. Returns {"agent_id", "revoked": True, "_note"}, or {"error", "error_code"}.

  Paramètres, retour & exemple (2)

  Paramètres

  • agent_id · string · requis
  • workspace_key · string · requis

  Exemple d'appel

  {"name": "ledger_revoke_secret", "arguments": {"agent_id": "texte", "workspace_key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_rotate_secret≈ 276 tokens

  Mint a NEW agent_secret for an agent_id your workspace already owns, invalidating the old one. Use this to RECOVER an agent whose secret was lost: the previous credential stops working immediately. Requires the workspace_key that owns agent_id — an agent's own agent_secret cannot rotate itself, because a leaked agent credential must not be able to lock its real owner out. Unlike ledger_track this never claims a new agent_id: an unknown id returns agent_not_claimed. The new secret is returned ONCE. Store it before you drop the response. Returns {"agent_id", "agent_secret", "_note"}, or {"error", "error_code"}.

  Paramètres, retour & exemple (2)

  Paramètres

  • agent_id · string · requis
  • workspace_key · string · requis

  Exemple d'appel

  {"name": "ledger_rotate_secret", "arguments": {"agent_id": "texte", "workspace_key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_set_budget≈ 538 tokens

  Set 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 — with one rule: raising or removing an existing cap requires the workspace_key. An agent_secret can tighten its own caps but never loosen them; to grow an allowance the agent asks its owner (see ledger_request_approval). 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).

  Paramètres, retour & exemple (7)

  Paramètres

  • agent_id · string · requis
    unique agent identifier
  • daily_cents · integer · optionnel
    daily spending cap in cents (0 = no daily cap)
  • agent_secret · string · optionnel
    required for every call after the first for this agent_id
  • daily_tokens · integer · optionnel
    daily token-burn cap (0 = no cap)
  • monthly_cents · integer · requis
    monthly spending cap in cents
  • workspace_key · string · optionnel
    required when claiming a brand-new agent_id; not needed once the agent_id has been claimed
  • monthly_tokens · integer · optionnel
    monthly token-burn cap (0 = no cap)

  Exemple d'appel

  {"name": "ledger_set_budget", "arguments": {"agent_id": "texte", "monthly_cents": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_start≈ 371 tokens

  Get a FREE AgentLedger workspace with no credential and no arguments — the MCP equivalent of opening POST /start in a browser. Call this FIRST if you have no credentials yet. Every other tool here (ledger_track, ledger_set_budget, ledger_report, ledger_alerts) needs a workspace_key or an agent_secret, so a caller arriving with neither must start here or it has nowhere to go. Takes NO arguments on purpose: the goal is zero friction. It returns a `workspace_key` (shown exactly once — it cannot be re-revealed, so store it before continuing) which you then send as `workspace_key` on your first ledger_track for a NEW agent_id. That first write returns the agent's own `agent_secret`, which authenticates every write after it. The free tier includes every rail, enforced budget caps, alerts, reports and the MCP server, capped at 3 agents per workspace. Minting is rate-limited per caller IP, the same limit the human door uses. Prefer to pay? POST /v1/billing/x402 with a wallet-signed payment needs no human and buys 24h of Pro (agent allowance per the live pass tier — see /pricing.md).

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "ledger_start", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_track≈ 606 tokens

  Record 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. Caps here bind the AMOUNT YOU REPORT — a caller that lies to amount_cents lies to the cap. The only enforcement against real spend is routing the provider call through the /proxy/{provider} rail, which prices from the provider's own usage block. Include tokens_in/tokens_out + model on every LLM call so token burn shows up in the /v1/tokens report.

  Paramètres, retour & exemple (9)

  Paramètres

  • rail · string · requis
    payment rail used — one of "mpp", "x402", "api_key", "manual"
  • model · string · optionnel
    model name (e.g. "gpt-4o") — token burn is reported per model
  • service · string · requis
    what was purchased (e.g. "search_query", "data_export")
  • agent_id · string · requis
    unique agent identifier (e.g. "research-agent-v2")
  • tokens_in · integer · optionnel
    prompt tokens consumed (0 if unknown)
  • tokens_out · integer · optionnel
    completion tokens consumed (0 if unknown)
  • agent_secret · string · optionnel
    required for every call after the first for this agent_id
  • amount_cents · integer · requis
    spend amount in cents (100 = $1.00), 0-10000000
  • workspace_key · string · optionnel
    required when claiming a brand-new agent_id; not needed once the agent_id has been claimed

  Exemple d'appel

  {"name": "ledger_track", "arguments": {"rail": "texte", "service": "texte", "agent_id": "texte", "amount_cents": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_wait_events≈ 755 tokens

  Long-poll an agent's event feed — how an agent with no public URL receives alerts. Webhooks (POST /v1/webhooks) push events to a URL you own; an agent on stdio MCP cannot host one, so it waits here instead. Call this in a loop: the call holds open up to `timeout` seconds (max 30) and returns when events arrive or the wait lapses. `consumer_id` names this consumer durably — pick a stable one (e.g. "claude-code-main") and reuse it. Each call returns a `cursor`; pass it back on your next call once you have processed that batch — that is the ack. To get restart redelivery, also pass `client_instance` (your process id or any per-boot token) and `client_started` (when your process booted): when the pair changes, events that were served but never acked come back with `redelivered: true`, so nothing is lost to a crash between serve and process. (The stdio MCP server supplies its own pid/started automatically — hosted callers must opt in because the gateway cannot see the client's process.) Each event is an envelope: id (deterministic — dedupe on it), kind (alert.raised | budget.warning | budget.exceeded | anomaly.detected), summary, context (agent_id, alert_type, timestamp), alerts_since_last_write (how many alerts are stacked up since the agent's last spend write — use it to throttle escalation), redelivered. Requires a credential: either the agent's own agent_secret or its workspace's workspace_key (same rule as GET /v1/agents/{agent_id}/events/wait).

  Paramètres, retour & exemple (9)

  Paramètres

  • name · string · optionnel
    optional label for this consumer instance
  • cursor · ? · optionnel
    line offset you have processed through (omit to continue)
  • timeout · ? · optionnel
    seconds to hold the call open (default 5, max 30)
  • agent_id · string · requis
    unique agent identifier
  • consumer_id · string · requis
    durable name for this consumer (1-64 chars, [A-Za-z0-9._-])
  • agent_secret · string · optionnel
    the agent's own secret (either this or workspace_key)
  • workspace_key · string · optionnel
    the owning workspace's key (either this or agent_secret)
  • client_started · string · optionnel
    when your process booted — paired with client_instance
  • client_instance · string · optionnel
    your process identity (e.g. pid or per-boot token) — enables restart redelivery

  Exemple d'appel

  {"name": "ledger_wait_events", "arguments": {"agent_id": "texte", "consumer_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• read_skill≈ 103 tokens

  Read a product skill file by its skill:// URI.

  Paramètres, retour & exemple (1)

  Paramètres

  • uri · string · requis
    e.g. skill://<product>/<skill-name>/SKILL.md Get valid URIs from `skills_list_tool`.

  Exemple d'appel

  {"name": "read_skill", "arguments": {"uri": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• skills_list_tool≈ 101 tokens

  List this product's skills. Each entry carries the SKILL.md URI, its name and description, verbatim frontmatter, and a per-file sha256 manifest. Read a body with `read_skill`.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "skills_list_tool", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://aiagentscity.com/mcp/