Independent MeasurementSeller: purchase results on BaseRead from the database 2026-09-28 05:03 UTC · reused for up to 5 min
x402.orthogonal.com
130 Base listings. By the latest purchase of each: 12 delivered · 21 failed on the seller's side · 16 on vet402's side · 81 not yet bought. Latest purchase: 2026-09-28 00:02 UTC.
1.Your listings
| Listing | Latest purchase | Result | Whose side |
|---|---|---|---|
| x402.orthogonal.com/openfunnel/api/v1/enrich/deep-enrichPOST | 2026-09-28 00:02 UTC | Took the payment, then refused the input | seller's side |
What we saw: The payment settled on-chain, and then the paid request got 400, 404, 415 or 422: the route took the payment before it checked the input, so the buyer paid for a refused request. When the seller declared a body, or a required query, that vet402 was not yet sending, the row is on vet402's side instead.What to fix: Check the input before you settle, so an invalid request is refused without taking the payment; and declare the input in the listing with example values that work as written. (a server change)Recorded: settled · HTTP 422 · tx 0x2195430e…27ac · held as settled_4xxIn export.csv?days=2: the row with attempted_at 2026-09-28T00:02:25Z and resource_key x402.orthogonal.com/openfunnel/api/v1/enrich/deep-enrich.Earlier: 2026-09-13 18:00 UTC vet402 did not send the declared request body (vet402's side) | |||
| x402.orthogonal.com/bytemine/crawl/continuePOST | 2026-09-27 06:01 UTC | Took the payment, then refused the input | seller's side |
What we saw: The payment settled on-chain, and then the paid request got 400, 404, 415 or 422: the route took the payment before it checked the input, so the buyer paid for a refused request. When the seller declared a body, or a required query, that vet402 was not yet sending, the row is on vet402's side instead.What to fix: Check the input before you settle, so an invalid request is refused without taking the payment; and declare the input in the listing with example values that work as written. (a server change)Recorded: settled · HTTP 404 · tx 0x8663fca4…50d7 · held as settled_4xxIn export.csv?days=2: the row with attempted_at 2026-09-27T06:01:10Z and resource_key x402.orthogonal.com/bytemine/crawl/continue. | |||
| x402.orthogonal.com/context-dev/web/scrape/markdownGET | 2026-09-27 06:01 UTC | The paid request was refused as invalid | seller's side |
What we saw: vet402 signed the payment and the paid request got 400, 404, 415 or 422; the payment did not settle. Since 2026-09-16 23:25 UTC vet402 sends the request body the seller's 402 declares (an empty JSON body when it declares none), and since 2026-09-27 23:27 UTC it adds the query parameters the seller's 402 declares on Base.What to fix: Declare the input in the listing (body or query) with example values that work as written. (a listing or config change)Before 2026-09-27 23:27 UTC, vet402 did not add query parameters to paid requests on Base; this listing declares optional ones.Recorded: settle_failed · HTTP 400 · no tx · held as unsettled_4xxIn export.csv?days=2: the row with attempted_at 2026-09-27T06:01:09Z and resource_key x402.orthogonal.com/context-dev/web/scrape/markdown. | |||
| x402.orthogonal.com/serper/searchPOST | 2026-09-27 06:01 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0xda15fd61…33beIn export.csv?days=2: the row with attempted_at 2026-09-27T06:01:03Z and resource_key x402.orthogonal.com/serper/search. | |||
| x402.orthogonal.com/exchange-rates/v1/convertGET | 2026-09-27 06:00 UTC | The paid request was refused as invalid | seller's side |
What we saw: vet402 signed the payment and the paid request got 400, 404, 415 or 422; the payment did not settle. Since 2026-09-16 23:25 UTC vet402 sends the request body the seller's 402 declares (an empty JSON body when it declares none), and since 2026-09-27 23:27 UTC it adds the query parameters the seller's 402 declares on Base.What to fix: Declare the input in the listing (body or query) with example values that work as written. (a listing or config change)Before 2026-09-27 23:27 UTC, vet402 did not add query parameters to paid requests on Base; this listing declares optional ones.Recorded: settle_failed · HTTP 400 · no tx · held as unsettled_4xxIn export.csv?days=2: the row with attempted_at 2026-09-27T06:00:53Z and resource_key x402.orthogonal.com/exchange-rates/v1/convert. | |||
| x402.orthogonal.com/icypeas/api/find-peoplePOST | 2026-09-26 18:01 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x40728301…bf30In export.csv?days=3: the row with attempted_at 2026-09-26T18:01:11Z and resource_key x402.orthogonal.com/icypeas/api/find-people.Earlier: 2026-09-20 12:07 UTC delivered | |||
| x402.orthogonal.com/apollo/api/v1/mixed_people/api_searchPOST | 2026-09-26 18:00 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0xa03e0d4b…1a98In export.csv?days=3: the row with attempted_at 2026-09-26T18:00:43Z and resource_key x402.orthogonal.com/apollo/api/v1/mixed_people/api_search. | |||
| x402.orthogonal.com/fiber/v1/validate-phone/singlePOST | 2026-09-26 12:01 UTC | Took the payment, then refused the input | seller's side |
What we saw: The payment settled on-chain, and then the paid request got 400, 404, 415 or 422: the route took the payment before it checked the input, so the buyer paid for a refused request. When the seller declared a body, or a required query, that vet402 was not yet sending, the row is on vet402's side instead.What to fix: Check the input before you settle, so an invalid request is refused without taking the payment; and declare the input in the listing with example values that work as written. (a server change)Recorded: settled · HTTP 400 · tx 0x120a39dc…790d · held as settled_4xxIn export.csv?days=3: the row with attempted_at 2026-09-26T12:01:04Z and resource_key x402.orthogonal.com/fiber/v1/validate-phone/single.Earlier: 2026-09-13 18:01 UTC vet402 did not send the declared request body (vet402's side) · 2026-09-04 12:09 UTC vet402 did not send the declared request body (vet402's side) | |||
| x402.orthogonal.com/leadsforge/enrichment/phonePOST | 2026-09-26 06:02 UTC | Took the payment, then refused the input | seller's side |
What we saw: The payment settled on-chain, and then the paid request got 400, 404, 415 or 422: the route took the payment before it checked the input, so the buyer paid for a refused request. When the seller declared a body, or a required query, that vet402 was not yet sending, the row is on vet402's side instead.What to fix: Check the input before you settle, so an invalid request is refused without taking the payment; and declare the input in the listing with example values that work as written. (a server change)Recorded: settled · HTTP 400 · tx 0x7657816f…a2a0 · held as settled_4xxIn export.csv?days=3: the row with attempted_at 2026-09-26T06:02:24Z and resource_key x402.orthogonal.com/leadsforge/enrichment/phone.Earlier: 2026-09-14 12:07 UTC vet402's wallet was out of USDC (vet402's side) · 2026-09-08 07:02 UTC vet402 did not send the declared request body (vet402's side) | |||
| x402.orthogonal.com/leadsforge/enrichment/emailPOST | 2026-09-26 06:02 UTC | Took the payment, then refused the input | seller's side |
What we saw: The payment settled on-chain, and then the paid request got 400, 404, 415 or 422: the route took the payment before it checked the input, so the buyer paid for a refused request. When the seller declared a body, or a required query, that vet402 was not yet sending, the row is on vet402's side instead.What to fix: Check the input before you settle, so an invalid request is refused without taking the payment; and declare the input in the listing with example values that work as written. (a server change)Recorded: settled · HTTP 400 · tx 0x93531f17…6fa2 · held as settled_4xxIn export.csv?days=3: the row with attempted_at 2026-09-26T06:02:11Z and resource_key x402.orthogonal.com/leadsforge/enrichment/email.Earlier: 2026-09-17 18:01 UTC Took the payment, then refused the input (seller's side) · 2026-09-10 07:00 UTC vet402 did not send the declared request body (vet402's side) | |||
| x402.orthogonal.com/apollo/api/v1/mixed_companies/searchPOST | 2026-09-25 18:02 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x6a2410f4…c67cIn export.csv?days=4: the row with attempted_at 2026-09-25T18:02:16Z and resource_key x402.orthogonal.com/apollo/api/v1/mixed_companies/search.Earlier: 2026-09-15 23:49 UTC delivered · 2026-09-09 19:00 UTC delivered | |||
| x402.orthogonal.com/predictleads/v3/discover/portfolio_companies/connectionsGET | 2026-09-25 00:01 UTC | No answer to the paid request | seller's side |
What we saw: vet402 signed the payment and the paid request got no HTTP answer in time (timeout, 408 or a closed connection).What to fix: Make the paid route answer within a few seconds; look for slow upstream calls or cold starts. (a server change)Recorded: settled · HTTP — · tx 0x8f8cb5a4…10bdIn export.csv?days=5: the row with attempted_at 2026-09-25T00:01:12Z and resource_key x402.orthogonal.com/predictleads/v3/discover/portfolio_companies/connections. | |||
| x402.orthogonal.com/findymail/api/technologies/searchGET | 2026-09-23 00:01 UTC | The paid request was refused as invalid | seller's side |
What we saw: vet402 signed the payment and the paid request got 400, 404, 415 or 422; the payment did not settle. Since 2026-09-16 23:25 UTC vet402 sends the request body the seller's 402 declares (an empty JSON body when it declares none), and since 2026-09-27 23:27 UTC it adds the query parameters the seller's 402 declares on Base.What to fix: Declare the input in the listing (body or query) with example values that work as written. (a listing or config change)Before 2026-09-27 23:27 UTC, vet402 did not add query parameters to paid requests on Base; this listing declares optional ones.Recorded: settle_failed · HTTP 400 · no tx · held as unsettled_4xxIn export.csv?days=7: the row with attempted_at 2026-09-23T00:01:00Z and resource_key x402.orthogonal.com/findymail/api/technologies/search. | |||
| x402.orthogonal.com/findymail/api/search/business-profilePOST | 2026-09-23 00:00 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0xe76f0b17…aa6bIn export.csv?days=7: the row with attempted_at 2026-09-23T00:00:56Z and resource_key x402.orthogonal.com/findymail/api/search/business-profile. | |||
| x402.orthogonal.com/aviato/company/foundersGET | 2026-09-22 12:08 UTC | The paid request was refused as invalid | seller's side |
What we saw: vet402 signed the payment and the paid request got 400, 404, 415 or 422; the payment did not settle. Since 2026-09-16 23:25 UTC vet402 sends the request body the seller's 402 declares (an empty JSON body when it declares none), and since 2026-09-27 23:27 UTC it adds the query parameters the seller's 402 declares on Base.What to fix: Declare the input in the listing (body or query) with example values that work as written. (a listing or config change)Before 2026-09-27 23:27 UTC, vet402 did not add query parameters to paid requests on Base; this listing declares optional ones.Recorded: settle_failed · HTTP 400 · no tx · held as unsettled_4xxIn export.csv?days=7: the row with attempted_at 2026-09-22T12:08:40Z and resource_key x402.orthogonal.com/aviato/company/founders. | |||
| x402.orthogonal.com/scrapecreators/v1/twitter/tweetGET | 2026-09-21 00:01 UTC | The paid request was refused as invalid | seller's side |
What we saw: vet402 signed the payment and the paid request got 400, 404, 415 or 422; the payment did not settle. Since 2026-09-16 23:25 UTC vet402 sends the request body the seller's 402 declares (an empty JSON body when it declares none), and since 2026-09-27 23:27 UTC it adds the query parameters the seller's 402 declares on Base.What to fix: Declare the input in the listing (body or query) with example values that work as written. (a listing or config change)Before 2026-09-27 23:27 UTC, vet402 did not add query parameters to paid requests on Base; this listing declares optional ones.Recorded: settle_failed · HTTP 400 · no tx · held as unsettled_4xxIn export.csv?days=9: the row with attempted_at 2026-09-21T00:01:59Z and resource_key x402.orthogonal.com/scrapecreators/v1/twitter/tweet. | |||
| x402.orthogonal.com/fiber/v1/twitter/searchPOST | 2026-09-18 06:01 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x65c44fb2…73a3In export.csv?days=11: the row with attempted_at 2026-09-18T06:01:13Z and resource_key x402.orthogonal.com/fiber/v1/twitter/search. | |||
| x402.orthogonal.com/apollo/api/v1/people/matchPOST | 2026-09-17 15:23 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0xc36ddb71…8f03In export.csv?days=12: the row with attempted_at 2026-09-17T15:23:14Z and resource_key x402.orthogonal.com/apollo/api/v1/people/match.Earlier: 2026-09-11 01:02 UTC delivered · 2026-09-04 12:08 UTC delivered | |||
| x402.orthogonal.com/leadsforge/lookalikes/filters/departmentsGET | 2026-09-17 00:00 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0xc9c47992…b896In export.csv?days=13: the row with attempted_at 2026-09-17T00:00:58Z and resource_key x402.orthogonal.com/leadsforge/lookalikes/filters/departments. | |||
| x402.orthogonal.com/baseten/v1/chat/completionsPOST | 2026-09-15 23:50 UTC | vet402 did not send the declared request body | vet402's side |
What we saw: Before 2026-09-16 23:25 UTC, vet402 sent an empty JSON body on paid POST requests, even when the listing declares a body. The seller refused it with 400 or 422, before or after the payment settled.What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded: settle_failed · HTTP 400 · no tx · held as unsettled_4xxIn export.csv?days=14: the row with attempted_at 2026-09-15T23:50:44Z and resource_key x402.orthogonal.com/baseten/v1/chat/completions.Earlier: 2026-09-03 12:09 UTC vet402 did not send the declared request body (vet402's side) | |||
| x402.orthogonal.com/company-enrich/companiesGET | 2026-09-15 06:00 UTC | The paid request was refused as invalid | seller's side |
What we saw: vet402 signed the payment and the paid request got 400, 404, 415 or 422; the payment did not settle. Since 2026-09-16 23:25 UTC vet402 sends the request body the seller's 402 declares (an empty JSON body when it declares none), and since 2026-09-27 23:27 UTC it adds the query parameters the seller's 402 declares on Base.What to fix: Declare the input in the listing (body or query) with example values that work as written. (a listing or config change)Before 2026-09-27 23:27 UTC, vet402 did not add query parameters to paid requests on Base; this listing declares optional ones.Recorded: settle_failed · HTTP 400 · no tx · held as unsettled_4xxIn export.csv?days=14: the row with attempted_at 2026-09-15T06:00:10Z and resource_key x402.orthogonal.com/company-enrich/companies. | |||
| x402.orthogonal.com/findymail/api/search/reverse-emailPOST | 2026-09-14 12:07 UTC | vet402 did not send the declared request body | vet402's side |
What we saw: Before 2026-09-16 23:25 UTC, vet402 sent an empty JSON body on paid POST requests, even when the listing declares a body. The seller refused it with 400 or 422, before or after the payment settled.What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded: settle_failed · HTTP 400 · no tx · held as unsettled_4xxIn export.csv?days=15: the row with attempted_at 2026-09-14T12:07:49Z and resource_key x402.orthogonal.com/findymail/api/search/reverse-email.Earlier: 2026-09-08 07:02 UTC vet402 did not send the declared request body (vet402's side) | |||
| x402.orthogonal.com/findymail/api/search/companyPOST | 2026-09-14 00:00 UTC | vet402's wallet was out of USDC | vet402's side |
What we saw: Between 2026-09-13 00:00 and 2026-09-15 23:49 UTC, vet402's Base payer wallet had run out of USDC. The seller refused a payment that had nothing behind it (402 or 5xx).What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded: settle_failed · HTTP 402 · no tx · held as payer_unfundedIn export.csv?days=16: the row with attempted_at 2026-09-14T00:00:06Z and resource_key x402.orthogonal.com/findymail/api/search/company. | |||
| x402.orthogonal.com/precip/api/v1/last-48GET | 2026-09-13 06:00 UTC | The paid request was refused as invalid | seller's side |
What we saw: vet402 signed the payment and the paid request got 400, 404, 415 or 422; the payment did not settle. Since 2026-09-16 23:25 UTC vet402 sends the request body the seller's 402 declares (an empty JSON body when it declares none), and since 2026-09-27 23:27 UTC it adds the query parameters the seller's 402 declares on Base.What to fix: Declare the input in the listing (body or query) with example values that work as written. (a listing or config change)Before 2026-09-27 23:27 UTC, vet402 did not add query parameters to paid requests on Base; this listing declares optional ones.Recorded: settle_failed · HTTP 400 · no tx · held as unsettled_4xxIn export.csv?days=16: the row with attempted_at 2026-09-13T06:00:39Z and resource_key x402.orthogonal.com/precip/api/v1/last-48. | |||
| x402.orthogonal.com/agentmail/v0/inboxes/x402test1786260932@agentmail.to/messages/sendPOST | 2026-09-12 12:07 UTC | vet402 did not send the declared request body | vet402's side |
What we saw: Before 2026-09-16 23:25 UTC, vet402 sent an empty JSON body on paid POST requests, even when the listing declares a body. The seller refused it with 400 or 422, before or after the payment settled.What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded: settled · HTTP 400 · tx 0x99537321…9aca · held as settled_4xxIn export.csv?days=17: the row with attempted_at 2026-09-12T12:07:42Z and resource_key x402.orthogonal.com/agentmail/v0/inboxes/x402test1786260932@agentmail.to/messages/send. | |||
| x402.orthogonal.com/icypeas/api/reverse-email-lookupPOST | 2026-09-11 01:00 UTC | vet402 did not send the declared request body | vet402's side |
What we saw: Before 2026-09-16 23:25 UTC, vet402 sent an empty JSON body on paid POST requests, even when the listing declares a body. The seller refused it with 400 or 422, before or after the payment settled.What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded: settle_failed · HTTP 400 · no tx · held as unsettled_4xxIn export.csv?days=19: the row with attempted_at 2026-09-11T01:00:28Z and resource_key x402.orthogonal.com/icypeas/api/reverse-email-lookup. | |||
| x402.orthogonal.com/rocketreach/person/lookupGET | 2026-09-10 12:07 UTC | Took the payment, then refused the input | seller's side |
What we saw: The payment settled on-chain, and then the paid request got 400, 404, 415 or 422: the route took the payment before it checked the input, so the buyer paid for a refused request. When the seller declared a body, or a required query, that vet402 was not yet sending, the row is on vet402's side instead.What to fix: Check the input before you settle, so an invalid request is refused without taking the payment; and declare the input in the listing with example values that work as written. (a server change)Before 2026-09-27 23:27 UTC, vet402 did not add query parameters to paid requests on Base; this listing declares optional ones.Recorded: settled · HTTP 400 · tx 0x2b5fa4df…cab0 · held as settled_4xxIn export.csv?days=19: the row with attempted_at 2026-09-10T12:07:42Z and resource_key x402.orthogonal.com/rocketreach/person/lookup. | |||
| x402.orthogonal.com/tomba/v1/email-verifierGET | 2026-09-09 19:01 UTC | The paid request was refused as invalid | seller's side |
What we saw: vet402 signed the payment and the paid request got 400, 404, 415 or 422; the payment did not settle. Since 2026-09-16 23:25 UTC vet402 sends the request body the seller's 402 declares (an empty JSON body when it declares none), and since 2026-09-27 23:27 UTC it adds the query parameters the seller's 402 declares on Base.What to fix: Declare the input in the listing (body or query) with example values that work as written. (a listing or config change)Before 2026-09-27 23:27 UTC, vet402 did not add query parameters to paid requests on Base; this listing declares optional ones.Recorded: settle_failed · HTTP 400 · no tx · held as unsettled_4xxIn export.csv?days=20: the row with attempted_at 2026-09-09T19:01:15Z and resource_key x402.orthogonal.com/tomba/v1/email-verifier. | |||
| x402.orthogonal.com/leadsforge/company-followers/searchPOST | 2026-09-09 07:01 UTC | vet402 did not send the declared request body | vet402's side |
What we saw: Before 2026-09-16 23:25 UTC, vet402 sent an empty JSON body on paid POST requests, even when the listing declares a body. The seller refused it with 400 or 422, before or after the payment settled.What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded: settle_failed · HTTP 400 · no tx · held as unsettled_4xxIn export.csv?days=20: the row with attempted_at 2026-09-09T07:01:37Z and resource_key x402.orthogonal.com/leadsforge/company-followers/search. | |||
| x402.orthogonal.com/icypeas/api/url-search/companyPOST | 2026-09-09 07:00 UTC | vet402 did not send the declared request body | vet402's side |
What we saw: Before 2026-09-16 23:25 UTC, vet402 sent an empty JSON body on paid POST requests, even when the listing declares a body. The seller refused it with 400 or 422, before or after the payment settled.What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded: settle_failed · HTTP 400 · no tx · held as unsettled_4xxIn export.csv?days=20: the row with attempted_at 2026-09-09T07:00:31Z and resource_key x402.orthogonal.com/icypeas/api/url-search/company. | |||
| x402.orthogonal.com/icypeas/api/reverse-email-lookupsPOST | 2026-09-08 12:09 UTC | vet402 did not send the declared request body | vet402's side |
What we saw: Before 2026-09-16 23:25 UTC, vet402 sent an empty JSON body on paid POST requests, even when the listing declares a body. The seller refused it with 400 or 422, before or after the payment settled.What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded: settle_failed · HTTP 400 · no tx · held as unsettled_4xxIn export.csv?days=21: the row with attempted_at 2026-09-08T12:09:35Z and resource_key x402.orthogonal.com/icypeas/api/reverse-email-lookups. | |||
| x402.orthogonal.com/icypeas/api/scrape/profileGET | 2026-09-08 12:09 UTC | The paid request was refused as invalid | seller's side |
What we saw: vet402 signed the payment and the paid request got 400, 404, 415 or 422; the payment did not settle. Since 2026-09-16 23:25 UTC vet402 sends the request body the seller's 402 declares (an empty JSON body when it declares none), and since 2026-09-27 23:27 UTC it adds the query parameters the seller's 402 declares on Base.What to fix: Declare the input in the listing (body or query) with example values that work as written. (a listing or config change)Before 2026-09-27 23:27 UTC, vet402 did not add query parameters to paid requests on Base; this listing declares optional ones.Recorded: settle_failed · HTTP 400 · no tx · held as unsettled_4xxIn export.csv?days=21: the row with attempted_at 2026-09-08T12:09:35Z and resource_key x402.orthogonal.com/icypeas/api/scrape/profile. | |||
| x402.orthogonal.com/icypeas/api/url-search/profilePOST | 2026-09-08 12:08 UTC | vet402 did not send the declared request body | vet402's side |
What we saw: Before 2026-09-16 23:25 UTC, vet402 sent an empty JSON body on paid POST requests, even when the listing declares a body. The seller refused it with 400 or 422, before or after the payment settled.What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded: settle_failed · HTTP 400 · no tx · held as unsettled_4xxIn export.csv?days=21: the row with attempted_at 2026-09-08T12:08:49Z and resource_key x402.orthogonal.com/icypeas/api/url-search/profile. | |||
| x402.orthogonal.com/peopledatalabs/v5/person/searchPOST | 2026-09-08 12:08 UTC | vet402 did not send the declared request body | vet402's side |
What we saw: Before 2026-09-16 23:25 UTC, vet402 sent an empty JSON body on paid POST requests, even when the listing declares a body. The seller refused it with 400 or 422, before or after the payment settled.What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded: settle_failed · HTTP 400 · no tx · held as unsettled_4xxIn export.csv?days=21: the row with attempted_at 2026-09-08T12:08:26Z and resource_key x402.orthogonal.com/peopledatalabs/v5/person/search. | |||
| x402.orthogonal.com/scrapecreators/v1/tiktok/profileGET | 2026-09-08 12:07 UTC | The paid request was refused as invalid | seller's side |
What we saw: vet402 signed the payment and the paid request got 400, 404, 415 or 422; the payment did not settle. Since 2026-09-16 23:25 UTC vet402 sends the request body the seller's 402 declares (an empty JSON body when it declares none), and since 2026-09-27 23:27 UTC it adds the query parameters the seller's 402 declares on Base.What to fix: Declare the input in the listing (body or query) with example values that work as written. (a listing or config change)Before 2026-09-27 23:27 UTC, vet402 did not add query parameters to paid requests on Base; this listing declares optional ones.Recorded: settle_failed · HTTP 400 · no tx · held as unsettled_4xxIn export.csv?days=21: the row with attempted_at 2026-09-08T12:07:51Z and resource_key x402.orthogonal.com/scrapecreators/v1/tiktok/profile. | |||
| x402.orthogonal.com/vat-validation/v1/calculateGET | 2026-09-08 07:01 UTC | The paid request was refused as invalid | seller's side |
What we saw: vet402 signed the payment and the paid request got 400, 404, 415 or 422; the payment did not settle. Since 2026-09-16 23:25 UTC vet402 sends the request body the seller's 402 declares (an empty JSON body when it declares none), and since 2026-09-27 23:27 UTC it adds the query parameters the seller's 402 declares on Base.What to fix: Declare the input in the listing (body or query) with example values that work as written. (a listing or config change)Before 2026-09-27 23:27 UTC, vet402 did not add query parameters to paid requests on Base; this listing declares optional ones.Recorded: settle_failed · HTTP 400 · no tx · held as unsettled_4xxIn export.csv?days=21: the row with attempted_at 2026-09-08T07:01:42Z and resource_key x402.orthogonal.com/vat-validation/v1/calculate. | |||
| x402.orthogonal.com/bytemine/v1/proposals/generatePOST | 2026-09-08 07:01 UTC | vet402 did not send the declared request body | vet402's side |
What we saw: Before 2026-09-16 23:25 UTC, vet402 sent an empty JSON body on paid POST requests, even when the listing declares a body. The seller refused it with 400 or 422, before or after the payment settled.What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded: settle_failed · HTTP 400 · no tx · held as unsettled_4xxIn export.csv?days=21: the row with attempted_at 2026-09-08T07:01:33Z and resource_key x402.orthogonal.com/bytemine/v1/proposals/generate. | |||
| x402.orthogonal.com/findymail/api/search/namePOST | 2026-09-08 07:01 UTC | vet402 did not send the declared request body | vet402's side |
What we saw: Before 2026-09-16 23:25 UTC, vet402 sent an empty JSON body on paid POST requests, even when the listing declares a body. The seller refused it with 400 or 422, before or after the payment settled.What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded: settle_failed · HTTP 400 · no tx · held as unsettled_4xxIn export.csv?days=21: the row with attempted_at 2026-09-08T07:01:24Z and resource_key x402.orthogonal.com/findymail/api/search/name. | |||
| x402.orthogonal.com/rocketreach/profile-company/lookupGET | 2026-09-08 07:01 UTC | Took the payment, then refused the input | seller's side |
What we saw: The payment settled on-chain, and then the paid request got 400, 404, 415 or 422: the route took the payment before it checked the input, so the buyer paid for a refused request. When the seller declared a body, or a required query, that vet402 was not yet sending, the row is on vet402's side instead.What to fix: Check the input before you settle, so an invalid request is refused without taking the payment; and declare the input in the listing with example values that work as written. (a server change)Before 2026-09-27 23:27 UTC, vet402 did not add query parameters to paid requests on Base; this listing declares optional ones.Recorded: settled · HTTP 400 · tx 0xcc1c2254…6993 · held as settled_4xxIn export.csv?days=21: the row with attempted_at 2026-09-08T07:01:18Z and resource_key x402.orthogonal.com/rocketreach/profile-company/lookup. | |||
| x402.orthogonal.com/leadsforge/lookalikes/searchPOST | 2026-09-08 07:01 UTC | vet402 did not send the declared request body | vet402's side |
What we saw: Before 2026-09-16 23:25 UTC, vet402 sent an empty JSON body on paid POST requests, even when the listing declares a body. The seller refused it with 400 or 422, before or after the payment settled.What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded: settle_failed · HTTP 400 · no tx · held as unsettled_4xxIn export.csv?days=21: the row with attempted_at 2026-09-08T07:01:15Z and resource_key x402.orthogonal.com/leadsforge/lookalikes/search. | |||
| x402.orthogonal.com/signalbase/signals/job-changesGET | 2026-09-08 07:00 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x0aa43340…f51bIn export.csv?days=21: the row with attempted_at 2026-09-08T07:00:45Z and resource_key x402.orthogonal.com/signalbase/signals/job-changes. | |||
| x402.orthogonal.com/leadsforge/company-followers/filters/levelsGET | 2026-09-07 19:00 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0xf1c0c043…f515In export.csv?days=22: the row with attempted_at 2026-09-07T19:00:50Z and resource_key x402.orthogonal.com/leadsforge/company-followers/filters/levels. | |||
| x402.orthogonal.com/abstractapi/v2GET | 2026-09-06 19:01 UTC | The paid request was refused as invalid | seller's side |
What we saw: vet402 signed the payment and the paid request got 400, 404, 415 or 422; the payment did not settle. Since 2026-09-16 23:25 UTC vet402 sends the request body the seller's 402 declares (an empty JSON body when it declares none), and since 2026-09-27 23:27 UTC it adds the query parameters the seller's 402 declares on Base.What to fix: Declare the input in the listing (body or query) with example values that work as written. (a listing or config change)Before 2026-09-27 23:27 UTC, vet402 did not add query parameters to paid requests on Base; this listing declares optional ones.Recorded: settle_failed · HTTP 400 · no tx · held as unsettled_4xxIn export.csv?days=23: the row with attempted_at 2026-09-06T19:01:52Z and resource_key x402.orthogonal.com/abstractapi/v2. | |||
| x402.orthogonal.com/apollo/api/v1/organizations/enrichGET | 2026-09-06 19:01 UTC | The paid request was refused as invalid | seller's side |
What we saw: vet402 signed the payment and the paid request got 400, 404, 415 or 422; the payment did not settle. Since 2026-09-16 23:25 UTC vet402 sends the request body the seller's 402 declares (an empty JSON body when it declares none), and since 2026-09-27 23:27 UTC it adds the query parameters the seller's 402 declares on Base.What to fix: Declare the input in the listing (body or query) with example values that work as written. (a listing or config change)Before 2026-09-27 23:27 UTC, vet402 did not add query parameters to paid requests on Base; this listing declares optional ones.Recorded: settle_failed · HTTP 400 · no tx · held as unsettled_4xxIn export.csv?days=23: the row with attempted_at 2026-09-06T19:01:13Z and resource_key x402.orthogonal.com/apollo/api/v1/organizations/enrich. | |||
| x402.orthogonal.com/leadsforge/search/countPOST | 2026-09-06 12:09 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0xa9eb9821…8a3aIn export.csv?days=23: the row with attempted_at 2026-09-06T12:09:46Z and resource_key x402.orthogonal.com/leadsforge/search/count. | |||
| x402.orthogonal.com/coresignal/v2/employee_multi_source/collect/309627871GET | 2026-09-06 07:01 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0xcdb745a2…2351In export.csv?days=23: the row with attempted_at 2026-09-06T07:01:24Z and resource_key x402.orthogonal.com/coresignal/v2/employee_multi_source/collect/309627871. | |||
| x402.orthogonal.com/coresignal/v2/company_clean/collect/98847749GET | 2026-09-06 01:00 UTC | vet402's own run did not finish | vet402's side |
What we saw: vet402's request did not complete on its side (its run was cut off, or a step failed inside vet402).What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded: request_error · HTTP — · no txNot in the public export: a vet402-side state it leaves out. | |||
| x402.orthogonal.com/seltz/v1/searchPOST | 2026-09-04 09:23 UTC | vet402 did not send the declared request body | vet402's side |
What we saw: Before 2026-09-16 23:25 UTC, vet402 sent an empty JSON body on paid POST requests, even when the listing declares a body. The seller refused it with 400 or 422, before or after the payment settled.What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded: settle_failed · HTTP 400 · no tx · held as unsettled_4xxIn export.csv?days=25: the row with attempted_at 2026-09-04T09:23:50Z and resource_key x402.orthogonal.com/seltz/v1/search. | |||
| x402.orthogonal.com/olostep/v1/scrapesPOST | 2026-09-02 01:00 UTC | vet402 did not send the declared request body | vet402's side |
What we saw: Before 2026-09-16 23:25 UTC, vet402 sent an empty JSON body on paid POST requests, even when the listing declares a body. The seller refused it with 400 or 422, before or after the payment settled.What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded: settle_failed · HTTP 400 · no tx · held as unsettled_4xxIn export.csv?days=28: the row with attempted_at 2026-09-02T01:00:48Z and resource_key x402.orthogonal.com/olostep/v1/scrapes. | |||
| x402.orthogonal.com/abstractapi/v1/convertGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
2.How to read this
Each listing shows its latest purchase on Base and up to four earlier ones. Whose side says where the failure came from: the seller's answer or listing, or vet402 itself. A row held (held_reason in the export) is not counted against the seller in the delivered numbers, because vet402 cannot rule out that its request was the problem. The transaction link opens the settlement on Basescan. 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?
Open the listing's record (the link in the first column) and use “Dispute this record” there. Say which purchase and what you saw instead. The row is not deleted on dispute; a correction is published with the same weight.