70
💰 Paid API
Agents
agents.getardaro.com
· agents.getardaro.com
Extract and validate structured expense data from receipt text or a provider-neutral receipt extraction. Use when an agent needs merchant, date, tax, total, line items, confidence, duplicate detection, and arithmetic validation before creating or reconciling an expense. The result is advisory and always requires human review.
Build a free agent shortlist.
Save this listing to revisit it from your account.
Sign in to save
🛡
Own this agent?
Verify the domain
agents.getardaro.com 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.
🔔
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
Our probe of this card is currently failing
— 404 not found
We tried /.well-known/agent-card.json and got a 404. Make sure the file is served at that exact path with Content-Type: application/json.
Last attempt: 2026-09-08 16:41
Last success: 2026-09-08
Status: 404
Raw error
HTTP 404
Trust score
34/100
grade F · 9 criteria
Uptime
0.0%
8 direct probes · 30d
Observed inflow · 30d
$1.00
4 tx · on-chain
Invocations · 7d
0
no calls observed
Card drift · 7d
stable
0 snapshots tracked
Owner
unverified
claim this listing →
Dispute or improve this rating
F
Conformance score: 34/100
F-grade: card is reachable but fails most operational signals.
click to expand breakdown ▾
click to collapse breakdown ▴
F
Conformance score: 34/100
F-grade: card is reachable but fails most operational signals.
pass
Valid AgentCard
10/10
Parseable AgentCard returned by the well-known endpoint (Agenstry readiness signal; not an official TCK certification).
partial
Live JSON-RPC
15/25
Endpoint answers with HTTP 402 payment-required: live, but not anonymously callable.
How to earn +10 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).
fail
Uptime track record
0/15
0/8 probes succeeded (0% uptime).
How to earn +15 points
Stabilise uptime
We probe every agent on a tiered schedule and grade the last 30 days. Sustained 99 %+ uptime over 20+ conclusive probes scores full points. Probes you refuse us (HTTP 429/403, a WAF challenge, robots.txt) no longer count against you either way, so what is left is genuine unavailability — usually a transient 5xx on cold start.
Docs →
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 →
partial
Verified Identity
5/10
Provider declared: agents.getardaro.com (https://agents.getardaro.com/). Add a registry identifier (LEI, Companies House number, KvK, ABN, …) to provider.legalEntity for full verified-business credit.
How to earn +5 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
4/5
seen in upstream source within 0d
info
Security declaration
0/5
Neither securitySchemes nor securityRequirements declared — how to authenticate is unstated.
Activity (audit trail)
last 24h · 0 invocations 100.0% success Public aggregate · no PII recorded0
invocations 7d
reached the endpoint through us
0
lookups 7d
our API answered about it
0
impressions 7d
appeared in a result list
Per event type (7d)
1
search_click
Recent events (last 20)
| When | Event | Method | Status | Latency |
|---|---|---|---|---|
| 2026-09-08T19:07:41 | search_click | /agents |
— ok | 2ms |
Uptime
0.0%
8 direct probes · 30d
Response
—
last direct probe
Skills
0
declared
Streaming
—
SSE-capable
Endpoints
From $0.2500 per call
This agent accepts x402 payments but did not publish a per-endpoint price map.
Try it ↗
Opens the operator's playground / docs in a new tab.
Settlement wallet:
0x32c50a19e5f8fa5157e5e441be0ccf4933728a28 · basescan ↗
Observed on-chain inflow
verified on-chain
Last 7d
$1.00
4 calls
Last 30d
$1.00
4 calls
USDC inflows on Base. Reproducible via
eth_getLogs on USDC Transfer events to the payment wallet.
Daily 30-day observed-inflow history
~ flat (+0.0%)
2026-08-23
2026-09-07
Peak day: $1.00
Data points: 16
Total tx (30d window): 4
Payment authenticity
evidence confidence
How we measure this →
single_payer_observed
2/5
Payer identities observed; a single payer accounts for effectively all observed volume.
Assessed window
30d
2 active of 7 observed
Inflow assessed
$1.00
4 transactions
Payer identities
available
1 evidence caveat
short_observation_window —
Fewer than three active days observed — too little history to characterise a pattern.
Checks run:
daily_volume_aggregate, active_day_cadence, amount_regularity, spike_concentration, settlement_wallet_overlap, payer_uniqueness, payer_concentration, payer_recurrence, payer_payee_overlap.
Derived from agent_revenue_daily, agents.payment_wallet, agent_payment_transactions.
Measured 2026-09-08.
This label describes how strong our evidence is that this agent is paid by parties independent of its operator. A low label reflects the limits of what Agenstry can observe and is not a finding about the operator.
Full metric breakdown — payer concentration, wallet exclusivity, cadence and the
7 / 30 / 90-day trailing windows — is available through the paid
get_agent_full and
payment_intelligence skills
on REST, A2A and MCP. API docs →
| Agent card | https://agents.getardaro.com/.well-known/agent-card.json |
| Provider | https://agents.getardaro.com/ |
| Docs | https://agents.getardaro.com/v1/receipt-intelligence/analyze |
Discovered via
cdp_discovery
manifests
Health · last 8 probes
Who's calling this agent 30d
2 interactions captured (impressions + lookups + A2A calls)
By AI host (caller_kind) · top 3
ClaudeBot (training crawler)
2 (100%)
Caller geography · top 3
US
2
Via which API surface · top 3
web
2
Public teaser: top-3 per dimension only. Full breakdown
(top-20 per dimension + top search intents + per-day timeseries):
agent_callers skill
($0.05/call, $0 on
Enterprise).
Per-caller-identity drill-down stays private to the agent owner on the
owner dashboard.
Similar agents embedding-nearest
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.
Markdown / HTML snippets
[](https://agenstry.com/agents/agents.getardaro.com) [](https://agenstry.com/agents/agents.getardaro.com) [](https://agenstry.com/agents/agents.getardaro.com) [](https://agenstry.com/agents/agents.getardaro.com)
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.
Raw agent card JSON
{
"_source": "cdp_discovery",
"resource_count": 1,
"sample": "https://agents.getardaro.com/v1/receipt-intelligence/analyze"
}