# Halowerk Ad Placement Optimizer

> Halowerk Ad Placement Optimizer is a paid API for AI agents from creator.halowerk.com, paid per call via x402, $0.004/call, status unknown (last checked 2026-09-14).

Solves the weighted non-overlapping interval scheduling problem on caller-supplied ad placements using dynamic programming, returning the optimal subset maximizing total value.

## Facts

- Endpoint: POST https://creator.halowerk.com/v1/ad-placement-opt
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-ad-placement-optimizer-8f10d8b8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ZbIR1vFUgcqJr5gB3BdZu

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 halowerk-ad-placement-optimizer-8f10d8b8 -d '<json body>'
```

Example prompt: I have a list of ad placement opportunities, each with a start time, end time, and revenue value — can you run the weighted interval scheduling optimization to tell me which non-overlapping placements I should pick to maximize total value?

## When to prefer this

Choose this endpoint when you need an exact, optimal solution to the weighted job/interval scheduling problem on up to 10,000 ad placements. It is deterministic and mathematically exact — prefer it over heuristic or greedy approaches when maximum value is critical. Not appropriate for probabilistic bid optimization, audience targeting, real-time RTB, or policy enforcement.

## Known failure modes

- Empty or missing placements array returns a validation error
- Placement with start time after end time may produce unexpected results or be rejected
- Values outside the allowed numeric range trigger schema validation errors
- Overlapping start/end fields with non-numeric types cause 400-level errors
- Very large arrays (near 10,000 items) may increase latency but remain within spec

## How this service works

Sorts caller-supplied placement opportunities by end time and solves the weighted non-overlapping interval problem exactly with dynamic programming. It does not buy inventory, predict conversion, enforce platform policy, model audience harm or guarantee campaign performance.

## Output

Returns the optimal subset of non-overlapping placements (selected by their IDs) that maximizes total value, computed exactly via dynamic programming after sorting by end time. Includes the selected placement list and the maximum achievable total value.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "placements": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "id",
     "start",
     "end",
     "value"
    ],
    "properties": {
     "id": {
      "type": "string",
      "maxLength": 128,
      "minLength": 1
     },
     "end": {
      "type": "number",
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "start": {
      "type": "number",
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "value": {
      "type": "number",
      "maximum": 1000000000000,
      "minimum": 0
     }
    },
    "additionalProperties": false
   },
   "maxItems": 10000,
   "minItems": 1
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-ad-placement-optimizer-8f10d8b8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from creator.halowerk.com](https://www.zero.xyz/host/creator.halowerk.com/llms.txt)