PayRequest vs PromptBase at a glance
| Area | PayRequest | PromptBase |
|---|---|---|
| Primary model | Seller-owned commerce platform plus optional marketplace | Specialist AI prompt marketplace |
| Direct storefront | PayRequest shop, product links and marketplace option | Creator profile, marketplace and referral links |
| Prompt delivery | Required teaser; private full text; copy button and email backup | Prompt revealed in buyer account after purchase |
| Prompt categories | 10 outcome categories plus model selection | Deep model, media and style taxonomy |
| Other commerce | Invoices, subscriptions, bookings, digital files and more | Prompts, AI apps/skills and custom AI work |
| Published platform fee | 2%, capped at €25, plus provider processing | 20% marketplace; 0% via seller referral link |
| Marketplace maturity | Newer, broader PayRequest marketplace | Established specialist prompt marketplace |
Choose PayRequest when you bring the audience
PayRequest is strongest when you want one branded place to sell prompts alongside services, downloads, subscriptions or other products. You connect your payment provider and keep the prompt hidden behind a creator-written teaser until payment.
Choose PromptBase for specialist marketplace depth
PromptBase focuses specifically on prompts and related AI products. It has deeper prompt-native discovery, review signals and model/style navigation. Sellers should evaluate whether that specialist audience offsets the marketplace fee for their products.
Compare fees by traffic source
A headline percentage is not the entire decision. PromptBase documents 20% on marketplace sales and 0% through the seller's referral link. PayRequest charges 2% per successful transaction, capped at EUR 25, plus the processing rate from the seller's connected provider. Compare the actual route a buyer uses, processing, currency, tax handling, refunds and the value of discovery.
A practical migration or multi-channel approach
You do not need to remove working marketplace listings immediately. Publish a PayRequest version for your audience, email list or broader catalog, then compare qualified traffic, conversion, net revenue and support burden. Keep product descriptions and model-version notes consistent across channels.