Agent readiness · File upload and storage
uploadthing.com
6 of 14 measurable points under formula 9.2, measured on 2026-08-12. 15 checks exist; each is one HTTP request with a published rule, so every sentence below can be rerun and argued with. 2 of them could not be measured from where we ask, and those are left out of the denominator rather than counted as failures.
A · Discovery
- PASSAnswers an agent user-agentAnswered 200 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology)
- FAILllms.txt publishedNo llms.txt at any of the 6 locations probed
- PASSDocs readable without JavaScript7,354 characters of text without JS, on https://docs.uploadthing.com/getting-started/astro rather than on https://docs.uploadthing.com/
- PASSOn-demand agents not blockedNo robots.txt, so nothing is disallowed for anyone
- N/APaths robots.txt points at answerNo robots.txt, so it points nowhere
- PASSNo punishing crawl delayNo robots.txt, so no Crawl-delay applies
B · Agent entry
- FAILAgent entry pointNone of the 9 known agent entry paths returns a file rather than your page shell
- FAILOAuth dynamic client registrationNo OAuth metadata on any of the 8 hosts probed, including the usual auth and api subdomains
- FAILMCP surfaceNo MCP surface: nothing answered at mcp.uploadthing.com, mcp.uploadthing.com/mcp, mcp.uploadthing.com/v1/mcp, api.uploadthing.com/mcp, /mcp or /api/mcp, and no file mentions MCP
C · Registration
- UNMEASUREDNo CAPTCHA in the signup HTMLUnmeasurable: we found no link to an account signup on the pages we read, while you publish prices at https://uploadthing.com/pricing, so this is a gap in our reading rather than a finding about youLink signup from your home page or your pricing page and this becomes measurable.
- UNMEASUREDSignup reachable without a browserUnmeasurable: we found no link to an account signup on the pages we read, while you publish prices at https://uploadthing.com/pricing, so this is a gap in our reading rather than a finding about youLink signup from your home page or your pricing page and this becomes measurable.
D · Provisioning
- FAILProgrammatic key provisioningNone of the 7 provisioning phrases appears in the 4 documents we read
- PASSFree tier or no-card trial stated in textFree tier or no-card signals at https://uploadthing.com/pricing: "Get Started for Free", "Started for Free", "$0"
E · Integration
- PASSTyped SDK on the registryuploadthing@7.7.4 ships types, matched from the registry by who publishes it rather than by a link on your site
- FAILMachine-readable API descriptionNo OpenAPI spec at the 5 usual paths, none declared by https://docs.uploadthing.com/, and no markdown negotiationPoint at your spec from your docs page with rel="service-desc" and an agent finds it without guessing.
Tell me when this changes
The failures here are the kind nobody notices. An edge rule that starts refusing agents changes nothing a person sees in a browser, so the first sign is usually an integration that quietly stopped working. We rescan weekly and write only when a verdict moves.
This page is the newest scan we hold for uploadthing.com and changes when we rescan. It is not a judgement of the product: we measure whether an unattended run can get through, not whether the thing is any good. The whole corpus is published as JSON and CSV.