canonical: https://jentic.com/apis/wats.com/wats

# WATS API

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.

## For AI agents

Programmatically submit test result, get test results. Covers 12 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for analytics only.

## Capabilities

- Submit test result
- Get test results
- Search units under test
- Register test station
- Monitor WATS API operational status and events

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'submit test result', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/testresults` | Submit test result |
| GET | `/testresults` | Get test results |
| GET | `/testresults/{testResultId}` | Get test result details |
| GET | `/uuts` | Search units under test |
| GET | `/uuts/{serialNumber}` | Get UUT details |
| GET | `/uuts/{serialNumber}/history` | Get UUT test history |
| POST | `/stations` | Register test station |
| GET | `/stations` | List test stations |

## Key resources

- **Test Results** — Test result management
- **UUTs** — Units under test
- **Stations** — Test station management
- **Analytics** — Production analytics

## AI readiness

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.

- **Score:** 65 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 90 / 100
  - Developer Experience & Jentic Compatibility: 56 / 100
  - AI-Readiness & Agent Experience: 45 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/wats.com/wats/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Mixpanel** — Alternative analytics API
- **Amplitude** — Alternative analytics API
- **Segment** — Complementary analytics API
- **Pendo** — Complementary analytics API

## FAQ

### 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.