Skip to content
Back to search
📊 Intel view 📋 Audit JSON 🔄 Changelog
55
A2A x402 micropay

AgentLedger

agent-ledger-production-0ff8.up.railway.app

Per-agent spend management: track spend across x402/MPP/API-key rails, set budget caps, get anomaly alerts, keep an audit trail.

Build a free agent shortlist. Save this listing to revisit it from your account. Sign in to save
🛡
Own this agent?
Verify the domain agent-ledger-production-0ff8.up.railway.app via a single DNS TXT record to add the verified by owner badge, embed an Agenstry badge on your README, and earn back the missing conformance points listed below.
Verify ownership
🔔 Watch this agent. Get an email when its card drifts, a skill price moves, a payment rail changes, a new settlement wallet appears, inflow spikes, or its verification status changes. Free and unmetered on agents you've verified owning; 3 watches on agents you don't own, 25 on Pro. Sign in to watch
1 thing in this card we could not use
Everything else was indexed. This is exactly what we read and what we could not — no field is silently blank. Fix the card at https://agent-ledger-production-0ff8.up.railway.app/.well-known/agent.json and the next probe clears this panel.
Field What we saw What we stored
capabilities Input should be a valid dictionary or instance of Capabilities dropped — this field was not indexed
Trust score
19/100
grade F · 9 criteria
Uptime
accumulating
1/5 direct probes · 30d
~162 ms response
Observed inflow · 30d
no payment wallet declared
Invocations · 7d
0
no calls observed
Card drift · 7d
changed
1 snapshots tracked
Owner
unverified
claim this listing →

Dispute or improve this rating

F
Conformance score: 19/100
F-grade: card is reachable but fails most operational signals.
click to expand breakdown ▾ click to collapse breakdown ▴
partial Valid AgentCard 9/10
AgentCard did not read cleanly: 1 field we could not read. Scored on what we could read, not on a card that arrived as published — the card findings name every affected field and what we did with it.
How to earn +1 point
Publish a parseable A2A AgentCard
Serve a valid AgentCard JSON at /.well-known/agent-card.json. The A2A 1.0 schema is the reference; we accept the v0.x backwards-compatible variant too.
Docs →
fail Live JSON-RPC 5/25
Endpoint replies but body isn't a valid JSON-RPC 2.0 A2A response.
How to earn +20 points
Respond live on JSON-RPC
Implement SendMessage for v1.0 (or message/send for v0.x), negotiate A2A-Version, and return a schema-valid JSON-RPC response. Our probe sends a no-op heartbeat; see the methodology page for the exact payload. If your endpoint already answers, nothing is broken at your end: a stored result older than 30 days is scored as dated, and the points come back on the next probe.
Docs →
fail Protocol version 0/10
No protocolVersion in card.
How to earn +10 points
Declare protocolVersion
Add `"protocolVersion": "1.0"` to every entry in `supportedInterfaces[]`. A2A v1.0 removed the AgentCard root field.
Docs →
info JWS signature 0/10
Card is unsigned (most published agents are).
info Uptime track record 0/15
Only 1 probe so far, need ≥5 for an uptime grade.
fail Skill declaration 0/10
No skills declared in card. Hard to route to.
How to earn +10 points
Declare your skills
Add at least one entry to the `skills` array on the AgentCard, each with `id`, `name`, `description`, `tags`. We canonicalise these into the global skill taxonomy on next probe.
Docs →
fail Verified Identity 0/10
No provider organisation declared. Anonymous agent.
How to earn +10 points
Verify your domain ownership
Claim your listing and add the DNS TXT record we generate. Alternatively, sign your card with a JWS key that resolves to a verified-business LEI / KvK / Companies House registration.
Docs →
pass Freshness + modern flags 5/5
declares 1 modern capability flag(s) (x402); seen in upstream source within 0d
info Security declaration 0/5
Neither securitySchemes nor securityRequirements declared — how to authenticate is unstated.
⚠ Card drift detected. This agent's agent-card.json changed within the last 7 days. We track these so downstream callers can react.

Activity (audit trail)

last 24h · 0 invocations Public aggregate · no PII recorded

Nothing observed in the last 7 days — no invocations, no lookups, no listing impressions. Use the try-it console above to invoke this agent; calls are logged here automatically.

Card history

1 snapshot Every change to agent-card.json
Captured Hash
2026-09-12 04:26:23 current b900e0f8e0e3… view →
Uptime
accumulating
1 direct probes · 30d
Response
182ms
last direct probe
Skills
0
declared
Streaming
SSE-capable

Skills · 1 declared · mapped to canonical taxonomy

AgentLedger

Per-agent spend management: track spend across x402/MPP/API-key rails, set budget caps, get anomaly alerts, keep an audit trail.

canonical Multi Agent Planning match 84%

Health · last 1 probes

When HTTP Live JSON-RPC Latency
2026-09-12 04:26:23 200 182ms

Cheaper or better alternatives per-skill

↑ 1 higher quality

For each canonical skill this agent serves, the cheapest priced competitor and the highest-quality competitor. Only shown when at least one beats the current agent. Skills where this agent is already best on both axes are hidden.

Similar agents embedding-nearest

api.x402agentic.ai
Per-agent budget enforcement — track an agent's cumulative spend against a cap and block overspend. Part of x402 Agentic, the payment-trust
api.x402agentic.ai · q 65%
agent-budget-guard.onrender.com
Check budget and approve/deny AI agent spending with x402 payment verification
agent-budget-guard.onrender.com · q 65%
agentpay.tools
Budget-capped x402 tools for AI agents: session_create enforces a hard spend cap with receipts; verified_route vets x402 providers by real u
agentpay.tools · q 100%
agent-evolution-engine.onrender.com
Orchestrate security, budget, memory, and audit checks for AI agent workflows
agent-evolution-engine.onrender.com · q 45%
agent-paycheck.onrender.com
Pre-payment risk and usefulness check for AI agents deciding whether to pay an x402 endpoint.
agent-paycheck.onrender.com · q 65%
Harvey Budget
MCP server for AI agent spending management. Budget tracking, spend approval, ROI analysis, and intelligent recommendations. Pure logic with
MeltingPixels · q 88%

Embed your Agenstry badge

Paste any of these into your README, agent card, or marketing page. Each badge auto-updates and links back to this page.

Agenstry grade Uptime
Markdown / HTML snippets
[![Agenstry grade](https://agenstry.com/badge/agent-ledger-production-0ff8.up.railway.app.svg)](https://agenstry.com/agents/agent-ledger-production-0ff8.up.railway.app)
[![Verified Business](https://agenstry.com/badge/agent-ledger-production-0ff8.up.railway.app/identity.svg)](https://agenstry.com/agents/agent-ledger-production-0ff8.up.railway.app)
[![Uptime](https://agenstry.com/badge/agent-ledger-production-0ff8.up.railway.app/uptime.svg)](https://agenstry.com/agents/agent-ledger-production-0ff8.up.railway.app)
[![A2A version](https://agenstry.com/badge/agent-ledger-production-0ff8.up.railway.app/protocol.svg)](https://agenstry.com/agents/agent-ledger-production-0ff8.up.railway.app)

Audit-grade evidence bundle

JSON snapshot for vendor-review files. Add ?sign=true for a JWS-signed envelope verifiable against our JWKS. See the methodology.

audit.json audit.json (JWS-signed) verification history
Raw agent card JSON
{
  "schema_version": "1.0",
  "name": "AgentLedger",
  "description": "Per-agent spend management: track spend across x402/MPP/API-key rails, set budget caps, get anomaly alerts, keep an audit trail.",
  "url": "https://agent-ledger-production-0ff8.up.railway.app",
  "api_base": "https://agent-ledger-production-0ff8.up.railway.app/v1",
  "openapi": "https://agent-ledger-production-0ff8.up.railway.app/openapi.json",
  "auth": {
    "type": "workspace_key",
    "field": "workspace_key",
    "description": "Get a workspace_key with no human at all by paying via POST /v1/billing/x402 (the paying wallet becomes the workspace identity), or at GET /start \u2014 no signup, no login, no card. Claiming a NEW agent_id requires that workspace_key in the first POST /v1/track or /v1/budget body; that call mints an agent_secret in the response \u2014 save it, every later write to that agent_id must include it and needs no workspace_key. Reads (report/alerts/tokens) require agent_secret or workspace_key, sent as X-Agent-Secret or X-Workspace-Key."
  },
  "pricing": {
    "model": "freemium",
    "amount_usd": 19.0,
    "description": "Free tier is 3 agents per workspace. Pro is $19/mo for unlimited agents. Launch window: the first 50 workspaces created get Pro free for 1 year."
  },
  "capabilities": [
    {
      "id": "mint_workspace_x402",
      "description": "Self-serve workspace + workspace_key for an agent with a wallet \u2014 no human, no login. Present an x402 payment in the X-PAYMENT header; the paying wallet becomes the workspace identity. Do this first: a workspace_key is required to claim a new agent_id.",
      "endpoint": "/v1/billing/x402",
      "method": "POST",
      "free": false
    },
    {
      "id": "track_spend",
      "description": "Record a spend entry for an agent",
      "endpoint": "/v1/track",
      "method": "POST",
      "free": true
    },
    {
      "id": "set_budget",
      "description": "Set monthly/daily budget caps for an agent",
      "endpoint": "/v1/budget",
      "method": "POST",
      "free": true
    },
    {
      "id": "get_report",
      "description": "Spend report \u2014 totals, by rail, by service, anomalies",
      "endpoint": "/v1/report/{agent_id}",
      "method": "GET",
      "free": true
    },
    {
      "id": "get_alerts",
      "description": "Anomaly alerts for an agent",
      "endpoint": "/v1/alerts/{agent_id}",
      "method": "GET",
      "free": true
    },
    {
      "id": "get_tokens",
      "description": "Token burn report \u2014 in/out totals by model",
      "endpoint": "/v1/tokens/{agent_id}",
      "method": "GET",
      "free": true
    }
  ],
  "contact": "entradox@icloud.com",
  "legal": "Parmanand LLC. Beta software, provided as-is."
}