For Agents
Programmatically create inquiry, list inquiries. Covers 4 operations with bearer authentication.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Pluuug 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%2Fsales-api.postoo.io%2Fsales-api-postoo" | 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%2Fsales-api.postoo.io%2Fsales-api-postoo" | 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 Pluuug API.
Create inquiry
List inquiries
Get automation status
Query and filter Pluuug API records by parameters
GET STARTED
Use for: I need to inquiry, I want to inquiries, Search for meetings, Find all automation status
Not supported: Does not handle payments, communications, or crm - use for analytics only.
Pluuug (Postoo) sales automation API with inquiries, meetings, and work tracking. The API exposes 4 endpoints secured with bearer authentication.
Monitor Pluuug API operational status and events
Patterns agents use Pluuug API for, with concrete tasks.
★ Analytics Operations
Use the Pluuug API to perform analytics operations programmatically. The API provides 4 endpoints covering core functionality including create inquiry, list inquiries, list meetings.
Call POST /inquiries to create inquiry
Automated automation Management
Automate automation operations by combining multiple Pluuug API endpoints. Agents can list inquiries and then list meetings in a single workflow.
Call GET /inquiries to list inquiries, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Pluuug 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 bearer tokens manually.
Search Jentic for 'create inquiry', load the operation schema, and execute with Jentic-managed credentials
4 endpoints — pluuug (postoo) sales automation api with inquiries, meetings, and work tracking.
METHOD
PATH
DESCRIPTION
/inquiries
Create inquiry
/inquiries
List inquiries
/meetings
List meetings
/automation
Get automation status
/inquiries
Create inquiry
/inquiries
List inquiries
/meetings
List meetings
/automation
Get automation status
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Pluuug API by hand means handling its bearer token, attaching it to each call against sales-api.postoo.io, and managing your own retries. Through Jentic you install once, import the Pluuug API from the API Directory, store the token once, and your agent calls it.
Permission scoping
The Pluuug API takes inquiry details in the request body rather than pinning to a resource path, so scope the agent to the operations it needs, such as listing inquiries or reading meetings, and leave out creating inquiries unless the agent needs them.
Credential isolation
Your Pluuug API 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.
Intent-based discovery
Agents search Jentic by intent such as 'create an inquiry' or 'list upcoming meetings', and Jentic returns the matching Pluuug API 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 Pluuug API through Jentic.
What authentication does the Pluuug API use?
The Pluuug API uses a Bearer token in the Authorization header. 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 create inquiry with the Pluuug API?
Yes. Use the POST /inquiries endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Pluuug 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 create inquiry through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create inquiry'. Jentic returns the matching Pluuug API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Pluuug API have?
The Pluuug API exposes 4 endpoints covering automation, inquiries, meetings operations.
Can I limit what my agent is allowed to do with the Pluuug API?
Yes. Because you run Jentic One yourself, your own rules decide which Pluuug API operations the agent may call and which credentials it can use. Since the API takes inquiry details in the request body rather than pinning to a resource path, you can grant read-only access such as GET /inquiries to list inquiries and GET /meetings to read meetings, while leaving out POST /inquiries so the agent cannot create new inquiries unless you allow it. The bearer token stays with your instance and is injected only for the operations you permit.