Feedback
Report a Search1API problem or missing capability without spending credits.
Use POST https://api.search1api.com/feedback when Search1API prevents or complicates your task: an unexpected API response, missing capability, or confusing documentation. This is an API-only integration; it does not add an MCP tool or CLI command.
Authenticate with your existing Search1API API key or OAuth bearer token. Feedback does not reserve or deduct credits, and an account with zero remaining credits can submit it. It does not accept payment credentials as a substitute for account authentication.
Submit a report
curl -X POST https://api.search1api.com/feedback \
-H "Authorization: Bearer $SEARCH1API_KEY" \
-H 'Content-Type: application/json' \
-d '{"message":"I need publication dates to identify recent articles","category":"feature_request"}'Only message is required. Optional fields:
| Field | Meaning | Limit |
|---|---|---|
message | What went wrong or what you need | 1-4000 characters |
intent | The task you were trying to complete | 2000 characters |
category | bug, feature_request, docs, or other (default) | Enum |
request_id | The original problem request's ID, if available | 256 characters |
agent.name | Agent name, self-reported | 128 characters |
agent.model | Model name, self-reported | 128 characters |
Unknown fields are rejected. In particular, callers cannot choose account, source, context, or status. Search1API attaches the authenticated account's opaque identifier and sets the source to api before forwarding to the independent Agent Feedback service. The service's project secret stays on Search1API's server; callers never need it.
Do not include API keys, tokens, passwords, email addresses, personal data, or private user content. This endpoint collects product feedback; it is not an urgent support channel. Do not report every empty search result or retry the same report automatically. Feedback is best effort and should not block your main task.
Response
Successful durable storage returns HTTP 201:
{ "id": "fb_...", "status": "new" }Reports appear in Search1API's project in the Agent Feedback console, where the operator can view them and change their status. This API does not expose feedback lists or status changes to customers.
| HTTP status | Meaning |
|---|---|
400 | Invalid JSON or fields |
401 | Missing or invalid Search1API credential |
403 | Account is disabled or OAuth account is not provisioned |
413 | JSON body exceeds 16 KiB |
415 | Use Content-Type: application/json |
429 | Rate limited; Retry-After: 60 |
500 | Authentication service error |
503 | Feedback configuration, limiter, or downstream service unavailable |
The limit is 10 submissions per authenticated account per minute at each Cloudflare location. Forwarding times out after 5 seconds. A failure never returns a successful receipt or deducts credits. If a timeout happens after storage, delivery is ambiguous: the MVP has no idempotency or automatic retry, so repeated submissions may create duplicates.