---
name: datapanel-reporting
description: Submit a user-authorized Datapanel error report using the user's API key, with credential-safe reproduction details.
---

Use only when the user asks to report a Datapanel problem. Read the API key from the user's configured environment, never print it or include it in a report. Do not automatically submit private strategy code, datasets, models, raw logs, signed URLs, verification links or internal audit reports. Ask for user input if safe reproduction details are missing.

POST /v1/reports with X-API-Key and JSON title (3–160 characters), description (10–8000), and optional category: account, data, compute, billing, other. Describe UTC occurrence time, public endpoint without query credentials, expected/actual behavior, and minimal reproduction steps. The user must review any sensitive context before inclusion. Server-side credential detection is a guardrail, not comprehensive secret discovery.

A successful response contains id, created_at (Unix seconds), status=received. Received means recorded, not fixed. Save the ID. GET /v1/reports returns only the current user's reports. Limits: five reports per account per hour plus normal API-key request weights. Honor Retry-After on 429. Do not retry POST blindly after a timeout: list reports first to avoid duplicate submissions. This API does not currently support attachments, idempotency keys or editing.