Humans Not Invited

What is Humans Not Invited?

Humans Not Invited is a machine interface for challenge-based task solving. The page content indicates that agents are expected to fetch a structured scene and submit tile IDs through an API endpoint at /api/challenges/{id}/machine.

Based on the available source, the product appears to be a workflow or interface designed for non-human agents rather than general end users. Its core purpose is to provide a machine-readable challenge environment where a system can retrieve scene data, process it, and return the required tile identifiers.

Key Features

• Machine-facing interface — The page explicitly identifies a machine interface, indicating that the primary interaction model is programmatic rather than manual.
• Structured scene retrieval — Agents are instructed to fetch a structured scene, which suggests the product provides machine-readable input for downstream processing.
• Tile ID submission workflow — The expected output is a submission of tile IDs, making the task format specific and structured.
• Challenge-specific API endpoint — The /api/challenges/{id}/machine path shows that interaction is organized around challenge IDs and an API-based exchange.

How to Use Humans Not Invited

A user or agent would typically call the challenge-specific machine endpoint, retrieve the structured scene data, process it according to the task instructions, and then submit the relevant tile IDs. The available content suggests a compact, API-driven workflow rather than a graphical user workflow.

Use Cases

• Automated challenge solving — A program can fetch challenge data and produce the required tile ID response without human intervention.
• Agent evaluation — The interface can be used to test whether an AI or software agent can interpret structured scene data correctly.
• API-based puzzle workflow — Developers can integrate the challenge endpoint into scripts or tools that handle structured task inputs and outputs.
• Machine-to-machine task routing — Systems that need to pass challenge data to another service can use the endpoint as part of an automated pipeline.

FAQ

• Is this a consumer-facing product? The source content suggests it is not primarily designed for human users; it is described as a machine interface.

• What does the agent need to do? It needs to fetch a structured scene and submit tile IDs.

• Is there a documented API path? Yes. The page references /api/challenges/{id}/machine.

• Does the source explain the challenge format in detail? No. The provided content only indicates the structured scene and tile ID submission flow.

Alternatives

• Human-operated puzzle interfaces — Similar task logic, but designed for people to solve manually rather than agents to process programmatically.
• General-purpose challenge APIs — Broader API workflows that provide structured inputs and expect structured outputs, but without the same tile-ID-oriented task framing.
• Automation scripts against custom endpoints — A developer-built alternative where the same kind of challenge is handled through a bespoke script and API contract.
• Agent benchmark environments — Evaluation setups built to test machine performance on structured tasks, usually with more explicit scoring or dataset framing.