Daily Logic Puzzle API & Archive - PUZRU
Pricing
Pay per usage
Daily Logic Puzzle API & Archive - PUZRU
Fetch two verified 6×6 cage-sum logic puzzles every day or retrieve any completed PUZRU World round by ID. Get clean JSON for websites, apps, widgets, classrooms, and automations without scraping, browser automation, or operating your own puzzle generator.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Puzru Team
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
Daily Logic Puzzle API & Archive — PUZRU
Fetch verified completed 6×6 cage-sum logic puzzles as structured JSON.
This Actor provides a thin, read-only integration over PUZRU's canonical puzzle distribution service. It does not scrape websites, run browser automation, or generate puzzles locally.
What this Actor does
Use the Actor to retrieve:
- today's two-puzzle Daily set
- one completed puzzle by round ID
- 6×6 puzzle structure
- givens
- arithmetic cages and cage sums
- difficulty metadata
- completed round metadata
- attribution and puzzle URLs
The puzzle format combines Latin-grid deduction with arithmetic cage sums, making it useful for logic puzzle, math puzzle, number puzzle, and grid puzzle applications.
Daily mode
Choose daily to retrieve today's Daily set.
{"mode": "daily"}
The result contains two completed puzzles:
warmup— the easier Daily puzzlechallenge— the harder Daily puzzle
Each run stores one canonical response object in the Actor's default dataset.
Completed round mode
Choose round and provide a positive completed round ID.
{"mode": "round","roundId": 21}
The Actor returns the immutable completed puzzle associated with that round.
If the requested round does not exist or is not available, the run fails rather than returning fabricated or partial puzzle data.
Input
mode
Type: string
Available values:
dailyround
Default:
daily
roundId
Type: integer
Required when:
mode = round
The value must be a positive completed round ID.
Output
The Actor stores one JSON item in its default dataset.
A Daily response can include fields such as:
okapiVersionprofiledailysetroundIdpuzzlecontributorsdiscovererqualityurlsattribution
A completed round response can include:
okapiVersionprofileroundIddifficultypuzzlecontributorsdiscovererqualityurlsattribution
Puzzle structure
Puzzle data can contain:
size
The PUZRU puzzle grid size.
Current distributed puzzles use a 6×6 grid.
givens
Pre-filled cell values indexed by cell position.
cages
Arithmetic cage definitions.
Each cage contains:
{"cells": [7, 8, 9, 14],"sum": 15}
Read-only by design
The Actor distributes completed puzzle data only.
It does not expose:
- canonical puzzle solutions
- live competitive state
- player sessions
- authentication credentials
- claim tokens
- account information
- puzzle-generation internals
- mutable gameplay operations
No scraping or browser automation
This Actor does not parse webpages or automate a browser.
It retrieves structured puzzle data directly from the canonical PUZRU distribution service and stores the response in an Apify dataset.
This makes it suitable for workflows that need predictable structured JSON without DOM parsing or browser dependencies.
Example use cases
The Actor can be used for:
- daily logic puzzle workflows
- puzzle widgets
- websites and apps
- education and classroom tools
- automation workflows
- structured puzzle datasets
- prototype logic games
- math and grid puzzle experiments
- agent and data-pipeline integrations
Reliability
Completed archive puzzles are immutable.
The Actor validates the upstream response before writing it to the dataset. Unexpected or unavailable responses cause the run to fail instead of producing misleading output.
Network requests also use a bounded timeout.
Security and privacy
The Actor uses a private server-to-server marketplace credential to identify trusted Apify traffic.
The credential is configured as a secret environment variable and is not part of Actor input or output.
The Actor does not require end users to provide:
- PUZRU accounts
- PUZRU API keys
- passwords
- authentication cookies
- personal information
Storage
Each successful run writes exactly one canonical API response to the default Apify dataset.
The dataset can then be consumed through Apify's standard dataset APIs and export formats.
