Pink Agentic AI Payments (by PinkWallet): lets Claude, ChatGPT, Cursor pay vendor invoices within company spending rules (budgets, caps, allow-lists, human approval). Sandbox preview, test money.
Nothing to run from here
AgentLedger is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
18
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Meter, cap, and block AI agent spend before the provider is charged.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http entradox-agentledger-mcp https://aiagentscity.com/mcp/
# 2 — ask your agent for something these tools do
# ledger_rotate_secret, ledger_revoke_secret, ledger_track and 15 more
AgentLedger costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ENAll 8 servers
entradox8 servers
6 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http entradox-agentledger-mcp https://aiagentscity.com/mcp/Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
18 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | — |
| workspace_key | string | yes | — |
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", "re
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | — |
| workspace_key | string | yes | — |
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 t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | unique agent identifier (e.g. "research-agent-v2") |
| rail | string | yes | payment rail used — one of "mpp", "x402", "api_key", "manual" |
| amount_cents | integer | yes | spend amount in cents (100 = $1.00), 0-10000000 |
| service | string | yes | what was purchased (e.g. "search_query", "data_export") |
| tokens_in | integer | no | prompt tokens consumed (0 if unknown) |
| tokens_out | integer | no | completion tokens consumed (0 if unknown) |
| model | string | no | model name (e.g. "gpt-4o") — token burn is reported per model |
| agent_secret | string | no | required for every call after the first for this agent_id |
| workspace_key | string | no | required when claiming a brand-new agent_id; not needed once the agent_id has been claimed |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | unique agent identifier |
| monthly_cents | integer | yes | monthly spending cap in cents |
| daily_cents | integer | no | daily spending cap in cents (0 = no daily cap) |
| monthly_tokens | integer | no | monthly token-burn cap (0 = no cap) |
| daily_tokens | integer | no | daily token-burn cap (0 = no cap) |
| agent_secret | string | no | required for every call after the first for this agent_id |
| workspace_key | string | no | required when claiming a brand-new agent_id; not needed once the agent_id has been claimed |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | unique agent identifier |
| days | integer | no | report window in days (default 30) |
| agent_secret | string | no | the agent's own secret (either this or workspace_key) |
| workspace_key | string | no | the owning workspace's key (either this or agent_secret) |
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 se
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | the agent whose budget the proxied calls are billed to |
| provider | string | no | which upstream to proxy: openai or anthropic |
| agent_secret | string | no | the agent's own secret (either this or workspace_key) |
| workspace_key | string | no | the owning workspace's key (either this or agent_secret) |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | unique agent identifier |
| agent_secret | string | no | the agent's own secret (either this or workspace_key) |
| workspace_key | string | no | the owning workspace's key (either this or agent_secret) |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | unique agent identifier |
| consumer_id | string | yes | durable name for this consumer (1-64 chars, [A-Za-z0-9._-]) |
| agent_secret | string | no | the agent's own secret (either this or workspace_key) |
| workspace_key | string | no | the owning workspace's key (either this or agent_secret) |
| cursor | no | line offset you have processed through (omit to continue) | |
| timeout | no | seconds to hold the call open (default 5, max 30) | |
| client_instance | string | no | your process identity (e.g. pid or per-boot token) — enables restart redelivery |
| client_started | string | no | when your process booted — paired with client_instance |
| name | string | no | optional label for this consumer instance |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | the agent that would spend |
| amount_cents | no | the spend in cents, if you already know it | |
| model | string | no | model id to price from tokens (instead of amount_cents) |
| tokens_in | integer | no | expected input tokens (with model) |
| tokens_out | integer | no | expected output tokens, e.g. your max_tokens (with model) |
| agent_secret | string | no | the agent's own secret (either this or workspace_key) |
| workspace_key | string | no | the owning workspace's key (either this or agent_secret) |
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 — t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | the agent asking for the exception |
| amount_cents | integer | yes | the spend to be approved, in cents |
| service | string | yes | what the money is for (e.g. "openai:gpt-5 batch eval") |
| reason | string | no | why, one line — shown to the approver |
| agent_secret | string | no | the agent's own secret (either this or workspace_key) |
| workspace_key | string | no | the owning workspace's key (either this or agent_secret) |
List spend-approval permits — yours, or your whole workspace's.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | no | list this agent's permits (needs agent_secret or workspace_key) |
| workspace_key | string | no | the owning workspace's key — lists ALL its agents' permits when given alone |
| agent_secret | string | no | the agent's own secret (agent view) |
| state | string | no | optional filter: pending | approved | denied | consumed | expired |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | the agent that requested the permit |
| approval_id | string | yes | the apr_ id from ledger_request_approval / ledger_approvals |
| decision | string | yes | 'approve' or 'deny' |
| workspace_key | string | yes | the key of the workspace that owns the agent |
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)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| model | string | yes | the model id you are about to call (e.g. gpt-4o, claude-sonnet-4) |
| tokens_in | integer | no | expected input tokens |
| tokens_out | integer | no | expected output tokens, e.g. your max_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 o
No parameter schema on file.
Self-serve documentation for AgentLedger — quickstart, MCP tools, REST endpoints, budget caps, error codes, and idempotency usage, as markdown.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | no | "quickstart" | "mcp" | "rest" | "budget" | "errors" | "idempotency" | "metering" | "events" | "all" (default "" == "all"). Unknown topics fall back to the full docs. |
Complete, runnable Python recipe for a common AgentLedger integration pattern.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pattern | string | yes | "python_tracking" | "budget_enforcement" | "weekly_report" | "retry_safe_writes" |
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.
No parameter schema on file.
Read a product skill file by its skill:// URI.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| uri | string | yes | e.g. skill://<product>/<skill-name>/SKILL.md Get valid URIs from skills_list_tool. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install AgentLedger or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.4.6.
0.4.6
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish AgentLedger can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.