For Agents
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SuiteBox Meeting Requests, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsuitebox.suitebox.co.nz%2Fsuitebox-suitebox-co-nz" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsuitebox.suitebox.co.nz%2Fsuitebox-suitebox-co-nz" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with SuiteBox Meeting Requests API.
SbxMeetingRequest
SbxCancelMeeting
SbxAuthenticateUser
Query and filter SuiteBox Meeting Requests records by parameters
GET STARTED
Programmatically sbxmeetingrequest, sbxcancelmeeting. Covers 3 operations.
Use for: I need to sbxmeetingrequest, I want to sbxcancelmeeting, Search for sbxauthenticateuser, List all records from SuiteBox Meeting Requests
Not supported: Does not handle payments, communications, or crm - use for productivity only.
This is a dummy web site to show the set up of swagger to manager API's for SuiteBox. The API exposes 3 endpoints.
Monitor SuiteBox Meeting Requests operational status and events
Patterns agents use SuiteBox Meeting Requests API for, with concrete tasks.
★ Productivity Operations
Use the SuiteBox Meeting Requests to perform productivity operations programmatically. The API provides 3 endpoints covering core functionality including sbxmeetingrequest, sbxcancelmeeting, sbxauthenticateuser.
Call GET /Meetings/SbxMeetingRequest to sbxmeetingrequest
Automated Authenticate Management
Automate authenticate operations by combining multiple SuiteBox Meeting Requests endpoints. Agents can sbxcancelmeeting and then sbxauthenticateuser in a single workflow.
Call GET /Meetings/SbxCancelMeeting to sbxcancelmeeting, then verify the result
AI Agent Integration via Jentic
AI agents discover and call SuiteBox Meeting Requests endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.
Search Jentic for 'sbxmeetingrequest', load the operation schema, and execute with Jentic-managed credentials
3 endpoints — this is a dummy web site to show the set up of swagger to manager api's for suitebox.
METHOD
PATH
DESCRIPTION
/Meetings/SbxMeetingRequest
SbxMeetingRequest
/Meetings/SbxCancelMeeting
SbxCancelMeeting
/Authentication/SbxAuthenticateUser
SbxAuthenticateUser
/Meetings/SbxMeetingRequest
SbxMeetingRequest
/Meetings/SbxCancelMeeting
SbxCancelMeeting
/Authentication/SbxAuthenticateUser
SbxAuthenticateUser
What agents get from Jentic-routed access to this vendor.
Setup
The SuiteBox Meeting Requests API exposes meeting request, cancellation, and user authentication calls that you would otherwise wire against its SBX host yourself. Through Jentic you install once, import SuiteBox Meeting Requests from the API Directory, and your agent calls them without you hand-building the request plumbing.
Permission scoping
SuiteBox carries its meeting and user targets in the request parameters rather than a resource path, so you limit the agent to the operations it needs, such as requesting a meeting. Because you choose the operations, cancelling a meeting is not available unless you include it in the allowed set.
Credential isolation
Any credential you configure for SuiteBox 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.
Intent-based discovery
Agents search Jentic by intent such as 'request a meeting' or 'cancel a meeting', and Jentic returns the matching SuiteBox operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using SuiteBox Meeting Requests API through Jentic.
What authentication does the SuiteBox Meeting Requests use?
The SuiteBox Meeting Requests uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I sbxmeetingrequest with the SuiteBox Meeting Requests?
Yes. Use the GET /Meetings/SbxMeetingRequest endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the SuiteBox Meeting Requests?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I sbxmeetingrequest through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'sbxmeetingrequest'. Jentic returns the matching SuiteBox Meeting Requests operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the SuiteBox Meeting Requests have?
The SuiteBox Meeting Requests exposes 3 endpoints covering authenticate, meeting operations.