Menu

We probed 171 third-party endpoints and 1,712 of our own handlers
πŸ“°

We probed 171 third-party endpoints and 1,712 of our own handlers

DEV Community: apiΒ·minia2aΒ·6 days ago
#wMO7u1ie
#devtoapi#devto#dev#endpoint#dead
Reading 0:00
15s threshold

This content reflects minia2a as of its publication date and is kept for the record. Current model: x402 pay-per-call in USDC on Base only , 5 free trial calls per signed wallet , no credits.

We probed 171 third-party endpoints and 1,712 of our own handlers. Here is what broke.

November 2026

A marketplace only measures what it decided to measure. Our delivery ledger records failures. It does not record "this request returned 200 OK, held the single-threaded sidecar for five seconds, and produced 80 MB". That second category is the one that hurts, and it is invisible in every error-rate dashboard.

This is a write-up of two audits we ran on our own catalogue: one over our handlers, one over the third-party listings we carry. We are publishing the method and the numbers, including the part where our own probing was wrong.

1. Our own handlers: the failure that does not show up in error rates

We scanned every handler for allocation sites whose size comes from the caller.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.