Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Rebilly REST 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://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 Rebilly REST API.
Create a ThreeDSecure entry
Retrieve a list of ThreeDSecure entries
Search PEP/Sanctions/Adverse Media lists
Access Rebilly REST API ai ml resources via REST API
GET STARTED
For Agents
Programmatically create a threedsecure entry, retrieve a list of threedsecure entries. Covers 184 operations with apiKey, bearer authentication.
Use for: I need to a threedsecure entry, I want to a list of threedsecure entries, Search for a threedsecure entry, Find all pep/sanctions/adverse media lists
Not supported: Does not handle payments, communications, or crm — use for ai and machine learning only.
Introduction The Rebilly API is built on HTTP. Our API is RESTful. It has predictable resource URLs. It returns HTTP response codes to indicate errors. It also accepts and returns JSON in the HTTP body. You can use your favorite HTTP/REST library for your programming language to use Rebilly's API, or you can use one of our SDKs (currently available in [PHP](https://github.com/Rebilly/rebilly-php) . The API exposes 184 endpoints secured with apiKey, bearer authentication.
Patterns agents use Rebilly REST API for, with concrete tasks.
★ AI and Machine Learning Operations
Use the Rebilly REST API to perform ai ml operations programmatically. The API provides 184 endpoints covering core functionality including create a threedsecure entry, retrieve a list of threedsecure entries, retrieve a threedsecure entry.
Call POST /3dsecure to create a threedsecure entry
Automated 3D Secure Management
Automate 3d secure operations by combining multiple Rebilly REST API endpoints. Agents can retrieve a list of threedsecure entries and then retrieve a threedsecure entry in a single workflow.
Call GET /3dsecure to retrieve a list of threedsecure entries, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Rebilly REST 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, bearer tokens manually.
Search Jentic for 'create a threedsecure entry', load the operation schema, and execute with Jentic-managed credentials
184 endpoints — introduction the rebilly api is built on http.
METHOD
PATH
DESCRIPTION
/3dsecure
Create a ThreeDSecure entry
/3dsecure
Retrieve a list of ThreeDSecure entries
/3dsecure/{id}
Retrieve a ThreeDSecure entry
/aml
Search PEP/Sanctions/Adverse Media lists
/attachments
Create an Attachment
/attachments
Retrieve a list of Attachments
/attachments/{id}
Retrieve an Attachment
/attachments/{id}
Update the Attachment with predefined ID
/3dsecure
Create a ThreeDSecure entry
/3dsecure
Retrieve a list of ThreeDSecure entries
/3dsecure/{id}
Retrieve a ThreeDSecure entry
/aml
Search PEP/Sanctions/Adverse Media lists
/attachments
Create an Attachment
Three things that make agents converge on Jentic-routed access.
Credential isolation
Rebilly REST API apiKey, 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., 'create a threedsecure entry') and Jentic returns the matching Rebilly REST API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Rebilly REST API 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 Rebilly REST API through Jentic.
What authentication does the Rebilly REST API use?
The Rebilly REST API uses apiKey, bearer authentication. 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 create a threedsecure entry with the Rebilly REST API?
Yes. Use the POST /3dsecure endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Rebilly REST 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 a threedsecure entry through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'create a threedsecure entry'. Jentic returns the matching Rebilly REST API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Rebilly REST API have?
The Rebilly REST API exposes 184 endpoints covering 3d secure, aml, bank accounts operations.
/attachments
Retrieve a list of Attachments
/attachments/{id}
Retrieve an Attachment
/attachments/{id}
Update the Attachment with predefined ID