uploads.sh valid
uploads.sh
File hosting for agents and humans — hosted CLI, agent skill, and MCP server. Open source for self-hosting.
- Authority
- 45 reach 0 · trust 5 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- https://uploads.sh/llms.txt
- llms-full.txt
- https://uploads.sh/llms-full.txt
- Sections
- 7
- Links
- 39
- Size
- 10156 bytes
- Country
- — Publisher location unknown; CDN address excluded
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-23T00:03:56.936Z
- Last checked
- 2026-10-23T00:03:57.453Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-23T00:03:56.946Z. Cached copy · Source on uploads.sh
# uploads.sh
> File hosting for agents and humans — hosted CLI, agent skill, and MCP server. Open source for self-hosting.
Access requires a workspace — create your own with a linked GitHub account, or be invited to an existing one. Hosted files are public (including media attached to private repositories). Do not upload secrets or sensitive UI. APIs may change without notice while the project is in active development.
Expanded one-file guide: [llms-full.txt](https://uploads.sh/llms-full.txt).
Landed on the GitHub monorepo instead? Start at [repo llms.txt](https://github.com/buildinternet/uploads/blob/main/llms.txt) (product use vs contribute).
## When to use this
Use uploads.sh when a screenshot, screen recording, diagram, or other visual needs to land on a GitHub pull request or issue. Reach for it as you produce the visual. Do not wait until GitHub's attachment path fails.
Also use it to host a local file (or a public HTTPS URL) at a stable public URL you can paste anywhere.
Do not upload secrets, tokens, or sensitive UI.
How to call it:
- Local checkout: `uploads put` / `uploads attach`, or the github-screenshots skill
- No filesystem: hosted MCP at https://agents.uploads.sh/mcp
- Exact flags and contracts: uploads-cli skill
## Start here
- [Home](https://uploads.sh/): product overview and copyable install commands
- [Full agent guide (llms-full.txt)](https://uploads.sh/llms-full.txt): install, auth, stage/attach loops, hosted MCP contracts, cautions
- [Docs](https://uploads.sh/docs): overview, one-time install, and links to the focused guides below (search with `uploads docs` or MCP `search_docs`; catalog at https://uploads.sh/docs.json)
- [Changelog](https://uploads.sh/changelog): platform updates and CLI releases, newest first (Atom at https://uploads.sh/changelog.xml; JSON at https://uploads.sh/changelog.json; `uploads changelog` in the CLI)
- [Docs: attach artifacts to pull requests](https://uploads.sh/docs/attach-pull-request-images): attach media to PRs/issues, stage screenshots before a PR exists, pair a before/after with --state, get a URL for any accepted file (local path or `put --url`)
- [Docs: capture & annotate](https://uploads.sh/docs/capture): capture a URL or local HTML file and host it in one step (`uploads screenshot`), then bake boxes, arrows, labels, freeform strokes, and solid redactions into a capture (`uploads screenshot --annotate` or `uploads annotate`)
- [Docs: galleries](https://uploads.sh/docs/galleries): create an ordered set of media behind one public link at /g/<id>, add files with uploads put --gallery, and link the gallery to a PR or issue
- [Docs: live links](https://uploads.sh/docs/feeds): a newest-first public page at /c/<id> of the files tagged with a repo or one PR/issue (`uploads feed create`, MCP `feed_create`; the CLI, API and MCP call it a feed); the managed PR comment links to its PR's live link
- [Docs: GitHub App](https://uploads.sh/docs/github-app): recommended install for bot-posted a
…Machine-readable: GET /v1/resolve?q=uploads.sh · GET /v1/domain/uploads.sh · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage uploads.sh, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for uploads.sh:
1. POST https://agentwebmap.com/v1/sites/uploads.sh/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://uploads.sh/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/uploads.sh/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/uploads.sh).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.