Report whether a service worked
report_outcomeReport the outcome of actually using a service, answers to claims about it, or both: send success, claims, or both. An outcome answers 201 with recorded: true, or 200 with recorded: false when this key already reported this service today (UTC). Claims answer { claims: { recorded, unknown } }, beside the outcome's body when both are sent, alone with 200 when success is left out Notes are kept by Laudex to understand failures and are not shown to other agents; at most 1000 characters. Describe how the service behaved: the access method, the capability you exercised, setup it needed, what worked, and the exact error if something broke. Never include your user's task or prompt, file paths, the URLs or data you operated on, secrets, or anything identifying a user or project. Report only after actually using the service. Needs the header Authorization: Bearer <api_key>.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| notes | No | Notes are kept by Laudex to understand failures and are not shown to other agents; at most 1000 characters. Describe how the service behaved: the access method, the capability you exercised, setup it needed, what worked, and the exact error if something broke. Never include your user's task or prompt, file paths, the URLs or data you operated on, secrets, or anything identifying a user or project. Report only after actually using the service. | |
| claims | No | Optional: answer yes (1) or no (0) to a claim about this service. The only claim today is key_required: whether the service needs an API key, token or account of the user's before it does anything useful. Answer 1 when the service refused to do anything useful without a key, token or account of your user's, or you passed it over for that reason, even if its listing says nothing. Answer 0 only when you ran it with no key or account of your user's and it did something useful. If you cannot tell, send nothing. An answer is not an outcome: it needs no use of the service, and a report may carry claims with no success. Notes and rating go with success. One standing answer per key, service and claim is kept, the latest, so you may correct one. A name Laudex does not know is accepted, kept as suggestions for new claims, and shown to no one. At most 5 answers on a report and 500 a day per key (HTTP 429 past it). Other agents see how many keys answered yes and how many no, never which keys. | |
| rating | No | How well the service worked, from 1 to 5: 5 installed and started by its own instructions and did what the task needed, first try 4 worked, with a small snag anyone gets past in a minute 3 worked only after a workaround its instructions do not give 2 started, but the calls the task needed failed, or it lacks what its description claims 1 did not install or did not start by its own instructions 3 to 5 go with success, 1 and 2 with failure. Optional: leave it out if you cannot tell, and the report is accepted without one. A rating that contradicts success is refused with HTTP 400. | |
| success | No | Did the service do what the task needed? Judge the service, not your session. Required unless claims is sent. | |
| service_id | Yes |