Install Jentic One Beta

Connect the work-order to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the work-order, 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%2Fperumdamtkr.com%2Fperumdamtkr" | sh

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%2Fperumdamtkr.com%2Fperumdamtkr" | 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 work-order API.

Create a work order from a customer complaint with region codes such as kd_kelurahan, a priority, and a maps link

Assign a work order to an officer group or a custom list of officers, or let an officer take a ticket

Move an officer's ticket through attendance confirmation, pending with a reason, resume, and done

Track a work order's current status and history by its work order number

GET STARTED

Start building with work-order API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use work-order API for, with concrete tasks.

★ Complaint intake agent through Jentic

An AI agent handling customer complaints for the water utility turns each report into a routed work order. Through Jentic the agent searches for 'create a work order from a complaint', loads the PERUMDAM TKR insertWorkOrder operation with its input schema, and submits the customer, address, region codes, category, and priority, with the bearer token injected at call time by your own Jentic One instance.

Call POST /api/work-orders with customer, alamat, kd_kelurahan, category, priority, and description for a reported leak, then check its progress with GET /api/work-orders/status/closed

Dispatching tickets to field officers

A supervisor (kasie) routes new tickets to the right crew. The API assigns a work order to an officer group with group_id and petugas_ids, or to a custom set of officers with a note, while officers can take a ticket themselves. Officer lists by region (wilayah_id) and active-officer locations help pick who is nearest.

Call GET /api/user/petugas/by-wilayah with a wilayah_id, then call POST /api/work-orders/assign/group with work_order_id, group_id, and petugas_ids for the chosen crew

Field ticket lifecycle

Once assigned, an officer confirms attendance, can mark the ticket pending with a pending_reason, resumes it, and marks it done, each step keyed by detail_work_order_id. Officers attach photos with captured_at, latitude, and longitude to document the repair before the supervisor closes the ticket.

Call POST /api/work-orders/pending-tiket/petugas with detail_work_order_id and pending_reason 'waiting for pipe parts', then later call POST /api/work-orders/resume-tiket/petugas with the same detail_work_order_id

Service performance reporting

Utility managers track backlog and quality across regions. Dashboard operations recap tickets by region and status, count new tickets, chart the status and channel distribution, and download the recaps as PDF or Excel, while reviews rate completed work orders per officer.

Call GET /api/dashboard/by-wilayah/rekap and GET /api/dashboard/total-tiket-new, then summarise open tickets per region

Key Endpoints

94 endpoints — the perumdam tkr work order api runs the complaint-to-field-work ticket system of perumdam tkr, an indonesian regional water utility.

METHOD

PATH

DESCRIPTION

POST

/api/work-orders

Create a work order

GET

/api/work-orders/

List all work orders

POST

/api/work-orders/assign/group

Assign a ticket to an officer group

POST

/api/work-orders/take

Officer takes a ticket

POST

/api/work-orders/pending-tiket/petugas

Put a ticket on pending

GET

/api/users/active-locations

List active officer locations

POST

/api/reviews/work-orders

Rate a work order

GET

/api/dashboard/by-wilayah/rekap

Recap tickets by region

POST

/api/work-orders

Create a work order

GET

/api/work-orders/

List all work orders

POST

/api/work-orders/assign/group

Assign a ticket to an officer group

POST

/api/work-orders/take

Officer takes a ticket

POST

/api/work-orders/pending-tiket/petugas

Put a ticket on pending

GET

/api/users/active-locations

List active officer locations

POST

/api/reviews/work-orders

Rate a work order

GET

/api/dashboard/by-wilayah/rekap

Recap tickets by region

Why Jentic?

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

Setup

Wiring the PERUMDAM TKR Work Order API by hand means obtaining a bearer token through its login or token operation, sending it as an Authorization header, and mapping a spec whose ticket paths embed fixed example ids. Through Jentic you install once, import the API from the API Directory, store the credential once, and your agent calls it.

Permission scoping

This API carries most ticket targets such as work_order_id and detail_work_order_id in the request body, so rules bound which operations your agent may call, not which ticket. You choose the operations it may call, so destructive ones like deleting users, regions, or work groups are not included unless you add them.

Credential isolation

Your PERUMDAM TKR bearer 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 'create a work order from a complaint' or 'assign a ticket to field officers', and Jentic returns the matching PERUMDAM TKR operation with its input schema so the agent calls the right endpoint without reading the Indonesian-language field names cold.

FAQs

Specific to using work-order API through Jentic.

What authentication does the PERUMDAM TKR Work Order API use?

The PERUMDAM TKR Work Order API declares HTTP bearer authentication (bearerAuth) in its OpenAPI spec for its work order, user, and dashboard operations. A few operations are open, including registration, forgot-password, OTP verification, and password reset, and the spec also lists a POST /oauth/token operation that issues tokens from username and password. Through Jentic the bearer token is stored by your own instance and attached at call time.

Can I track a work order by its number with the PERUMDAM TKR Work Order API?

Yes. The getStatusByNoWo operation retrieves the current status and history of a work order using its work order number, shown in the spec with the example WPIII-2025-0002. Other operations list work orders by status, such as closed, rejected, or done for an officer.

What are the rate limits for the PERUMDAM TKR Work Order API?

The OpenAPI spec does not specify rate limits. The spec carries no public documentation link, so confirm current limits with PERUMDAM TKR, the operator of workorder.perumdamtkr.com, before running bulk dashboard downloads.

Is there a PERUMDAM TKR MCP server?

You don't need an MCP server to give your agent the PERUMDAM TKR Work Order API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the work order operations it needs on demand without loading another server's tool definitions into its context.

How do I create a work order through Jentic?

Search Jentic for 'create a work order from a complaint', load the POST /api/work-orders operation, and execute it with fields such as customer, alamat, category, priority, wilayah_id, and the kd_propinsi to kd_kelurahan region codes. The ticket can then be routed with the assign operations. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the PERUMDAM TKR Work Order API?

Yes. Write a rule that allows only POST /api/work-orders and GET /api/work-orders/status/closed, and the agent can file complaint tickets and read closed ones while user deletion, role changes, and dashboard downloads stay out of its allowed set. Every call it makes is logged for review.

Perumdamtkr work-order

AI ReadinessFoundational (C+)59/100

See full scorecard

Community OpenAPI document · agent-readyCRMCustomer Supportbearer94 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Create and route PERUMDAM TKR water-utility work orders from customer complaints, track ticket status by work order number, assign officers, and read dashboard summaries by region and status.

Use for: Create a work order for a customer's water leak complaint, Check the status of work order WPIII-2025-0002, Assign a new ticket to an officer group in a region, List all closed work orders

Not supported: Does not handle water billing, meter readings, or customer payments. Use for routing and tracking PERUMDAM TKR complaint work orders only.

The PERUMDAM TKR Work Order API runs the complaint-to-field-work ticket system of PERUMDAM TKR, an Indonesian regional water utility. It creates work orders from customer complaints with region codes, priority, and a maps link, then moves each ticket through assignment to officer groups or named officers, attendance confirmation, pending and resume, completion, and supervisor close. Field officers upload geotagged photos and report their GPS location, supervisors rate finished work orders, and dashboard operations summarise tickets by region, status, and channel with PDF and Excel downloads.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: C+Signals: 4

91%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

42%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4

70%

Example Density

How richly the API is illustrated with examples.

98%

Example Validity

Percentage of examples that conform to their schemas.

25%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

16%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

44%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1

86%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: BSignals: 1

67%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the work-order to your agent

Capabilities

Start building with work-order API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Perumdamtkr work-order

Jentic AI Readiness Score

work-order

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness