Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Scoro 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%2Fscoro.com%2Fscoro" | 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%2Fscoro.com%2Fscoro" | 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 Scoro API.
userAuth modify
companyAccount list
contacts list
Query and filter Scoro API records by parameters
Monitor Scoro API operational status and events
GET STARTED
Patterns agents use Scoro API for, with concrete tasks.
★ Developer Tools Operations
Use the Scoro API to perform developer tools operations programmatically. The API provides 148 endpoints covering core functionality including userauth modify, userauth delete, userauth versioncheck.
Call POST /userAuth/modify to userauth modify
Automated Activities Management
Automate activities operations by combining multiple Scoro API endpoints. Agents can userauth delete and then userauth versioncheck in a single workflow.
Call POST /userAuth/delete/{id} to userauth delete, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Scoro 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 tokens manually.
Search Jentic for 'userauth modify', load the operation schema, and execute with Jentic-managed credentials
148 endpoints — scoro work management api.
METHOD
PATH
DESCRIPTION
/userAuth/modify
userAuth modify
/userAuth/delete/{id}
userAuth delete
/userAuth/versionCheck
userAuth versionCheck
/userAuth/verify
userAuth verify
/companyAccount/list
companyAccount list
/contacts/list
contacts list
/contacts/view/{id}
contacts view
/contacts/modify/{id}
contacts modify
/userAuth/modify
userAuth modify
/userAuth/delete/{id}
userAuth delete
/userAuth/versionCheck
userAuth versionCheck
/userAuth/verify
userAuth verify
/companyAccount/list
companyAccount list
/contacts/list
contacts list
/contacts/view/{id}
contacts view
/contacts/modify/{id}
contacts modify
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Scoro API by hand means passing your apiKey in the query string, resolving your per-company host at {company}.scoro.com, and building retries across its many list, view, and modify calls yourself. Through Jentic you install once, import Scoro from the API Directory, store the API key once, and your agent calls it.
Permission scoping
Scoro puts the record id in the URL path (/contacts/view/{id} and /contacts/modify/{id}), so a rule can pin your agent to one contact: it can view or modify that record and nothing else. You choose the operations it may call, so destructive ones like contact deletion or userAuth deletion are not included unless you add them.
Credential isolation
Your Scoro 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 'list contacts' or 'view a contact by id', and Jentic returns the matching Scoro 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 Scoro API through Jentic.
What authentication does the Scoro API use?
The Scoro API uses an API key passed in the `apiKey` query. 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 userauth modify with the Scoro API?
Yes. Use the POST /userAuth/modify endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Scoro 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 userauth modify through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'userauth modify'. Jentic returns the matching Scoro API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Scoro API have?
The Scoro API exposes 148 endpoints covering activities, addresses, bills operations.
Can I limit what my agent is allowed to do with the Scoro API?
Yes. Because you run Jentic One yourself, your own rules decide which Scoro operations and credentials the agent may use. Since Scoro puts the record id in the URL path, such as /contacts/view/{id} and /contacts/modify/{id}, you can pin the agent to a single contact so it only views or modifies that record. You also choose the operations it may call, so destructive ones like contact deletion or userAuth deletion stay off the list unless you explicitly add them.
For Agents
Programmatically userauth modify, userauth delete. Covers 148 operations with apiKey authentication.
Use for: I need to userauth modify, I want to userauth delete, Search for userauth versioncheck, Find all userauth verify
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Scoro work management API. The API exposes 148 endpoints secured with apiKey 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>