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

# Enigmasuite Tlajo API

The Tlajo API returns municipal service report data for Tlajomulco, covering citizen water-truck (pipa) delivery requests and public sanitation (Aseo Publico) activity. One operation lists water-truck request reports with pagination controls, and the other returns a summary of public sanitation reports, both as JSON. It is a read-only reporting surface intended for dashboards and civic monitoring rather than for filing requests or dispatching service. Access is authenticated with a bearer JWT.

## For AI agents

Read municipal service report data for Tlajomulco: list paginated water-truck (pipa) request reports and retrieve the public sanitation report summary as JSON.

## Scope

Does not handle water-truck dispatch, filing new service requests, payments, or citizen account management. Use for reading Tlajomulco water-request and public-sanitation report data only.

## Capabilities

- Retrieve paginated water-truck (pipa) request reports via `/api/reports/water-truck-requests/{limit}/{page}`
- Page through large water-request report sets using the {limit} and {page} path parameters
- Read a summary of public sanitation (Aseo Publico) reports via `/api/reports/reports-public-sanitation/summary`

## Use cases

### AI agent civic reporting assistant

An AI assistant pulls Tlajomulco municipal report data on demand through Jentic, so a city analyst can ask a question in natural language and get back the current water-truck request figures or the public sanitation summary without touching the raw endpoints. Jentic injects the bearer token at call time, so the agent never holds the credential.

Example prompt: Search Jentic for 'get the public sanitation report summary', call GET `/api/reports/reports-public-sanitation/summary`, and summarise the returned figures for the analyst

### Water-truck request monitoring

Operations staff track the stream of citizen water-truck (pipa) delivery requests to spot demand spikes across neighbourhoods. The Tlajo API returns these requests as paginated report rows, so a monitoring job can walk the pages and keep a rolling view current. Because the endpoint is read-only, it is safe to poll on a schedule.

Example prompt: Call GET `/api/reports/water-truck-requests/{limit}/{page}` with a page size, then increment the page path parameter to walk through every water-truck request report row

### Public sanitation summary dashboard

A civic dashboard shows how public sanitation (Aseo Publico) work is trending for the municipality. The Tlajo API exposes a single summary operation that returns the aggregated sanitation figures, which a dashboard backend can fetch and cache. The read-only shape keeps the integration simple and side-effect-free.

Example prompt: Call GET `/api/reports/reports-public-sanitation/summary` and render the returned sanitation summary figures on a dashboard tile

## Key resources

- **Water-truck request reports** — Paginated reports of citizen water-truck (pipa) delivery requests
- **Public sanitation reports** — Summary figures for public sanitation (Aseo Publico) activity

## 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: 74 / 100
  - Developer Experience & Jentic Compatibility: 85 / 100
  - AI-Readiness & Agent Experience: 44 / 100
  - Agent Usability: 94 / 100
  - Security: 75 / 100
  - AI Discoverability: 50 / 100
- **View full report:** https://jentic.com/apis/enigmasuite.com/enigmasuite/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 Tlajo API by hand means obtaining and refreshing a bearer JWT, choosing the right host, and paging the water-request report yourself. Through Jentic you install once, import Tlajo from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Tlajo exposes two read operations, so a rule can allow your agent just the report reads it needs: the water-truck request report, the public-sanitation summary, or both. You choose the operations it may call, and because both are read-only there is nothing the agent can change.
- **Credential handling:** Your Tlajo 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.
- **Discovery method:** Agents search Jentic by intent such as 'list water-truck requests' or 'get the public sanitation summary', and Jentic returns the matching Tlajo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **data.gov.uk CKAN API** — Open government data catalogue API serving public-sector datasets, a broader civic-data source than a single municipality's reports
- **MojePanstwo API** — Public-institution and civic data API for Poland, another source of government report and registry data
- **Licitalab** — Public procurement and tender data for Chile, pairing government-sector data with municipal service reporting

## FAQ

### What authentication does the Tlajo API use?

The Tlajo API authenticates with a bearer token in JWT format, per its OpenAPI spec. When you call it through Jentic, the token is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's prompt, logs, or context.

### Can I read water-truck request reports with the Tlajo API?

Yes. Call GET `/api/reports/water-truck-requests/{limit}/{page}`, passing a page size as {limit} and a page number as {page}, and the API returns that page of citizen water-truck (pipa) delivery request report rows. Increment the page path parameter to walk through the full set.

### Can the Tlajo API return a public sanitation summary?

Yes. Call GET `/api/reports/reports-public-sanitation/summary` and the API returns the aggregated public sanitation (Aseo Publico) report figures as JSON, which a dashboard or agent can read directly. It is a read-only operation with no parameters to set.

### What are the rate limits for the Tlajo API?

The OpenAPI spec does not specify rate limits for the Tlajo API. Since both operations are read-only, poll them on a sensible schedule and have your agent retry with backoff when the API signals that it is being throttled.

### How do I read the sanitation summary through Jentic?

Search Jentic for 'get the public sanitation report summary' to load the Tlajo operation with its input schema, then call GET `/api/reports/reports-public-sanitation/summary` and work with the returned figures. 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 Tlajo API?

Yes. Because you run Jentic One yourself, you decide which Tlajo operations the agent may call. You can allow only the public-sanitation summary and leave out the water-truck request report, or allow both, and because the two operations are read-only the agent can read municipal report data without changing anything, with every call logged.