> For the complete documentation index, see [llms.txt](https://docs.nfstay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nfstay.com/partners/particle-network.md).
# Particle Network
### Understanding Wallet-as-a-Service
Wallet-as-a-Service represents a **fundamental shift** in how users, especially non-Web3-natives, **onboard and interact with decentralized applications**. Wallet-as-a-Services leverages **non-custodial key management mechanisms to facilitate account creation** through familiar **social accounts**, upon which interaction with these accounts happens through an interface embedded within an application. Onboarding users through traditional means (OAuth) and then keeping on-chain interactions confined within a given application, rather than requiring extension downloads or external applications, enables a user experience (UX) flow that feels familiar and natural to end-users.
The resulting account from this novel onboarding process is generally an Externally-Owned-Account (EOA). However, some Wallet-as-a-Service providers, such as Particle Network, use these EOAs as signers (owners) for smart accounts, thus bringing the power of account abstraction directly to accounts generated via WaaS, further increasing the possibilities for powerful UX.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.nfstay.com/partners/particle-network.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.