api.walletforge.app

https://api.walletforge.app/v1/fetch-markdown

Shares a payout wallet with 3 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.

Fetch a public URL and return cleaned markdown

59
reliability

Reliability & health

Uptime and response time from our own unpaid probes, plus the reliability score built from them.

7 days 30 days

Uptime

100.0% avg
0% 50% 100% Tue 1 PMThu 4 PMSat 6 PMTue 7 AM

Response time

p50 32ms · p95 34ms
0ms 50ms 100ms Tue 1 PMThu 4 PMSat 6 PMTue 7 AM
Data table
Reliability history per time bucket over the last 7 days (hourly).
Bucket Uptime Probes Response time
9/29/2026, 1:00:00 PM 100% 1 31ms
9/29/2026, 3:00:00 PM 100% 1 32ms
9/29/2026, 4:00:00 PM 100% 1 33ms
9/29/2026, 7:00:00 PM 100% 1 32ms
9/29/2026, 8:00:00 PM 100% 1 37ms
9/29/2026, 10:00:00 PM 100% 1 32ms
9/30/2026, 12:00:00 AM 100% 1 32ms
9/30/2026, 3:00:00 AM 100% 1 32ms
9/30/2026, 5:00:00 AM 100% 1 33ms
9/30/2026, 7:00:00 AM 100% 1 33ms
9/30/2026, 9:00:00 AM 100% 1 36ms
9/30/2026, 11:00:00 AM 100% 1 38ms
9/30/2026, 1:00:00 PM 100% 1 31ms
9/30/2026, 3:00:00 PM 100% 1 33ms
9/30/2026, 5:00:00 PM 100% 1 31ms
9/30/2026, 7:00:00 PM 100% 1 31ms
9/30/2026, 9:00:00 PM 100% 1 31ms
9/30/2026, 11:00:00 PM 100% 1 31ms
10/1/2026, 1:00:00 AM 100% 1 31ms
10/1/2026, 3:00:00 AM 100% 1 31ms
10/1/2026, 5:00:00 AM 100% 1 31ms
10/1/2026, 7:00:00 AM 100% 1 31ms
10/1/2026, 9:00:00 AM 100% 1 30ms
10/1/2026, 11:00:00 AM 100% 1 32ms
10/1/2026, 1:00:00 PM 100% 1 30ms
10/1/2026, 3:00:00 PM 100% 1 32ms
10/1/2026, 4:00:00 PM 100% 1 30ms
10/1/2026, 6:00:00 PM 100% 1 31ms
10/1/2026, 8:00:00 PM 100% 1 32ms
10/1/2026, 10:00:00 PM 100% 1 33ms
10/2/2026, 12:00:00 AM 100% 1 31ms
10/2/2026, 2:00:00 AM 100% 1 32ms
10/2/2026, 4:00:00 AM 100% 1 32ms
10/2/2026, 6:00:00 AM 100% 1 31ms
10/2/2026, 8:00:00 AM 100% 1 34ms
10/2/2026, 10:00:00 AM 100% 1 32ms
10/2/2026, 12:00:00 PM 100% 1 31ms
10/2/2026, 2:00:00 PM 100% 1 30ms
10/2/2026, 4:00:00 PM 100% 1 32ms
10/2/2026, 6:00:00 PM 100% 1 30ms
10/2/2026, 8:00:00 PM 100% 1 33ms
10/2/2026, 11:00:00 PM 100% 1 30ms
10/3/2026, 12:00:00 AM 100% 1 34ms
10/3/2026, 2:00:00 AM 100% 1 30ms
10/3/2026, 4:00:00 AM 100% 1 31ms
10/3/2026, 6:00:00 AM 100% 1 31ms
10/3/2026, 8:00:00 AM 100% 1 30ms
10/3/2026, 10:00:00 AM 100% 1 33ms
10/3/2026, 12:00:00 PM 100% 1 32ms
10/3/2026, 2:00:00 PM 100% 1 31ms
10/3/2026, 4:00:00 PM 100% 1 31ms
10/3/2026, 6:00:00 PM 100% 1 33ms
10/3/2026, 8:00:00 PM 100% 1 33ms
10/3/2026, 11:00:00 PM 100% 1 32ms
10/4/2026, 1:00:00 AM 100% 1 31ms
10/4/2026, 3:00:00 AM 100% 1 32ms
10/4/2026, 5:00:00 AM 100% 1 32ms
10/4/2026, 7:00:00 AM 100% 1 34ms
10/4/2026, 9:00:00 AM 100% 1 32ms
10/4/2026, 1:00:00 PM 100% 1 34ms
10/4/2026, 3:00:00 PM 100% 1 32ms
10/4/2026, 5:00:00 PM 100% 1 32ms
10/4/2026, 7:00:00 PM 100% 1 33ms
10/4/2026, 9:00:00 PM 100% 1 30ms
10/5/2026, 2:00:00 AM 100% 1 32ms
10/5/2026, 7:00:00 AM 100% 1 33ms
10/5/2026, 9:00:00 AM 100% 1 32ms
10/5/2026, 11:00:00 AM 100% 1 31ms
10/5/2026, 1:00:00 PM 100% 1 33ms
10/5/2026, 2:00:00 PM 100% 1 30ms
10/5/2026, 4:00:00 PM 100% 1 55ms
10/5/2026, 6:00:00 PM 100% 1 31ms
10/5/2026, 8:00:00 PM 100% 1 32ms
10/5/2026, 10:00:00 PM 100% 1 32ms
10/6/2026, 1:00:00 AM 100% 1 31ms
10/6/2026, 2:00:00 AM 100% 1 32ms
10/6/2026, 5:00:00 AM 100% 1 31ms
10/6/2026, 7:00:00 AM 100% 1 31ms
59
Composite reliability — the weighted average of the dimensions below, on a 0–100 scale.
Availability
96

How often it was reachable when we probed it (weight 35%).

Latency
100

How quickly it answers when it is up — fast scores high (weight 20%).

Security
100

Whether it serves over working TLS / https (weight 15%).

Transparency
61

Whether the operator disclosed what it does — description, schema, identity (weight 15%).

Activity
4

Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).

Confidence 100% — how much probe evidence backs this score. A thin history is flagged, not hidden.

See the scoring methodology for exactly how each number is computed.

Payment

Currencies
USDC
Networks
base
Facilitator
unknown
SDK
unknown

Operator

Company
inferred — unknown
Jurisdiction
—
Registrar
Dynadot LLC.
Domain registered
2025-10-28
Hosting network
GOOGL-2
Hosting country
—

Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.

On-chain activity (base)

33
payments (30d)
0.97
USD volume (30d)
5
paying wallets (30d)

Payments per day

last payment 9/18/2026
0 10 20 Sep 7Sep 9Sep 14Sep 18
Data table
Settled payments per day.
Day Payments Volume (USD) Paying wallets
9/7/2026 1 0.01 1
9/8/2026 2 0.1 1
9/9/2026 1 0.05 1
9/13/2026 3 0.11 3
9/14/2026 15 0.51 1
9/17/2026 4 0.12 1
9/18/2026 7 0.07 1

Payout address changed 1 time, last on 9/17/2026

  • 0xb5F5…8E94 → 0x405b…201c (base) · 9/17/2026

A changed payout address is worth a second look — it can be routine, but it is also how a hijacked listing redirects funds.

This payout wallet is shared: figures cover all 4 endpoints paid at it, since payments cannot be attributed to one of them. Only payments settled on chains and facilitators we index.

Linked by wallet — likely same operator

On-chain agent identity and the x402 endpoint that shares its settlement wallet.

https://api.walletforge.app/v1/wallet/usdc-transfers x402 endpoint https://api.walletforge.app/v1/wallet/balance x402 endpoint https://api.walletforge.app/v1/normalize x402 endpoint
Response schema 
{}