Repuso Public API

Name: Repuso Public API API
Brand: Repuso Public API
Availability: InStock

✓ Official Vendor SpecIdentity AuthAuthenticationbearer19 EndpointsREST

For Agents

Programmatically check connection, get invite requests. Covers 19 operations with bearer authentication.

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.

Install Jentic One Beta (Self-Hosted)

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 | sh

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 instance

Jentic 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 API.

Check Connection

Get Invite Requests

Update Invite Request

Delete Invite Request

Add Invite Request

GET STARTED

Start building with Repuso Public API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Repuso Public API 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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Repuso Public API bearer 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., 'check connection') and Jentic returns the matching Repuso Public API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Repuso Public API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Auth0

Alternative identity auth API

Choose Auth0 when you need a different approach to identity auth operations

Alternative

Okta

Alternative identity auth API

Choose Okta when you need a different approach to identity auth operations

FAQs

Specific to using Repuso Public API 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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.