40
💰 Paid API
Recallguard-Api
recallguard-api.vercel.app
· recallguard-api.vercel.app
RecallGuard inventory matcher: match up to 100 items against US recalls, $0.10 per call
Build a free agent shortlist.
Save this listing to revisit it from your account.
Sign in to save
🛡
Own this agent?
Verify the domain
recallguard-api.vercel.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.
🔔
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-10-05 07:53
Last success: 2026-10-05
Status: 404
Raw error
HTTP 404
Trust score
34/100
grade F · 9 criteria
Uptime
accumulating
3/5 direct probes · 30d
Observed inflow · 30d
$2.51
2 tx · on-chain
Invocations · 7d
0
2 listing impressions — no calls
Card drift · 7d
changed
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"` (Major.Minor, no patch number — §3.6) 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 3 probes 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` — `description` and `tags` are REQUIRED on AgentSkill since A2A v1.0, and tags are what discovery filters match on. We canonicalise these into the global skill taxonomy on next probe.
Docs →
partial
Verified Identity
5/10
Provider declared: recallguard-api.vercel.app (https://recallguard-api.vercel.app/). 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.
⚠ 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 recorded0
invocations 7d
reached the endpoint through us
0
lookups 7d
our API answered about it
2
impressions 7d
appeared in a result list
Per event type (7d)
2
search_impression
Recent events (last 20)
| When | Event | Method | Status | Latency |
|---|---|---|---|---|
| 2026-10-04T01:45:15 | search_impression | — |
200 ok | — |
| 2026-10-04T01:45:08 | search_impression | — |
200 ok | — |
Uptime
accumulating
3 direct probes · 30d
Response
—
last direct probe
Skills
0
declared
Streaming
—
SSE-capable
Endpoints
From $0.0500 per call
| Endpoint | Price | Currency |
|---|---|---|
https://recallguard-api.vercel.app/api/v1/feed
|
0.05 | USDC |
https://recallguard-api.vercel.app/api/v1/match
|
0.1 | USDC |
Try it ↗
Opens the operator's playground / docs in a new tab.
Settlement wallet:
0x90e23a7b6f6494a879d05ddc4278d0e55dec1e01 on Base
· basescan ↗
Listed by facilitators
PayAI · 1
Observed on-chain inflow
verified on-chain
Last 7d
$2.51
2 transfers · synced 2026-10-03
Last 30d
$2.51
2 transfers · synced 2026-10-03
USDC inflows on Base. Reproducible via eth_getLogs on USDC Transfer events to the wallet. Inflow to a wallet, not proof that every transfer was a paid call.
How the last 30 days were settled
x402-settled: $0.00 (0%)
· 0 transfers sent by a known x402 facilitator
Other: $0.00 plain transfers sent by the payer · $2.41 other contract calls.
How we classify
Daily 30-day observed-inflow history
2026-10-02
2026-10-05
Last 30 days
Peak 30-day total: $2.51
Data points: 4
Total tx (30d window): 2
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 29 observed
Inflow assessed
$2.51
2 transactions
Payer identities
available
2 evidence caveats
single_day_concentration —
Most observed volume landed on a single day of the window.
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-10-04.
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
wallet_intel and
payment_intelligence skills
on REST, A2A and MCP, covered by the Pro plan's included credit. API docs →
| Agent card | https://recallguard-api.vercel.app/.well-known/agent-card.json |
| Provider | https://recallguard-api.vercel.app/ |
| Docs | https://recallguard-api.vercel.app/api/v1/match |
Discovered via
cdp_discovery
recrawl_warm
Health · last 3 probes
Who's calling this agent 30d
2 interactions captured (impressions + lookups + A2A calls)
By AI host (caller_kind) · top 3
curl
2 (100%)
Caller geography · top 3
US
2
Via which API surface · top 3
rest
2
Public view: top 3 per dimension. 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/recallguard-api.vercel.app) [](https://agenstry.com/agents/recallguard-api.vercel.app) [](https://agenstry.com/agents/recallguard-api.vercel.app) [](https://agenstry.com/agents/recallguard-api.vercel.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.
Raw agent card JSON
{
"_source": "cdp_discovery",
"resource_count": 1,
"sample": "https://recallguard-api.vercel.app/api/v1/match"
}