Paywary

Leaderboard / agent402.tools / endpoint

POST https://agent402.tools/api/skill/schema-evolution

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
Data transform by rules, confidence 90%
Latest quote
$0.008 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
3h ago
Next probe
2026-11-17 23:26 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:50420x3600…000080000xaBF4…a9D0defaultyes55m ago
cdpexacteip155:13290xe15f…239280000xaBF4…a9D0defaultyes55m ago
cdpexacteip155:422200xcebA…118C80000xaBF4…a9D0defaultyes55m ago
cdpexacteip155:570730x2D27…EAEd80000xaBF4…a9D0defaultyes55m ago
cdpexactalgorand:wGHE2Pwdvd7S12BL5FaOP20EGYesN73k315667048000C7IIHG…2XIEdefaultyes55m ago
cdpexactBase0x8335…2913$0.0080xaBF4…a9D0defaultyes55m ago
cdpexacteip155:100x0b2C…Ff8590000xaBF4…a9D0defaultyes55m ago
cdpexactPolygon0x3c49…335980000xaBF4…a9D0defaultyes55m ago
cdpexactArbitrum0xaf88…583180000xaBF4…a9D0defaultyes55m ago
cdpexacteip155:1430x7547…b60380000xaBF4…a9D0defaultyes55m ago
cdpexactAvalanche0xB97E…8a6E80000xaBF4…a9D0defaultyes55m ago
cdpuptoBase0x8335…2913$0.0080xaBF4…a9D0permit2yes55m ago
cdpexactSolanaEPjFWd…Dt1v8000J7aN3P…3xwgdefaultyes55m ago
cdpexactstellar:pubnetCCW67T…MI7580000GDNJXC…WWRLdefaultyes55m ago
payaiexactSolanaEPjFWd…Dt1v8000J7aN3P…3xwgdefaultyes40m ago
cdpexacteip155:46630x5fc5…d168100000xaBF4…a9D0defaultyes55m ago
payaiexactBase0x8335…2913$0.0080xaBF4…a9D0defaultyes40m ago

Listing changes

WhenEventFromTo
43m agodisappeared——
55m agodescription_changedThe 'did this API contract change in a way that breaks our integration?' workflow. Diff two OpenAPI snapshots structurally, lint the new one for agent-readiness regressions, extract the endpoint surface for inventory comparison, validate a known-good payload against the new contract, and summarize security-relevant changes. Six tools, one go/no-go answer on whether the upstream API broke us.Schema evolution check skill: one call compares two OpenAPI snapshots and returns the structural diff, the new spec's lint score, its endpoint list, the first endpoint's required params, an empty request body checked against that endpoint, and a security summary, so an agent can judge whether the change breaks an integration.
55m agodescription_changedThe 'did this API contract change in a way that breaks our integration?' workflow. Diff two OpenAPI snapshots structurally, lint the new one for agent-readiness regressions, extract the endpoint surface for inventory comparison, validate a known-good payload against the new contract, and summarize security-relevant changes. Six tools, one go/no-go answer on whether the upstream API broke us.Schema evolution check skill: one call compares two OpenAPI snapshots and returns the structural diff, the new spec's lint score, its endpoint list, the first endpoint's required params, an empty request body checked against that endpoint, and a security summary, so an agent can judge whether the change breaks an integration.
55m agodescription_changedThe 'did this API contract change in a way that breaks our integration?' workflow. Diff two OpenAPI snapshots structurally, lint the new one for agent-readiness regressions, extract the endpoint surface for inventory comparison, validate a known-good payload against the new contract, and summarize security-relevant changes. Six tools, one go/no-go answer on whether the upstream API broke us.Schema evolution check skill: one call compares two OpenAPI snapshots and returns the structural diff, the new spec's lint score, its endpoint list, the first endpoint's required params, an empty request body checked against that endpoint, and a security summary, so an agent can judge whether the change breaks an integration.
55m agodescription_changedThe 'did this API contract change in a way that breaks our integration?' workflow. Diff two OpenAPI snapshots structurally, lint the new one for agent-readiness regressions, extract the endpoint surface for inventory comparison, validate a known-good payload against the new contract, and summarize security-relevant changes. Six tools, one go/no-go answer on whether the upstream API broke us.Schema evolution check skill: one call compares two OpenAPI snapshots and returns the structural diff, the new spec's lint score, its endpoint list, the first endpoint's required params, an empty request body checked against that endpoint, and a security summary, so an agent can judge whether the change breaks an integration.
55m agodescription_changedThe 'did this API contract change in a way that breaks our integration?' workflow. Diff two OpenAPI snapshots structurally, lint the new one for agent-readiness regressions, extract the endpoint surface for inventory comparison, validate a known-good payload against the new contract, and summarize security-relevant changes. Six tools, one go/no-go answer on whether the upstream API broke us.Schema evolution check skill: one call compares two OpenAPI snapshots and returns the structural diff, the new spec's lint score, its endpoint list, the first endpoint's required params, an empty request body checked against that endpoint, and a security summary, so an agent can judge whether the change breaks an integration.
55m agodescription_changedThe 'did this API contract change in a way that breaks our integration?' workflow. Diff two OpenAPI snapshots structurally, lint the new one for agent-readiness regressions, extract the endpoint surface for inventory comparison, validate a known-good payload against the new contract, and summarize security-relevant changes. Six tools, one go/no-go answer on whether the upstream API broke us.Schema evolution check skill: one call compares two OpenAPI snapshots and returns the structural diff, the new spec's lint score, its endpoint list, the first endpoint's required params, an empty request body checked against that endpoint, and a security summary, so an agent can judge whether the change breaks an integration.
55m agoprice_changed800010000
55m agodescription_changedThe 'did this API contract change in a way that breaks our integration?' workflow. Diff two OpenAPI snapshots structurally, lint the new one for agent-readiness regressions, extract the endpoint surface for inventory comparison, validate a known-good payload against the new contract, and summarize security-relevant changes. Six tools, one go/no-go answer on whether the upstream API broke us.Schema evolution check skill: one call compares two OpenAPI snapshots and returns the structural diff, the new spec's lint score, its endpoint list, the first endpoint's required params, an empty request body checked against that endpoint, and a security summary, so an agent can judge whether the change breaks an integration.
55m agodescription_changedThe 'did this API contract change in a way that breaks our integration?' workflow. Diff two OpenAPI snapshots structurally, lint the new one for agent-readiness regressions, extract the endpoint surface for inventory comparison, validate a known-good payload against the new contract, and summarize security-relevant changes. Six tools, one go/no-go answer on whether the upstream API broke us.Schema evolution check skill: one call compares two OpenAPI snapshots and returns the structural diff, the new spec's lint score, its endpoint list, the first endpoint's required params, an empty request body checked against that endpoint, and a security summary, so an agent can judge whether the change breaks an integration.
55m agodescription_changedThe 'did this API contract change in a way that breaks our integration?' workflow. Diff two OpenAPI snapshots structurally, lint the new one for agent-readiness regressions, extract the endpoint surface for inventory comparison, validate a known-good payload against the new contract, and summarize security-relevant changes. Six tools, one go/no-go answer on whether the upstream API broke us.Schema evolution check skill: one call compares two OpenAPI snapshots and returns the structural diff, the new spec's lint score, its endpoint list, the first endpoint's required params, an empty request body checked against that endpoint, and a security summary, so an agent can judge whether the change breaks an integration.
55m agodescription_changedThe 'did this API contract change in a way that breaks our integration?' workflow. Diff two OpenAPI snapshots structurally, lint the new one for agent-readiness regressions, extract the endpoint surface for inventory comparison, validate a known-good payload against the new contract, and summarize security-relevant changes. Six tools, one go/no-go answer on whether the upstream API broke us.Schema evolution check skill: one call compares two OpenAPI snapshots and returns the structural diff, the new spec's lint score, its endpoint list, the first endpoint's required params, an empty request body checked against that endpoint, and a security summary, so an agent can judge whether the change breaks an integration.
55m agodescription_changedThe 'did this API contract change in a way that breaks our integration?' workflow. Diff two OpenAPI snapshots structurally, lint the new one for agent-readiness regressions, extract the endpoint surface for inventory comparison, validate a known-good payload against the new contract, and summarize security-relevant changes. Six tools, one go/no-go answer on whether the upstream API broke us.Schema evolution check skill: one call compares two OpenAPI snapshots and returns the structural diff, the new spec's lint score, its endpoint list, the first endpoint's required params, an empty request body checked against that endpoint, and a security summary, so an agent can judge whether the change breaks an integration.
55m agodescription_changedThe 'did this API contract change in a way that breaks our integration?' workflow. Diff two OpenAPI snapshots structurally, lint the new one for agent-readiness regressions, extract the endpoint surface for inventory comparison, validate a known-good payload against the new contract, and summarize security-relevant changes. Six tools, one go/no-go answer on whether the upstream API broke us.Schema evolution check skill: one call compares two OpenAPI snapshots and returns the structural diff, the new spec's lint score, its endpoint list, the first endpoint's required params, an empty request body checked against that endpoint, and a security summary, so an agent can judge whether the change breaks an integration.
55m agodescription_changedThe 'did this API contract change in a way that breaks our integration?' workflow. Diff two OpenAPI snapshots structurally, lint the new one for agent-readiness regressions, extract the endpoint surface for inventory comparison, validate a known-good payload against the new contract, and summarize security-relevant changes. Six tools, one go/no-go answer on whether the upstream API broke us.Schema evolution check skill: one call compares two OpenAPI snapshots and returns the structural diff, the new spec's lint score, its endpoint list, the first endpoint's required params, an empty request body checked against that endpoint, and a security summary, so an agent can judge whether the change breaks an integration.

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
34m agoWeb audit90%rulesv1rule web_audit matched "lint" in description
6h agoData transform50%llmv1claude-haiku-5-5: The endpoint diffs two OpenAPI specs structurally, extracts endpoint surfaces and validates payloads against a contract, which is deterministic spec tooling. It also includes linting and a security summary, so it is not a pure transform. data_transform is the closest fit, though the description is framed as a multi-tool workflow and could fall under other categories.
23h agoInference60%rulesv1rule inference matched "summarize" in description

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
3h agofree402423 msv2yes$0.0080xaBF4…a9D0—
9h agofree402392 msv2yes$0.0080xaBF4…a9D0—
15h agofree402135 msv2yes$0.0080xaBF4…a9D0—
22h agofree40277 msv2yes$0.0080xaBF4…a9D0—
28h agofree402197 msv2yes$0.0080xaBF4…a9D0—
34h agofree40231 msv2yes$0.0080xaBF4…a9D0—
40h agofree40224 msv2yes$0.0080xaBF4…a9D0—