# The Stall — Code Test Detector

> The Stall — Code Test Detector is a paid API for AI agents from the-stall.intuitek.ai, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Analyzes code or text properties to detect whether content was written as a test, stub, placeholder, or boilerplate rather than production code

## Facts

- Endpoint: GET https://the-stall.intuitek.ai/cap/code-test-detector
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/the-stall-code-test-detector-07831e72
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2jYIsnGiv_O-KyOrHQvRO

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability the-stall-code-test-detector-07831e72
```

Example prompt: Can you check whether this code snippet is a test stub or placeholder rather than real production code? Here are the properties: it's a short function with hardcoded return values and no real logic.

## When to prefer this

Use this endpoint when you need a lightweight, pay-per-call (no API key) classifier to determine if a code snippet or set of code properties represents test/stub/boilerplate versus real production code — especially useful in automated code review pipelines or submission validation workflows where you want to filter out test submissions.

## Known failure modes

- Empty or missing properties field returns error
- Malformed input schema causes 400-level response
- Ambiguous code properties may yield low-confidence classification
- Payment failure on Base mainnet results in 402 response and no data returned
- Service unavailability returns 5xx error

## How this service works

Detects testing frameworks and test coverage presence in a code snippet or GitHub repository. For code snippets: identifies test functions, assertions, mocks, fixtures, and frameworks (Jest, pytest, go test, JUnit, RSpec, etc.). For GitHub repos: counts test files vs source files, surfaces config files, and gives a coverage verdict. No code execution — pure static analysis.

## Output

Returns a classification indicating whether the submitted code or code properties represent a test, stub, placeholder, or boilerplate — likely including a label and confidence signal indicating production vs. test status.

## Example request

```json
{
 "code": "function testExample() {\n  return 'test';\n}"
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/the-stall-code-test-detector-07831e72/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from the-stall.intuitek.ai](https://www.zero.xyz/host/the-stall.intuitek.ai/llms.txt)
