Lennert Onyx Api2Clients
Browse all Swaggerhub Lennert Onyx APIs★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controlnone2 EndpointsREST
For Agents
Programmatically fetch contractor info, fetch user info. Covers 2 operations.
Use for: I need to fetch contractor info, I want to fetch user info, Get the current status of Api2Clients resources, List all records from Api2Clients
Not supported: Does not handle payments, communications, or crm — use for developer tools only.
API to fetch contractor/user information from OnyxOne. The apikey will be provided by OnyxOne upon request Changelog: * 2.0.0 (Expected beta release: 03/10/2023, Expected live release: 03/10/2023) * * Not backward compatible change: UIN is removed from the user response. The API exposes 2 endpoints.
Install Jentic One Beta
Connect the Api2Clients to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Api2Clients, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 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.
Capabilities
What an agent can do with Api2Clients API.
Fetch contractor info
Manage developer tools data programmatically
Integrate Api2Clients into automated workflows
Query and filter Api2Clients records by parameters
Monitor Api2Clients operational status and events
Use Cases
Patterns agents use Api2Clients API for, with concrete tasks.
★ Developer Tools Operations
Use the Api2Clients to perform developer tools operations programmatically. The API provides 2 endpoints covering core functionality including fetch contractor info, fetch user info.
Call GET /companies to fetch contractor info
Data Retrieval and Monitoring
Query Api2Clients resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.
Poll the primary Api2Clients endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call Api2Clients 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 none tokens manually.
Search Jentic for 'fetch contractor info', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
2 endpoints — api to fetch contractor/user information from onyxone.
METHOD
PATH
DESCRIPTION
GET
/companies
Fetch contractor info
GET
/users
Fetch user info
GET
/companies
Fetch contractor info
GET
/users
Fetch user info
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Api2Clients none 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., 'fetch contractor info') and Jentic returns the matching Api2Clients operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Api2Clients 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
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
FAQs
Specific to using Api2Clients API through Jentic.
What authentication does the Api2Clients use?
The Api2Clients uses no 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 fetch contractor info with the Api2Clients?
Yes. Use the GET /companies endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Api2Clients?
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 fetch contractor info through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'fetch contractor info'. Jentic returns the matching Api2Clients operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Api2Clients have?
The Api2Clients exposes 2 endpoints covering companies, users operations.
GET STARTED