# OOBE

## OOBE-PROTOCOL Docs

- [Welcome to OOBE Protocol](https://oobe-protocol.gitbook.io/oobe-protocol/readme.md)
- [Protocol - Structure](https://oobe-protocol.gitbook.io/oobe-protocol/getting-started/publish-your-docs.md): Configurable Modules and API Key Authentication
- [Core - Introduction](https://oobe-protocol.gitbook.io/oobe-protocol/getting-started/quickstart.md): What is Oobe Core?  is a framework designed to facilitate the integration and management of various services and modules within a unified platform
- [How to Set Up the SDK in Node.js Environments](https://oobe-protocol.gitbook.io/oobe-protocol/getting-started/quickstart/how-to-set-up-the-sdk-in-node.js-environments.md): Start with the right set up of your environments!
- [How to Set Up API Key Authentication](https://oobe-protocol.gitbook.io/oobe-protocol/getting-started/quickstart/how-to-set-up-api-key-authentication.md): Authenticate with API Keys - AUTH v1
- [Initializing The Core Module](https://oobe-protocol.gitbook.io/oobe-protocol/getting-started/quickstart/initializing-the-core-module.md)
- [Quick Usage Example](https://oobe-protocol.gitbook.io/oobe-protocol/getting-started/quickstart/quick-usage-example.md): An easy example to run the agent using Readline
- [DApp - Agent Builder](https://oobe-protocol.gitbook.io/oobe-protocol/getting-started/quickstart-1.md)
- [OOBE-PROTOCOL + NEXTJS + LANGCHAIN](https://oobe-protocol.gitbook.io/oobe-protocol/getting-started/quickstart-2.md): \[NOT RELEASED YET]
- [Backend - Building an API Router to handle agent actions](https://oobe-protocol.gitbook.io/oobe-protocol/getting-started/quickstart-2/backend-building-an-api-router-to-handle-agent-actions.md)
- [Frontend - handle data from the agent API using useChat from ai-sdk](https://oobe-protocol.gitbook.io/oobe-protocol/getting-started/quickstart-2/frontend-handle-data-from-the-agent-api-using-usechat-from-ai-sdk.md)
- [Synapse Gateway RPC](https://oobe-protocol.gitbook.io/oobe-protocol/synapse-gateway-rpc.md): Synapse Gateway RPC is a high-performance, scalable RPC gateway designed for Solana. It provides optimized endpoint routing, intelligent request balancing, and advanced caching.
- [Why Synapse Gateway?](https://oobe-protocol.gitbook.io/oobe-protocol/synapse-gateway-rpc/why-synapse-gateway.md): standard RPCs aren’t enough when speed, reliability, and scalability matter. Synapse Gateway delivers optimized Solana access with intelligent load balancing, advanced caching, and zero downtime
- [Core Features](https://oobe-protocol.gitbook.io/oobe-protocol/synapse-gateway-rpc/core-features.md): Designed for users, developers and high-demand apps
- [Smart Data Relayer](https://oobe-protocol.gitbook.io/oobe-protocol/synapse-gateway-rpc/smart-data-relayer.md): Explanation for Synapse Gateway Only
- [Access Tiers](https://oobe-protocol.gitbook.io/oobe-protocol/synapse-gateway-rpc/access-tiers.md): Table that represent tiers and prices. Can may be change in future!
- [Gateway Architecture](https://oobe-protocol.gitbook.io/oobe-protocol/synapse-gateway-rpc/gateway-architecture.md)
- [Integration with OOBE Protocol](https://oobe-protocol.gitbook.io/oobe-protocol/synapse-gateway-rpc/integration-with-oobe-protocol.md): Synapse Gateway integration and explanation in a sum
- [Info And Contacts](https://oobe-protocol.gitbook.io/oobe-protocol/official-link/info-and-contacts.md): OOBE - OFFICIAL LINKS


---

# 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, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on a page URL with the `ask` query parameter:
```
GET https://oobe-protocol.gitbook.io/oobe-protocol/readme.md?ask=<question>
```
The question should be specific, self-contained, and written in natural language.
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.