Skip to main content
POST
Report a problem
  • Report each problem once, when it happens: something slow, an unexpected error, a confusing description or answer, a wrong result, or a design you had to work around. Not your own input mistakes, or website problems Pomerado explained.
  • To change one tool, such as adding a filter, input or output, use POST /v1/tools/{id}/changes instead.
  • Never include passwords, codes, tokens, card numbers, personal details, page content or your users’ data.
  • Pomerado attaches who sent the report and from where. It links the related job, tool and integration only when you can read them.
  • The same report from you within a day counts again (status merged). Your account can send 50 reports an hour and 200 a day, across its members and clients; past that it answers report_limit_reached, and you carry on without retrying.
  • Reports are kept 90 days and only help the Pomerado team improve Pomerado. They are not a support channel: if it is urgent, the user can email founders@pomerado.ai (the receipt’s message also gives the Discord invite). Ask the user before sending any email; never email on your own.
  • Callers: an API key, an integration’s API key, an MCP OAuth token or a Dashboard session.
  • Permission: any signed-in member, for their own records.
  • Effect: Creates or changes something.
  • Errors: report_limit_reached, sign_in_required, and the errors any request can get.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
summary
string
required

One sentence saying what happened, 10 to 200 characters.

Required string length: 10 - 200
category
enum<string>
required

slow: a tool or job took too long. error: an error you didn't expect, or one that didn't say how to fix it. confusing: a description, input or answer that was unclear. workaround: you had to work around a design, with extra calls, guessing or retrying. wrong_result: a result was wrong. missing_capability: Pomerado can't do something you needed. worked_well: something worked notably well. other: anything else.

Available options:
slow,
error,
confusing,
workaround,
wrong_result,
missing_capability,
worked_well,
other
task_outcome
enum<string>

How your task ended: completed, completed_with_workaround, partially_completed or blocked.

Available options:
completed,
completed_with_workaround,
partially_completed,
blocked
details
string

What you tried and what happened, up to 4,000 characters, quoting exact tool names, error codes and parameter names.

Maximum string length: 4000
suggested_improvement
string

The one change that would have helped, up to 1,000 characters.

Maximum string length: 1000
waited_seconds
integer

For slow: about how many seconds it took, 0 to 86,400.

Required range: 0 <= x <= 86400

What the report is about. Pomerado links only the IDs you can read.

Response

The stored report

report_id
string
required

The report's ID: rpt_ and 32 hex digits

status
enum<string>
required

recorded: a new report. merged: you sent the same report within the last day, so it counted again

Available options:
recorded,
merged
severity
enum<string>
required

Derived by Pomerado: high for a blocked task; medium for a partial one, a workaround or an error on a job that failed on Pomerado's side; none for worked_well; otherwise low

Available options:
high,
medium,
low,
none
linked
object
required

The related IDs Pomerado kept; one you can't read is left out

message
string
required

What to do next