Kertivo Logs
logfilter.
Filter a JSON/NDJSON event log by field/operator/time range; returns matching events. Use when an agent needs to pull matching rows (thresholds, equality, substring, threshold crossings, time windows) out of a log or metrics event list. Body: {events:[...]|"<ndjson>", filter:{field,op,value?,direction?,timeField?,from?,to?,limit?}}. Ops: gt,gte,lt,lte,eq,ne,contains,crosses_threshold. Free demo at POST /demo; docs at /openapi.json.
Live
Last successful check: 26 Oct 2026, 06:48 UTC.
- answered, last 24 hours
- 100%
- answered, last 30 days
- 100%
4 different wallets paid it in the last 30 days, as the x402 Bazaar reports. Payments
How addrbook checks →Connect
https:x402: an unpaid request gets a 402 with the price and pay-to wallet. addrbook never pays.
Who's behind it
- Listed by
- x402 Bazaarlast seen UTC
- Wallets named
- 0x509e55c4f898b43c856fb0e51048b1b7bfbc9edenamed by x402 Bazaar
- Listed since
Payments
- different wallets paid it, last 30 days
- 4
- paid calls, last 30 days
- 6
- last paid call (UTC)
As the x402 Bazaar reports, from payments Coinbase's facilitator settled. Read . addrbook has not counted these payments itself.
How it asks to be paid
| Network | Price | Paid in | Settled by | Pays to |
|---|---|---|---|---|
| Base | $0.005 | USDC | Per request | 0x509e55c4f898b43c856fb0e51048b1b7bfbc9ede |
From its own 402 answer at UTC. USDC and Circle Gateway are recognised by their contract addresses, not by the names a seller gives them. How payments are read
Checks by endpoint
| Host | Protocol | State | Last checked (UTC) | Last answered (UTC) | 24 hours | 30 days | Tools |
|---|---|---|---|---|---|---|---|
| logfilter. | x402 | Live | 100% | 100% | — |
Also listed as
Other entries that share an endpoint with this one.