canonical: https://jentic.com/apis/9bot.com.br/9bot # 9bot Agent and MCP Gateway API The 9bot gateway API is the public HTTP surface of the 9bot agent tool gateway: it exchanges JSON-RPC tool messages, serves OAuth and discovery metadata, and reports gateway health. The exact tools and their input schemas are discovered dynamically after OAuth authorization and depend on the application scopes, authorized groups, and tenant configuration in play. It gives an agent one authenticated endpoint to reach whatever tools a tenant has enabled. ## For AI agents Reach a tenant's enabled tools through one authenticated 9bot gateway endpoint, with OAuth and discovery metadata and a health check. ## Scope Does not host the underlying tools, store business data, or manage user accounts. Use for routing agent tool calls and serving discovery metadata only. ## Capabilities - Exchange JSON-RPC tool messages with the 9bot gateway - Discover the tools a tenant has enabled after authorization - Read OAuth protected-resource and authorization-server metadata - Fetch the gateway discovery document and server manifest - Check the gateway's health status ## Use cases ### Agent Tool Access Through One Gateway An agent needs to call whatever tools a given tenant has enabled without integrating each one separately. The 9bot gateway exposes a single JSON-RPC exchange endpoint behind OAuth, and the available tools are discovered dynamically after authorization, so the agent reaches a tenant's full enabled tool set through one authenticated surface. Example prompt: Authorize against the 9bot gateway and exchange a JSON-RPC message to list and call an enabled tool ### OAuth Discovery and Bootstrapping A client needs to bootstrap its OAuth flow against the 9bot gateway before it can call any tool. The gateway serves protected-resource and authorization-server metadata plus a discovery document, so an agent can read the metadata, complete authorization, and learn where to send tool messages without hard-coded configuration. Example prompt: Read the OAuth protected-resource and authorization-server metadata from the gateway to bootstrap an authorization flow ### Gateway Health Monitoring An operations agent watches whether the 9bot gateway is reachable before routing agent traffic to it. The health endpoint returns the gateway's status without a credential, so a monitor can poll it on a schedule and alert when the gateway is unavailable. Example prompt: Poll the gateway health endpoint and raise an alert if it reports an unhealthy status ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/mcp` | Exchange a JSON-RPC tool message | | GET | `/mcp/health` | Get the gateway health status | | GET | `/.well-known/mcp` | Get gateway discovery metadata | | GET | `/.well-known/oauth-protected-resource` | Get OAuth protected-resource metadata | | GET | `/.well-known/oauth-authorization-server` | Get OAuth authorization-server metadata | | GET | `/server.json` | Get the gateway server manifest | ## Key resources - **Gateway** — Exchange JSON-RPC tool messages and discover enabled tools - **Discovery** — Read OAuth and gateway discovery metadata and the server manifest - **Health** — Report the gateway's current health status ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 62 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 56 / 100 - Developer Experience & Jentic Compatibility: 64 / 100 - AI-Readiness & Agent Experience: 49 / 100 - Agent Usability: 94 / 100 - Security: 60 / 100 - AI Discoverability: 69 / 100 - **View full report:** https://jentic.com/apis/9bot.com.br/9bot/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the 9bot gateway by hand means completing its OAuth bearer flow and handling JSON-RPC tool envelopes yourself. Through Jentic you install once, import it from the API Directory, store the token once, and your agent calls the gateway. - **Permission scoping:** You choose which 9bot operations your agent may call, so it can exchange tool messages and read discovery metadata while nothing else is reachable unless you add it. - **Credential handling:** Your 9bot token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'reach the 9bot tool gateway', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Composio** — Composio gives agents a managed catalog of tool integrations; 9bot is a single-tenant gateway that exposes a tenant's own enabled tools. - **Zapier** — Zapier automates multi-step workflows across apps; 9bot is the authenticated gateway an agent calls to invoke a tenant's tools. - **Pipedream** — Pipedream runs event-driven integration workflows; 9bot provides the single tool-exchange endpoint an agent routes calls through. ## FAQ ### What authentication does the 9bot gateway API use? The 9bot gateway authenticates the tool-exchange endpoint with an OAuth bearer token in the Authorization header, per its OpenAPI spec. The discovery and health endpoints are open and need no credential. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's context. ### Can my agent discover which tools a tenant has enabled? Yes. After OAuth authorization, the gateway exposes its available tools dynamically through the JSON-RPC exchange endpoint, and the set depends on the application scopes, authorized groups, and tenant configuration. An agent reads the discovery metadata, authorizes, and then lists and calls the enabled tools through the one exchange endpoint. ### What are the rate limits for the 9bot gateway API? The OpenAPI spec does not define rate limits. Check the 9bot documentation at https://9bot.com.br for the current limits that apply to the gateway. ### How do I reach the 9bot gateway through Jentic? Import the 9bot gateway API from the Jentic directory and give your agent an intent such as 'reach the 9bot tool gateway'. Jentic returns the exchange operation with its input schema, your agent completes authorization and sends tool messages, and your stored token is injected at execution time. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Can I limit what my agent is allowed to do with the 9bot gateway API? Yes. Write a rule that allows only the tool-exchange and discovery-read operations, so your agent can reach enabled tools and read metadata but nothing beyond that surface, and every call it makes is logged. ### Is there a 9bot MCP server? Yes: the 9bot gateway itself is a tool-calling gateway that exchanges JSON-RPC messages and discovers tools dynamically after OAuth authorization. Through Jentic you connect it from the API Directory without wiring that transport yourself: import it, store your credential once, and your agent calls it.