Nostr Service Providers
Nostr Service Providers in the Crays Nostr research atlas: Nostr Service Providers belong in Apps as service architecture, not as a consumer app. The useful question is what an app can outsource, request or verify through Nostr-native providers.
Nostr Service Providers is now part of the Apps route because it answers a concrete reader question: use it when the reader needs to understand service layers behind app behavior rather than another product card.
Why this belongs in Apps
Nostr Service Providers belong in Apps as service architecture, not as a consumer app. The useful question is what an app can outsource, request or verify through Nostr-native providers. That matters because the Apps hub is not only a client list. It is the product shelf: clients, creator tools, signers, publishing workflows, app services, migration helpers and the evidence that explains how those pieces fit together.
The source page describes it this way: Soapbox frames NSPs as decentralized services that can support Shakespeare projects and related Nostr-native service work. We keep that public signal close, but the Crays page turns it into a clean reader path instead of copying a marketing page.
What it teaches the reader
Nostr Service Providers should help you see one specific job inside Nostr: service providers and AI workflows. If that is the job you brought to the page, this entry gives you the direct source, the nearest category and the next internal Crays page to read.
- Reader job. Use it when the reader needs to understand service layers behind app behavior rather than another product card.
- Apps shelf. Developer tools
- External source. https://soapbox.pub/blog/understanding-nostr-service-providers
Where it fits in the route
Open the category when you want neighbors, open the developer tools shelf when you want the second Crays view, and open the source when a claim needs checking.
Source trail
The cards below are the evidence trail for this entry. They are direct source links, not hidden assumptions.