Independent MeasurementSeller: purchase results on BaseRead from the database 2026-09-29 08:08 UTC · reused for up to 5 min

vet402Sellers · What to fix firstMethodology

agents.daedalusdevelopmentgroup.com: x402 purchase results on Base, latest attempt 2026-09-25

113 Base listings. Latest result about the seller at each listing: 1 delivered · 0 failed on the seller's side · 4 with no such result among the attempts shown · 108 not tried yet. This counts, for each listing, the newest purchase that delivered or the newest failure on the seller's side. Attempts on vet402's side, not bought, not sorted, or awaiting on-chain verification are skipped.

By the latest attempt at each listing, whatever it was: 1 delivered · 0 failed on the seller's side · 0 on vet402's side · 4 not sorted (vet402 cannot show the failure was not its own) · 108 not tried yet.

Latest attempt: 2026-09-25 00:02 UTC. This page read the ledger at 2026-09-29 08:08 UTC and reuses that read for up to 5 min.

1.Your listings

agents.daedalusdevelopmentgroup.com/v1/whois-lookupPOST
Latest attempt
2026-09-25 00:02 UTC
Result
Payment settled, then the input was rejected
Whose side
not sorted (held)
Decision API now: asking… · the full answer
What we saw: The payment settled on-chain, and then the paid request got 400, 404, 415 or 422. vet402 holds this row (held_reason settled_4xx): its own request may have been the problem, so this page does not count the row as the seller's fault.Last result about the seller: none among the attempts shown. The latest attempt is not sorted; there has been no attempt since.The 402 terms vet402 paid: exact · 0.002 USDC · payTo 0x8afb…0bc6. Input sent: body declared, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.002 USDC · payTo 0x8afb…0bc6 · nonce 0x3619…ebdd · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: This page does not count it as the seller's fault. Checking the input before settling avoids taking a payment for a refused request, and declaring the input with example values that work as written lets vet402 send a valid one.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 400 · tx 0xdb1f8137…cbc9 · held as settled_4xx (the payment settled, then the paid request got a 4xx)In export.csv?days=6: the row with attempted_at 2026-09-25T00:02:12Z and resource_key agents.daedalusdevelopmentgroup.com/v1/whois-lookup.
After a fixNext purchase by vet402: Not before 2026-10-01 00:02 UTC (a listing is bought at most once every 6 days). After that it depends on the daily budget and the order of demand, so this is the earliest date, not a booking.Email me when this result changes Dispute this purchase
agents.daedalusdevelopmentgroup.com/v1/evidence/batchPOST
Latest attempt
2026-09-24 12:01 UTC
Result
Payment settled, then the input was rejected
Whose side
not sorted (held)
Decision API now: asking… · the full answer
What we saw: The payment settled on-chain, and then the paid request got 400, 404, 415 or 422. vet402 holds this row (held_reason settled_4xx): its own request may have been the problem, so this page does not count the row as the seller's fault.Last result about the seller: none among the attempts shown. The latest attempt is not sorted; there has been no attempt since.The 402 terms vet402 paid: exact · 0.01 USDC · payTo 0x8afb…0bc6. Input sent: body declared, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x8afb…0bc6 · nonce 0x58eb…93e3 · validBefore not recorded.Answer to the paid request: HTTP 404 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: This page does not count it as the seller's fault. Checking the input before settling avoids taking a payment for a refused request, and declaring the input with example values that work as written lets vet402 send a valid one.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 404 · tx 0x81c1dabe…c8af · held as settled_4xx (the payment settled, then the paid request got a 4xx)In export.csv?days=6: the row with attempted_at 2026-09-24T12:01:24Z and resource_key agents.daedalusdevelopmentgroup.com/v1/evidence/batch.
After a fixNext purchase by vet402: Not before 2026-09-30 12:01 UTC (a listing is bought at most once every 6 days). After that it depends on the daily budget and the order of demand, so this is the earliest date, not a booking.Email me when this result changes Dispute this purchase
agents.daedalusdevelopmentgroup.com/v1/threat-checkPOST
Latest attempt
2026-09-24 06:01 UTC
Result
Payment settled, then the input was rejected
Whose side
not sorted (held)
Decision API now: · the full answer
What we saw: The payment settled on-chain, and then the paid request got 400, 404, 415 or 422. vet402 holds this row (held_reason settled_4xx): its own request may have been the problem, so this page does not count the row as the seller's fault.Last result about the seller: none among the attempts shown. The latest attempt is not sorted; there has been no attempt since.The 402 terms vet402 paid: exact · 0.005 USDC · payTo 0x8afb…0bc6. Input sent: body declared, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.005 USDC · payTo 0x8afb…0bc6 · nonce 0x1b01…c0d4 · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: This page does not count it as the seller's fault. Checking the input before settling avoids taking a payment for a refused request, and declaring the input with example values that work as written lets vet402 send a valid one.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 400 · tx 0xfa2b338c…3310 · held as settled_4xx (the payment settled, then the paid request got a 4xx)In export.csv?days=7: the row with attempted_at 2026-09-24T06:01:17Z and resource_key agents.daedalusdevelopmentgroup.com/v1/threat-check.
After a fixNext purchase by vet402: Not before 2026-09-30 06:01 UTC (a listing is bought at most once every 6 days). After that it depends on the daily budget and the order of demand, so this is the earliest date, not a booking.Email me when this result changes Dispute this purchase
agents.daedalusdevelopmentgroup.com/v1/embeddingsPOST
Latest attempt
2026-09-24 00:00 UTC
Result
Payment settled, then the input was rejected
Whose side
not sorted (held)
Decision API now: · the full answer
What we saw: The payment settled on-chain, and then the paid request got 400, 404, 415 or 422. vet402 holds this row (held_reason settled_4xx): its own request may have been the problem, so this page does not count the row as the seller's fault.Last result about the seller: none among the attempts shown. The latest attempt is not sorted; there has been no attempt since.The 402 terms vet402 paid: exact · 0.001 USDC · payTo 0x8afb…0bc6. Input sent: body declared, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0x8afb…0bc6 · nonce 0x3363…d199 · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: This page does not count it as the seller's fault. Checking the input before settling avoids taking a payment for a refused request, and declaring the input with example values that work as written lets vet402 send a valid one.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 400 · tx 0x388eaa51…05bc · held as settled_4xx (the payment settled, then the paid request got a 4xx)In export.csv?days=7: the row with attempted_at 2026-09-24T00:00:31Z and resource_key agents.daedalusdevelopmentgroup.com/v1/embeddings.
After a fixNext purchase by vet402: Not before 2026-09-30 00:00 UTC (a listing is bought at most once every 6 days). After that it depends on the daily budget and the order of demand, so this is the earliest date, not a booking.Email me when this result changes Dispute this purchase
agents.daedalusdevelopmentgroup.com/v1/tx-smoke-testPOST
Latest attempt
2026-09-23 06:01 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.01 USDC · payTo 0x8afb…0bc6. Input sent: body declared, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x8afb…0bc6 · nonce 0xa763…406d · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x7605acff…4418In export.csv?days=8: the row with attempted_at 2026-09-23T06:01:31Z and resource_key agents.daedalusdevelopmentgroup.com/v1/tx-smoke-test.
After a fixNext purchase by vet402: The regular sweep can pick this listing again since 2026-09-29 06:01 UTC (a listing is bought at most once every 6 days). When it does depends on the daily budget and the order of demand, so there is no booked date.Email me when this result changes Dispute this purchase
agents.daedalusdevelopmentgroup.com/v1/agent-checkout-conformance-auditPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/agent-discovery-packPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/agent-marketplace-listing-packPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/agent-payment-readiness-auditPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/agent-readiness-scorecardPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/agent-registryPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/agent-service-distribution-packPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/agent-supply-chain-baselinePOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/agent-tool-schema-repairPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/ai-agent-buyer-service-bundlePOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/ai-agent-skill-portPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/artifact-receipt-console-packPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/base64-codecPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/browser-proofPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/buyer-agent-smoke-probePOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/code-executionPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/code-to-endpointPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/commodity-pricePOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/contract-abiPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/credential-escrow-proxyPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/diff-textPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/dns-lookupPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/email-sendPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/ethereum/rpcPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/evidence/anchorPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/fetch-as-markdownPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/fx-ratePOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/git-repo-analyzePOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/hash-computePOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/hermes-skill-workflow-devPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/http-headersPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/image-generationPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/inbox/lookupPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/inbox/messages/listPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/inbox/registerPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/inbox/sendPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/inbox/settingsPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/ip-geolocationPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/json-validatePOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/landing-page-conversion-diffPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/language-detectPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/lead-packPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/link-extractPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/llm-judgePOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
agents.daedalusdevelopmentgroup.com/v1/local-business-demo-packPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes

2.How to read this

Each listing shows its latest attempt on Base and up to four earlier ones. A row where vet402 signed a payment and sent the paid request is an L1 result: “Recorded (L1 paid purchase)” when the payment settled on-chain, and “signed, not settled on-chain” when it did not. A row where vet402 did not sign is marked “not bought” and is not an L1 result. The listing's record page also shows the L0 state (“Published state”), which checks that an unpaid request gets a valid 402, so a listing can pass L0 and still fail here. Whose side puts a failure on the seller's side when the row shows vet402 was not at fault: it signed on the listing's terms, its wallet held the price, it sent the declared input, and the seller answered explicitly or had its declared time. Even then, one such failure is “not sorted: one failure so far”: a failure goes on the seller's side only when the same listing has one on two different days (UTC), and those rows are marked “under re-check” while we re-check them. A row that cannot show all of that is “not sorted”, and so is a held row (held_reason in the export), a failure where no payment was taken (“no charge”), and a payment that settled before the seller refused an input vet402 had not sent. “Signed payment” and “Answer to the paid request” show what the row recorded, and nothing else: the answer's body and header values are not published. The maxTimeoutSeconds on a row is the listing's value today; a declared price or address on a not-bought row is the value recorded at the time of the attempt. The transaction link opens the settlement on Basescan. “Decision API now” is what the decision API (GET /api/v1/resources/{id}/decision?role=payer, no key) answers for the listing when you open this page; your browser asks it for the first 2 listings, and for the others when you ask. It is cautious for the payer: it leaves out the attempts that show vet402's fault, are held, or took no payment, and counts the rest, so it can say WARN or BLOCK for a listing whose failures this page leaves not sorted. The codes that decided the answer come first, each with one sentence on what it means for that listing (reason codes). “After a fix” gives the earliest date vet402's regular sweep can buy the listing again, where the rules let it be worked out, and the links to be told of a change or to dispute a row. Listings removed from the Bazaar, and listings whose catalog network is not Base, are not on this page. The fix-first page groups the same results across sellers (methodology).

3.Think a row is wrong?

Use “Dispute this purchase” on the row: it opens Dispute this record on the listing's record page with the purchase time filled in. Say what you saw instead. The row is not deleted on dispute; a correction is published with the same weight.