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.