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

# LottoLens PH Public PCSO Data API

The LottoLens PH Public PCSO Data API provides read-only access to a fixed snapshot of Philippine PCSO draw results. It returns snapshot metadata, the full set of historical draw-result rows, and the normal draw schedule for the covered games. The immutable JSON files are served over a CDN, so an agent can look up past results or the draw calendar without scraping or maintaining its own dataset.

## For AI agents

Read a fixed snapshot of Philippine PCSO draw results, the draw schedule, and snapshot metadata.

## Scope

Reads a fixed snapshot of PCSO draw results, schedule, and metadata; it does not provide live draws, place bets, or write any data.

## Capabilities

- Read snapshot and dataset metadata
- Retrieve the full set of historical draw-result rows
- Retrieve the normal draw schedule for the covered games
- Check the snapshot version before reading data
- Consume static, cacheable JSON files

## Use cases

### Read historical draw results

Answering questions about past PCSO draws needs the full result history. The API returns the complete set of historical draw-result rows as a single static JSON file, so an application can search or summarize past outcomes. Because the file is a fixed snapshot, results are stable between updates.

Example prompt: Retrieve the historical results snapshot and return the requested draws.

### Get the draw schedule

Knowing when draws happen helps plan reminders and displays. The API returns the normal draw days, times, and result formats for the covered games, so an application can show an accurate calendar. The schedule is served as its own static JSON file.

Example prompt: Retrieve the normal draw schedule and return the days and times.

### Check the snapshot version

Static data should be read against a known version. The API returns metadata describing the current snapshot, letting an application detect when the dataset has changed before re-reading the larger result file. This keeps a cache accurate without refetching everything.

Example prompt: Read the snapshot metadata and return the current version.

### Agent-driven results lookup

An AI agent can answer questions about PCSO draws for a user without a developer wiring each call. Through Jentic the agent matches an intent such as 'what were the recent draw results' to the results operation, runs it, and returns the data. The files are public and read-only, so no credential is involved.

Example prompt: Retrieve the results snapshot and return the draws the user asked about.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/v1/results.json` | Retrieve all historical draw-result rows in the fixed snapshot. |
| GET | `/api/v1/schedule.json` | Retrieve the normal draw days, times, and result formats. |
| GET | `/api/v1/metadata.json` | Retrieve API and fixed-snapshot metadata. |

## Key resources

- **Results** — The full set of historical PCSO draw-result rows.
- **Schedule** — Normal draw days, times, and result formats per game.
- **Metadata** — Snapshot version and dataset metadata.

## Why Jentic

- **Setup:** Reading LottoLens yourself means fetching each static JSON file, caching it, and checking the metadata for changes. With Jentic you install once, import LottoLens from the API Directory, and call the operations by intent.
- **Permission scoping:** Jentic lets you grant your agent only the operations it needs, such as reading results and the schedule, and enforces that on every call.
- **Credential handling:** LottoLens serves public, read-only JSON and requires no credential, so Jentic One calls the endpoints directly with nothing to store.
- **Discovery method:** Agents find LottoLens through Jentic's intent search, matching a request like 'get the latest PCSO draw results' to the right operation without hardcoded endpoints.

## Related APIs

- **TheSportsDB** — Free sports data across leagues and events.
- **balldontlie** — Free structured sports statistics data.
- **PandaScore** — Esports results, odds, and live data.

## FAQ

### What can an AI agent do with the LottoLens PCSO Data API through Jentic?

An agent can read historical PCSO draw results, the normal draw schedule, and snapshot metadata. Through Jentic the agent matches an intent to the right operation and runs it against the public JSON files.

### Does the LottoLens PCSO Data API require authentication?

No. The JSON files are public and read-only, so no credential is required to read them. Jentic One calls the endpoints directly with nothing to configure for access.

### Is the data live or a fixed snapshot?

The data is a fixed, independently compiled snapshot served as immutable JSON files over a CDN. Clients should cache responses and read the metadata file to detect when a new snapshot is published.

### Does the LottoLens PCSO Data API document rate limits?

The OpenAPI specification does not state rate limits; the files are static and served through GitHub Pages with CDN caching. Cache responses on your side and re-read only when the snapshot metadata changes.

### Can I control which LottoLens operations my agent can call?

Yes. Jentic lets you allow only the operations your agent needs, for example reading results and the schedule. Your Jentic One instance enforces that boundary on every call.