Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the WATS 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%2Fwats.com%2Fwats" | 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%2Fwats.com%2Fwats" | 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 WATS API.
Submit test result
Get test results
Search units under test
Register test station
Monitor WATS API operational status and events
GET STARTED
Patterns agents use WATS API for, with concrete tasks.
★ Analytics Operations
Use the WATS API to perform analytics operations programmatically. The API provides 12 endpoints covering core functionality including submit test result, get test results, get test result details.
Call POST /testresults to submit test result
Automated Test Results Management
Automate test results operations by combining multiple WATS API endpoints. Agents can get test results and then get test result details in a single workflow.
Call GET /testresults to get test results, then verify the result
AI Agent Integration via Jentic
AI agents discover and call WATS 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 bearer tokens manually.
Search Jentic for 'submit test result', load the operation schema, and execute with Jentic-managed credentials
12 endpoints — wats manufacturing test management and analytics api.
METHOD
PATH
DESCRIPTION
/testresults
Submit test result
/testresults
Get test results
/testresults/{testResultId}
Get test result details
/uuts
Search units under test
/uuts/{serialNumber}
Get UUT details
/uuts/{serialNumber}/history
Get UUT test history
/stations
Register test station
/stations
List test stations
/testresults
Submit test result
/testresults
Get test results
/testresults/{testResultId}
Get test result details
/uuts
Search units under test
/uuts/{serialNumber}
Get UUT details
/uuts/{serialNumber}/history
Get UUT test history
/stations
Register test station
/stations
List test stations
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the WATS API by hand means learning its bearer auth, pointing at api.wats.com, and handling responses yourself. Through Jentic you install once, import the WATS API from the API Directory, store the token once, and your agent calls it.
Permission scoping
WATS puts the record id in the URL path (/testresults/{testResultId}, /uuts/{serialNumber}/...), so a rule can pin your agent to reading one test result or unit's history and nothing else. You choose the operations it may call, so writes like submitting test results or creating stations are not included unless you add them.
Credential isolation
Your WATS token 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 'submit a test result' or 'get a unit's history', and Jentic returns the matching WATS 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 WATS API through Jentic.
What authentication does the WATS API use?
The WATS API uses a Bearer token in the Authorization header. 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 submit test result with the WATS API?
Yes. Use the POST /testresults endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the WATS 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 submit test result through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'submit test result'. Jentic returns the matching WATS API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the WATS API have?
The WATS API exposes 12 endpoints covering test results, uuts, stations operations.
Can I limit what my agent is allowed to do with the WATS API?
Yes. Because you run Jentic One yourself, your own rules decide which WATS operations and credentials the agent may use. Since WATS puts the record id in the URL path (/testresults/{testResultId}, /uuts/{serialNumber}/history), you can pin the agent to reading one test result or one unit's history and nothing else. Write operations like POST /testresults to submit a test result or POST /stations to register a station are excluded unless you explicitly grant them.
For Agents
Programmatically submit test result, get test results. Covers 12 operations with bearer authentication.
Use for: I need to submit test result, I want to test results, Search for test result details, Find all units under test
Not supported: Does not handle payments, communications, or crm - use for analytics only.
WATS manufacturing test management and analytics API. Manage test results, units under test, stations, and production analytics. The API exposes 12 endpoints secured with bearer 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>