Repuso Public API
Official vendor OpenAPI document · agent-readyIdentity AuthAuthenticationbearer19 EndpointsREST
For Agents
Programmatically check connection, get invite requests. Covers 19 operations with bearer authentication.
Use for: I need to check connection, I want to invite requests, Search for one invite request, Find all invite request
Not supported: Does not handle payments, communications, or crm - use for identity and authentication only.
Repuso public API for managing review invite requests, sub-accounts, users, and login URLs. The API exposes 19 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the Repuso Public API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Repuso Public 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.
1
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%2Frepuso.com%2Frepuso" | sh2
Step 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%2Frepuso.com%2Frepuso" | 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.
Capabilities
What an agent can do with Repuso Public API.
Check Connection
Get Invite Requests
Update Invite Request
Delete Invite Request
Add Invite Request
Use Cases
Patterns agents use Repuso Public API for, with concrete tasks.
★ Identity and Authentication Operations
Use the Repuso Public API to perform identity auth operations programmatically. The API provides 19 endpoints covering core functionality including check connection, get invite requests, get one invite request.
Call GET /hello to check connection
Automated Auth Management
Automate auth operations by combining multiple Repuso Public API endpoints. Agents can get invite requests and then get one invite request in a single workflow.
Call GET /invite/requests/get to get invite requests, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Repuso Public 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 'check connection', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
19 endpoints — repuso public api for managing review invite requests, sub-accounts, users, and login urls.
METHOD
PATH
DESCRIPTION
GET
/hello
Check Connection
GET
/invite/requests/get
Get Invite Requests
GET
/invite/requests/get/{inviteRequestId}
Get One Invite Request
PUT
/invite/requests/update/{inviteRequestId}
Update Invite Request
DELETE
/invite/requests/delete/{inviteRequestId}
Delete Invite Request
POST
/invite/requests/add
Add Invite Request
POST
/invite/requests/add_bulk
Add Bulk Invite Requests
POST
/invite/requests/send/{inviteRequestId}
Send Invite Request
GET
/hello
Check Connection
GET
/invite/requests/get
Get Invite Requests
GET
/invite/requests/get/{inviteRequestId}
Get One Invite Request
PUT
/invite/requests/update/{inviteRequestId}
Update Invite Request
DELETE
/invite/requests/delete/{inviteRequestId}
Delete Invite Request
POST
/invite/requests/add
Add Invite Request
POST
/invite/requests/add_bulk
Add Bulk Invite Requests
POST
/invite/requests/send/{inviteRequestId}
Send Invite Request
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Repuso by hand means setting its bearer auth on every request against the /public/v1 host and tracking invite request ids across add, update, send, and delete calls yourself. Through Jentic you install once, import the Repuso Public API from the API Directory, store the key once, and your agent calls it.
Permission scoping
Repuso puts the invite request id in the URL path (/invite/requests/get/{inviteRequestId}), so a rule can pin your agent to reading and sending one invite request. You choose the operations it may call, so a destructive one like invite request deletion is not included unless you add it.
Credential isolation
Your Repuso API 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 'check the connection' or 'send an invite request', and Jentic returns the matching Repuso Public API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Repuso Public API through Jentic.
What authentication does the Repuso Public API use?
The Repuso Public 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 check connection with the Repuso Public API?
Yes. Use the GET /hello endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Repuso Public 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 check connection through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'check connection'. Jentic returns the matching Repuso Public API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Repuso Public API have?
The Repuso Public API exposes 19 endpoints covering auth, invite requests, account operations.
Can I limit what my agent is allowed to do with the Repuso Public API?
Yes. Because you run Jentic One yourself, your own rules decide which Repuso operations and credentials the agent may use. Repuso puts the invite request id in the URL path, such as /invite/requests/get/{inviteRequestId}, so you can pin the agent to reading and sending a single invite request. You choose the operations it may call, so a destructive one like invite request deletion is excluded unless you add it.
GET STARTED