Product
Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing
Developers

GET STARTED

API DirectoryBrowse 10,000+ APIs Ready For AI Agent IntegrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI Readiness using our scorecardArazzo UIVisualize Arazzo Workflows As Interactive DocumentationArazzo EditorBuild And Edit Multi-Step API Workflows Visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
Resources
Company
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
Resources
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

Terms & Conditions•Privacy Policy•
© 2026 Jentic. All rights reserved.
Switch to light modeSwitch to dark mode
APIs / Developer Tools / Swaggerhub Lennert Onyx / Api2Clients
Api2Clients logo

Lennert Onyx Api2Clients

Browse all Swaggerhub Lennert Onyx APIs
Community OpenAPI document · agent-readyDeveloper ToolsSource Controlnone2 EndpointsREST

Know of an official OpenAPI document? Contribute it →

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.

Jentic One on GithubView OpenAPI Document

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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.lennert-onyx%2Fapi2clients" | sh
2

Step 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%2Fswaggerhub.lennert-onyx%2Fapi2clients" | 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 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?

What agents get from Jentic-routed access to this vendor.

Setup

Setup

Wiring Api2Clients by hand means choosing between its SwaggerHub mock host and the beta.onyxone.com backend and shaping its company and user reads yourself. Through Jentic you install once, import Api2Clients from the API Directory, and your agent calls it without you hand-building each request.

Permission scoping

Permission scoping

Api2Clients exposes only company and user reads and carries any filters outside the resource path, so limit the agent to the operations it needs, such as listing companies or users. Both exposed operations are read-only, and you choose which of them the agent may call.

Credential management

Credential isolation

Any Api2Clients 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

Intent-based discovery

Agents search Jentic by intent such as 'list companies' or 'fetch users', and Jentic returns the matching Api2Clients operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

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

Alternative

Gitlab

→

Alternative developer tools API

Choose Gitlab 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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.

Can I limit what my agent is allowed to do with the Api2Clients API?

Yes. Api2Clients exposes only two read-only operations, listing companies with GET /companies and fetching users with GET /users, and because you run Jentic One yourself, your own rules decide which of these the agent may call. You can grant just GET /companies for contractor lookups while withholding the user read, or allow both. Since the credentials and the allowed operation list live in your self-hosted instance, the agent can only invoke the reads you have explicitly permitted.

GET STARTED

Start building with Api2Clients API

Explore with Jentic One
View OpenAPI Document