Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Repsly 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%2Frepsly.com%2Frepsly" | 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%2Frepsly.com%2Frepsly" | 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 Repsly API.
Import a single client
Batch import clients
Integrate Repsly API into automated workflows
Query and filter Repsly API records by parameters
Monitor Repsly API operational status and events
GET STARTED
Patterns agents use Repsly API for, with concrete tasks.
★ CRM Operations
Use the Repsly API to perform crm operations programmatically. The API provides 25 endpoints covering core functionality including import a single client, batch import clients, import a single account.
Call POST /import/client to import a single client
Automated Export Management
Automate export operations by combining multiple Repsly API endpoints. Agents can batch import clients and then import a single account in a single workflow.
Call POST /import/clientList to batch import clients, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Repsly 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 basic tokens manually.
Search Jentic for 'import a single client', load the operation schema, and execute with Jentic-managed credentials
25 endpoints — repsly field service management api for importing and exporting clients, products, packages, pricelists, schedules, users, and more.
METHOD
PATH
DESCRIPTION
/import/client
Import a single client
/import/clientList
Batch import clients
/import/account
Import a single account
/import/accountList
Batch import accounts
/import/product
Import a single product
/import/productList
Batch import products
/import/package
Import a single package
/import/packageList
Batch import packages
/import/client
Import a single client
/import/clientList
Batch import clients
/import/account
Import a single account
/import/accountList
Batch import accounts
/import/product
Import a single product
/import/productList
Batch import products
/import/package
Import a single package
/import/packageList
Batch import packages
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Repsly by hand means encoding HTTP basic username and password on every request against the /v3 host and batching client, account, and product imports yourself. Through Jentic you install once, import the Repsly API from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
Repsly's import endpoints address the target in the request body rather than a resource id in the path, so limit the agent to the operations it needs, such as importing a single client or a client list. You choose that set, so the agent only runs the import operations you grant.
Credential isolation
Your Repsly basic-auth credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'import a single client' or 'import a product list', and Jentic returns the matching Repsly 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 Repsly API through Jentic.
What authentication does the Repsly API use?
The Repsly API uses HTTP Basic authentication with username and password. 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 import a single client with the Repsly API?
Yes. Use the POST /import/client endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Repsly 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 import a single client through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'import a single client'. Jentic returns the matching Repsly API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Repsly API have?
The Repsly API exposes 25 endpoints covering export, import, sales operations.
Can I limit what my agent is allowed to do with the Repsly API?
Yes. Because you run Jentic One yourself, your own rules decide which Repsly operations and credentials your agent may use. Since Repsly's import endpoints name the target in the request body rather than a resource id in the path, you grant only the specific operations the agent needs, such as POST /import/client to import a single client or POST /import/clientList to batch import clients. The agent can call just those import operations you have allowed, and your basic-auth credentials stay injected at execution time rather than exposed to the agent.
For Agents
Programmatically import a single client, batch import clients. Covers 25 operations with basic authentication.
Use for: I need to import a single client, I want to batch import clients, Search for import a single account, Find all batch import accounts
Not supported: Does not handle payments, communications, or developer tools - use for crm only.
Repsly field service management API for importing and exporting clients, products, packages, pricelists, schedules, users, and more. Supports both JSON and XML. The API exposes 25 endpoints secured with basic authentication.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>