Anubis runs a tiered vendor program. Applications go through a vetting step before listings go live. Reputation accrues per fulfilled order. The dispute panel exposes outcomes on the vendor profile page so you can read the history before deciding to order.
New vendor accounts on Anubis cannot list immediately. The platform vets the application, screens for proof-of-life from previous platforms where the vendor has history, and weighs the categories the vendor wants to enter. This filters the worst of the burner-account churn before it reaches the storefront. It does not eliminate it; you still want to read profiles before clicking buy.
Three numbers matter on a vendor profile. Feedback count. On-time-shipment ratio. Dispute-loss ratio. A vendor with a thousand fulfilled orders and a ninety-five percent on-time ratio is a different counterparty from a vendor with twenty fulfilled orders and an unspecified ratio. The data is there; spend ninety seconds reading it before placing an order.
Long order history with consistent ship-out timing. Dispute outcomes weighted toward buyer-favourable resolutions or low overall dispute volume. Active forum presence (vendors who post on the platform forum tend to take their reputation more seriously than vendors who do not). Listings priced in line with category averages, not aggressively cheaper than peers.
New vendors with aggressively underpriced listings. Vendors with high dispute-loss ratios but high feedback count (this is the pattern of a vendor coasting on residual reputation while planning a graceful exit). Listings that ask for finalize-early. The platform supports normal escrow flow by default; if a vendor pushes finalize-early, ask why.
| Role | Address | Lat | |
|---|---|---|---|
| Primary | anubisqr57mqcf3vfqv3hknwbpux5ioqs6atmpwrqive6x6wrkdtrwyd.onion |
142 ms | |
| Backup A | anubisgrlku6ohajojoq52kr6nzixtkfp3jc3pdncgdoykgyfxfutgyd.onion |
178 ms | |
| Backup B | anubisrjpfcc43t4r4zl5ovayivjxqkn63ykkzfngjqvk26lnbgcyryd.onion |
214 ms |