{"id":"glitternetwork-pinme","name":"pinme","af_score":42.5,"security_score":49.0,"reliability_score":22.5,"what_it_does":"PinMe is a zero-config CLI tool that uploads/export static frontend content to an IPFS-based publishing system, producing preview URLs and optionally binding content to a domain (PinMe subdomains and custom DNS) using an AppKey/VIP membership.","best_when":"You have a static frontend build artifact (dist/build/out/public) and want quick, verifiable IPFS-based hosting with optional domain binding.","avoid_when":"You need first-class REST/SDK integrations, fine-grained programmatic domain/app management, or guaranteed IPFS-network-wide deletion semantics.","last_evaluated":"2026-03-29T18:05:28.347405+00:00","has_mcp":false,"has_api":false,"auth_methods":["AppKey via pinme set-appkey","Login/logout via local storage","VIP membership for domain binding (authorization gating)"],"has_free_tier":true,"known_gotchas":["CLI is designed around interactive prompts when arguments are missing; agents should always pass explicit paths/CIDs to avoid prompt-driven flows.","Router mode constraint: deployed sites may require hash routing; history-mode sites can 404 on sub-routes.","Domain binding requires VIP and AppKey; agents that attempt binding without auth may fail.","Avoid uploading prohibited paths/files (node_modules, .env, .git, src, config files); ensure build output contains index.html and static assets.","Export is asynchronous and uses polling every 5 seconds; long-running operations may need timeout handling in automation."],"error_quality":null}