> For the complete documentation index, see [llms.txt](https://docs.baasid.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.baasid.io/100-decentralization/1.-background-of-baasid/1.10-db-governance-of-baasid-participants.md).
# 1.10 "DB Governance” of BaaSid Participants
"BaaSid" does not particularly discriminate between blockchain based services and web or app based services. The user (participant) needs both services, and this is because the users benefit providers in various ways.
**"BaaSid" participants are clients that are already aggressive and have potential, and they make up the Decentralized database for a safe login and verification where they trust one another and verify one another.**
In other words, "BaaSid" participants can access all websites (application standard of "BaaSid's" API) including those of financial institutions, banks, brokerages, and retail with tight security and convenience, quickly and safely. "BaaSid" has this type of potential customer infrastructure and users and is also a form of "verification managed governance."
---
# 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.baasid.io/100-decentralization/1.-background-of-baasid/1.10-db-governance-of-baasid-participants.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.