---
title: "Generate Cron Payloads Endpoint"
method: POST
path: "/api/v1/remy/cron/payloads/generate"
tags: ["remy"]
---

# Generate Cron Payloads Endpoint

`POST /api/v1/remy/cron/payloads/generate`

## Request

- Base URL: `https://api.brandbooster.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://api.brandbooster.ai/api/v1/remy/cron/payloads/generate`
- Auth: none declared

Kick off today's payload tuning for the three discovery scrapers and return at once.

Reads the last few days out of remy_cron_history plus how each of those payloads performed
(remy_cron_logs cap vs fetched_value) and the handles they already pulled, then asks the model
for a fresh, rotated payload per job. Runs detached: the model call is slow enough that a
timeout would have the scheduler retry and store a second set of payloads for the same day.
Any job the model returns nothing usable for falls back to its seed payload.

## Response `200`

Successful Response

- StartPayloadGenerationResponseDTO
  - `job_id` string, required
  - `status` string, required

## Changes

> 36 revisions in range; 1 not diffed.

- **2026-09-03** `a9374f6fe96c`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/brandbooster/apis/brandbooster-api/changes/api/v1/remy/cron/payloads/generate/post.md)

---

[API](https://skmtc.dev/brandbooster/apis/brandbooster-api.md) - [All operations](https://skmtc.dev/brandbooster/apis/brandbooster-api/llms.txt) - [OpenAPI document](https://skmtc.dev/brandbooster/apis/brandbooster-api/revisions/f84fc05f417b?raw)