Paywary

Leaderboard / agent402.tools / endpoint

POST https://agent402.tools/api/skill/trip-planner

Scores measure reliability and honesty, not output quality.

94Payconfidence: medium
  • Listed only 1 day ago; new listings earn trust over 30 days.
  • Answered all 7 probes in the last 7 days.
Category
Utility by rules, confidence 90%
Latest quote
$0.006 on Base to 0xaBF4…a9D0
Uptime
100% / 7d, 100% / 30d
Delivery
none not yet paid-tested
HTTPS
yes
First listed
2026-11-16
Last probe
2h ago
Next probe
2026-11-18 00:05 UTC

Score components

Uptime, 7 days
100w 15%
Uptime, 30 days
100w 15%
Valid x402 challenge
100w 15%
Price honesty
100w 15%
Delivery after payment
n/aexcluded
Wallet stability
100w 10%
Listing age
6w 5%
HTTPS
100w 5%

Catalog listings

SourceSchemeNetworkAssetListed pricePay toFlowCurrentLast seen
cdpexacteip155:422200xcebA…118C60000xaBF4…a9D0defaultyes25m ago
cdpexacteip155:1430x7547…b60360000xaBF4…a9D0defaultyes25m ago
cdpexactAvalanche0xB97E…8a6E60000xaBF4…a9D0defaultyes25m ago
cdpexacteip155:46630x5fc5…d168100000xaBF4…a9D0defaultyes25m ago
cdpexacteip155:570730x2D27…EAEd60000xaBF4…a9D0defaultyes25m ago
cdpexactSolanaEPjFWd…Dt1v6000J7aN3P…3xwgdefaultyes25m ago
cdpexactstellar:pubnetCCW67T…MI7560000GDNJXC…WWRLdefaultyes25m ago
cdpexactalgorand:wGHE2Pwdvd7S12BL5FaOP20EGYesN73k315667046000C7IIHG…2XIEdefaultyes25m ago
cdpexacteip155:50420x3600…000060000xaBF4…a9D0defaultyes25m ago
payaiexactBase0x8335…2913$0.0060xaBF4…a9D0defaultyes11m ago
cdpexactArbitrum0xaf88…583160000xaBF4…a9D0defaultyes25m ago
cdpexacteip155:13290xe15f…239260000xaBF4…a9D0defaultyes25m ago
payaiexactSolanaEPjFWd…Dt1v6000J7aN3P…3xwgdefaultyes11m ago
cdpexactPolygon0x3c49…335960000xaBF4…a9D0defaultyes25m ago
cdpexacteip155:100x0b2C…Ff8570000xaBF4…a9D0defaultyes25m ago
cdpuptoBase0x8335…2913$0.0060xaBF4…a9D0permit2yes25m ago
cdpexactBase0x8335…2913$0.0060xaBF4…a9D0defaultyes25m ago

Listing changes

WhenEventFromTo
14m agodisappeared——
25m agodescription_changedPlan a multi-stop journey deterministically: geocode each stop, sum the pairwise haversine distances, estimate arrival times by adding driving hours per leg, count business days from today to each arrival, and pull the weather forecast at every US stop. Six tools - three pure-CPU (math + time), three egress (geocoding + weather) - covering the deterministic skeleton of every road-trip / sales-tour / delivery-route planning problem.Plan a multi-stop journey deterministically: geocode each stop, sum the pairwise haversine distances, estimate arrival times by adding driving hours per leg, count business days from today. Data © OpenStreetMap contributors, ODbL (openstreetmap.org/copyright).
25m agodescription_changedPlan a multi-stop journey deterministically: geocode each stop, sum the pairwise haversine distances, estimate arrival times by adding driving hours per leg, count business days from today to each arrival, and pull the weather forecast at every US stop. Six tools - three pure-CPU (math + time), three egress (geocoding + weather) - covering the deterministic skeleton of every road-trip / sales-tour / delivery-route planning problem.Plan a multi-stop journey deterministically: geocode each stop, sum the pairwise haversine distances, estimate arrival times by adding driving hours per leg, count business days from today. Data © OpenStreetMap contributors, ODbL (openstreetmap.org/copyright).
25m agodescription_changedPlan a multi-stop journey deterministically: geocode each stop, sum the pairwise haversine distances, estimate arrival times by adding driving hours per leg, count business days from today to each arrival, and pull the weather forecast at every US stop. Six tools - three pure-CPU (math + time), three egress (geocoding + weather) - covering the deterministic skeleton of every road-trip / sales-tour / delivery-route planning problem.Plan a multi-stop journey deterministically: geocode each stop, sum the pairwise haversine distances, estimate arrival times by adding driving hours per leg, count business days from today. Data © OpenStreetMap contributors, ODbL (openstreetmap.org/copyright).
25m agodescription_changedPlan a multi-stop journey deterministically: geocode each stop, sum the pairwise haversine distances, estimate arrival times by adding driving hours per leg, count business days from today to each arrival, and pull the weather forecast at every US stop. Six tools - three pure-CPU (math + time), three egress (geocoding + weather) - covering the deterministic skeleton of every road-trip / sales-tour / delivery-route planning problem.Plan a multi-stop journey deterministically: geocode each stop, sum the pairwise haversine distances, estimate arrival times by adding driving hours per leg, count business days from today. Data © OpenStreetMap contributors, ODbL (openstreetmap.org/copyright).
25m agodescription_changedPlan a multi-stop journey deterministically: geocode each stop, sum the pairwise haversine distances, estimate arrival times by adding driving hours per leg, count business days from today to each arrival, and pull the weather forecast at every US stop. Six tools - three pure-CPU (math + time), three egress (geocoding + weather) - covering the deterministic skeleton of every road-trip / sales-tour / delivery-route planning problem.Plan a multi-stop journey deterministically: geocode each stop, sum the pairwise haversine distances, estimate arrival times by adding driving hours per leg, count business days from today. Data © OpenStreetMap contributors, ODbL (openstreetmap.org/copyright).
25m agodescription_changedPlan a multi-stop journey deterministically: geocode each stop, sum the pairwise haversine distances, estimate arrival times by adding driving hours per leg, count business days from today to each arrival, and pull the weather forecast at every US stop. Six tools - three pure-CPU (math + time), three egress (geocoding + weather) - covering the deterministic skeleton of every road-trip / sales-tour / delivery-route planning problem.Plan a multi-stop journey deterministically: geocode each stop, sum the pairwise haversine distances, estimate arrival times by adding driving hours per leg, count business days from today. Data © OpenStreetMap contributors, ODbL (openstreetmap.org/copyright).
25m agoprice_changed600010000
25m agodescription_changedPlan a multi-stop journey deterministically: geocode each stop, sum the pairwise haversine distances, estimate arrival times by adding driving hours per leg, count business days from today to each arrival, and pull the weather forecast at every US stop. Six tools - three pure-CPU (math + time), three egress (geocoding + weather) - covering the deterministic skeleton of every road-trip / sales-tour / delivery-route planning problem.Plan a multi-stop journey deterministically: geocode each stop, sum the pairwise haversine distances, estimate arrival times by adding driving hours per leg, count business days from today. Data © OpenStreetMap contributors, ODbL (openstreetmap.org/copyright).
25m agodescription_changedPlan a multi-stop journey deterministically: geocode each stop, sum the pairwise haversine distances, estimate arrival times by adding driving hours per leg, count business days from today to each arrival, and pull the weather forecast at every US stop. Six tools - three pure-CPU (math + time), three egress (geocoding + weather) - covering the deterministic skeleton of every road-trip / sales-tour / delivery-route planning problem.Plan a multi-stop journey deterministically: geocode each stop, sum the pairwise haversine distances, estimate arrival times by adding driving hours per leg, count business days from today. Data © OpenStreetMap contributors, ODbL (openstreetmap.org/copyright).
25m agodescription_changedPlan a multi-stop journey deterministically: geocode each stop, sum the pairwise haversine distances, estimate arrival times by adding driving hours per leg, count business days from today to each arrival, and pull the weather forecast at every US stop. Six tools - three pure-CPU (math + time), three egress (geocoding + weather) - covering the deterministic skeleton of every road-trip / sales-tour / delivery-route planning problem.Plan a multi-stop journey deterministically: geocode each stop, sum the pairwise haversine distances, estimate arrival times by adding driving hours per leg, count business days from today. Data © OpenStreetMap contributors, ODbL (openstreetmap.org/copyright).
25m agodescription_changedPlan a multi-stop journey deterministically: geocode each stop, sum the pairwise haversine distances, estimate arrival times by adding driving hours per leg, count business days from today to each arrival, and pull the weather forecast at every US stop. Six tools - three pure-CPU (math + time), three egress (geocoding + weather) - covering the deterministic skeleton of every road-trip / sales-tour / delivery-route planning problem.Plan a multi-stop journey deterministically: geocode each stop, sum the pairwise haversine distances, estimate arrival times by adding driving hours per leg, count business days from today. Data © OpenStreetMap contributors, ODbL (openstreetmap.org/copyright).
25m agodescription_changedPlan a multi-stop journey deterministically: geocode each stop, sum the pairwise haversine distances, estimate arrival times by adding driving hours per leg, count business days from today to each arrival, and pull the weather forecast at every US stop. Six tools - three pure-CPU (math + time), three egress (geocoding + weather) - covering the deterministic skeleton of every road-trip / sales-tour / delivery-route planning problem.Plan a multi-stop journey deterministically: geocode each stop, sum the pairwise haversine distances, estimate arrival times by adding driving hours per leg, count business days from today. Data © OpenStreetMap contributors, ODbL (openstreetmap.org/copyright).
25m agodescription_changedPlan a multi-stop journey deterministically: geocode each stop, sum the pairwise haversine distances, estimate arrival times by adding driving hours per leg, count business days from today to each arrival, and pull the weather forecast at every US stop. Six tools - three pure-CPU (math + time), three egress (geocoding + weather) - covering the deterministic skeleton of every road-trip / sales-tour / delivery-route planning problem.Plan a multi-stop journey deterministically: geocode each stop, sum the pairwise haversine distances, estimate arrival times by adding driving hours per leg, count business days from today. Data © OpenStreetMap contributors, ODbL (openstreetmap.org/copyright).
25m agodescription_changedPlan a multi-stop journey deterministically: geocode each stop, sum the pairwise haversine distances, estimate arrival times by adding driving hours per leg, count business days from today to each arrival, and pull the weather forecast at every US stop. Six tools - three pure-CPU (math + time), three egress (geocoding + weather) - covering the deterministic skeleton of every road-trip / sales-tour / delivery-route planning problem.Plan a multi-stop journey deterministically: geocode each stop, sum the pairwise haversine distances, estimate arrival times by adding driving hours per leg, count business days from today. Data © OpenStreetMap contributors, ODbL (openstreetmap.org/copyright).

Paid probes

No paid probes yet. Paid probing is off by default and runs weekly per host under a strict spend cap; each paid probe links to its on-chain transaction here.

Delivery checks

Inside each paid probe we ask for something whose correct answer we know, then compare. A pass means the seller delivered what it was paid for; a fail means it charged and returned something wrong; inconclusive means we could not judge (no reference, unknown input shape, or a non-2xx response). Every row carries the request, the response hash and the reference so the verdict can be reproduced. Judged results feed the "Delivery after payment" component (pass 1, error after payment 0.25, fail 0); inconclusive rows are excluded; a fail in the last 14 days caps the verdict at caution. Methodology.

No delivery checks yet. They run inside the weekly paid probe.

Classification history

Every classification is kept; the newest row is the current category. Rules match the listing text; the model is consulted only when the rules are unsure.

WhenCategoryConfidenceMethodVersionEvidence
5m agoUtility90%rulesv1rule utility matched "geocod" in description
22h agoUtility90%rulesv1rule utility matched "geocod" in description

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
2h agofree402409 msv2yes$0.0060xaBF4…a9D0—
8h agofree402474 msv2yes$0.0060xaBF4…a9D0—
15h agofree402101 msv2yes$0.0060xaBF4…a9D0—
21h agofree40240 msv2yes$0.0060xaBF4…a9D0—
27h agofree40240 msv2yes$0.0060xaBF4…a9D0—
33h agofree40235 msv2yes$0.0060xaBF4…a9D0—
40h agofree40234 msv2yes$0.0060xaBF4…a9D0—