Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SignUpGenius API, 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%2Fsignupgenius.com%2Fsignupgenius" | 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%2Fsignupgenius.com%2Fsignupgenius" | 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 SignUpGenius API.
Get user profile
Manage analytics data programmatically
Integrate SignUpGenius API into automated workflows
Query and filter SignUpGenius API records by parameters
Monitor SignUpGenius API operational status and events
GET STARTED
Patterns agents use SignUpGenius API for, with concrete tasks.
★ Analytics Operations
Use the SignUpGenius API to perform analytics operations programmatically. The API provides 6 endpoints covering core functionality including get user profile, get active sign-ups created by user, get expired sign-ups.
Call GET /user/profile to get user profile
Automated Reports Management
Automate reports operations by combining multiple SignUpGenius API endpoints. Agents can get active sign-ups created by user and then get expired sign-ups in a single workflow.
Call GET /signups/created/active to get active sign-ups created by user, then verify the result
AI Agent Integration via Jentic
AI agents discover and call SignUpGenius API 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 apiKey tokens manually.
Search Jentic for 'get user profile', load the operation schema, and execute with Jentic-managed credentials
6 endpoints — signupgenius api for retrieving sign-up sheets, participant information, and report data.
METHOD
PATH
DESCRIPTION
/user/profile
Get user profile
/signups/created/active
Get active sign-ups created by user
/signups/created/expired
Get expired sign-ups
/signups/report/{signupId}
Get sign-up report
/signups/report/{signupId}/filled
Get filled slots report
/signups/report/{signupId}/available
Get available slots
/user/profile
Get user profile
/signups/created/active
Get active sign-ups created by user
/signups/created/expired
Get expired sign-ups
/signups/report/{signupId}
Get sign-up report
/signups/report/{signupId}/filled
Get filled slots report
/signups/report/{signupId}/available
Get available slots
What agents get from Jentic-routed access to this vendor.
Setup
Wiring SignUpGenius by hand means passing its user_key in the query string, pointing calls at https://api.signupgenius.com/v2/k, and tracking signup ids across its report endpoints yourself. Through Jentic you install once, import SignUpGenius from the API Directory, store the user_key once, and your agent calls it.
Permission scoping
SignUpGenius puts the signup id in the URL path (/signups/report/{signupId}), so a rule can pin your agent to one signup: it can read that signup's report, filled slots, and available slots and nothing else. You choose the operations it may call, so anything you do not add stays unavailable to the agent.
Credential isolation
Your SignUpGenius user_key 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 'get user profile' or 'get a signup report', and Jentic returns the matching SignUpGenius 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 SignUpGenius API through Jentic.
What authentication does the SignUpGenius API use?
The SignUpGenius API uses an API key passed in the `user_key` query. 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 get user profile with the SignUpGenius API?
Yes. Use the GET /user/profile endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the SignUpGenius API?
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 get user profile through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get user profile'. Jentic returns the matching SignUpGenius API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the SignUpGenius API have?
The SignUpGenius API exposes 6 endpoints covering reports, signups, user operations.
Can I limit what my agent is allowed to do with the SignUpGenius API?
Yes. Because you run Jentic One yourself, your own rules decide which SignUpGenius operations and credentials the agent can use, so anything you do not add stays unavailable. Since SignUpGenius puts the signup id in the URL path (/signups/report/{signupId}), a rule can pin the agent to a single signup and let it read only that signup's report, filled slots, and available slots. You can also restrict it to read-only calls like get user profile and active sign-ups while withholding anything else.
For Agents
Programmatically get user profile, get active sign-ups created by user. Covers 6 operations with apiKey authentication.
Use for: I need to user profile, I want to active sign-ups created by user, Search for expired sign-ups, Find all sign-up report
Not supported: Does not handle payments, communications, or crm - use for analytics only.
SignUpGenius API for retrieving sign-up sheets, participant information, and report data. The API exposes 6 endpoints secured with apiKey authentication.