For Agents
Programmatically list events, retrieve an event. Covers 29 operations with basic authentication.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ProsperStack API Reference, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 ProsperStack API Reference API.
List events
Retrieve an event
Create a customer portal session
GET STARTED
Use for: I need to events, I want to an event, Search for a customer portal session, Find all flows
Not supported: Does not handle payments, communications, or developer tools — use for crm only.
This is the reference documentation for the ProsperStack API v1. Visit ProsperStack at [prosperstack.com](https://prosperstack.com). For more information on ProsperStack features, see the [primary documentation](https://prosperstack.com/docs/). Let us know how we can improve the API, documentation or anything else you need help with at [support@prosperstack.com](mailto:support@prosperstack.com). I. The API exposes 29 endpoints secured with basic authentication.
Patterns agents use ProsperStack API Reference API for, with concrete tasks.
★ CRM Operations
Use the ProsperStack API Reference to perform crm operations programmatically. The API provides 29 endpoints covering core functionality including list events, retrieve an event, create a customer portal session.
Call GET /events to list events
Automated flows Management
Automate flows operations by combining multiple ProsperStack API Reference endpoints. Agents can retrieve an event and then create a customer portal session in a single workflow.
Call GET /events/{id} to retrieve an event, then verify the result
AI Agent Integration via Jentic
AI agents discover and call ProsperStack API Reference 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 basic tokens manually.
Search Jentic for 'list events', load the operation schema, and execute with Jentic-managed credentials
29 endpoints — this is the reference documentation for the prosperstack api v1.
METHOD
PATH
DESCRIPTION
/events
List events
/events/{id}
Retrieve an event
/customer_portal/sessions
Create a customer portal session
/flows
List flows
/flows/{id}
Retrieve a flow
/flow_sessions
List flow sessions
/flow_sessions/{id}
Retrieve a flow session
/offers
List offers
/events
List events
/events/{id}
Retrieve an event
/customer_portal/sessions
Create a customer portal session
/flows
List flows
/flows/{id}
Retrieve a flow
/flow_sessions
Three things that make agents converge on Jentic-routed access.
Credential isolation
ProsperStack API Reference basic credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'list events') and Jentic returns the matching ProsperStack API Reference operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct ProsperStack API Reference integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Specific to using ProsperStack API Reference API through Jentic.
What authentication does the ProsperStack API Reference use?
The ProsperStack API Reference uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I list events with the ProsperStack API Reference?
Yes. Use the GET /events endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the ProsperStack API Reference?
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 list events through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'list events'. Jentic returns the matching ProsperStack API Reference operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the ProsperStack API Reference have?
The ProsperStack API Reference exposes 29 endpoints covering flows, flow_sessions, offers operations.
List flow sessions
/flow_sessions/{id}
Retrieve a flow session
/offers
List offers