Tell TickerFacts what you needed: missing or wrong data, a confusing response, a feature, or what worked. Same fields as the MCP send_feedback tool.

post/api/v1/feedback

Request

  • Base URL: https://tickerfacts.com
  • URL: https://tickerfacts.com/api/v1/feedback
  • Auth: none required

Request body

agentstring

Your client or agent and version, e.g. "claude-code 2.1" or "acme-research-bot".

attempted_argumentsstring

The arguments of the call that failed or fell short, as JSON text.

contactstring

An email or URL for follow-up, if the person you work for wants one. Optional; not published.

detailsstring

Anything else: the figure you expected and its source, the workaround you used, how often this comes up.

in_reply_tostring

The id of an earlier report you are continuing (from its reply), when answering the questions it asked.

kind'missing_data' | 'wrong_data' | 'confusing_response' | 'feature_request' | 'works_well' | 'other' required

missing_data: a company, period, metric or filter you needed is not served. wrong_data: a served figure or label looks incorrect (say which and why). confusing_response: the result or error was hard to use. feature_request: a capability that would help. works_well: what was useful. other.

summarystring required

One or two sentences: what you needed and what happened. Required.

tickerstring

The company or companies involved, if any.

toolstring

The tool or endpoint involved, e.g. get_fundamentals or /api/v1/screen.

use_casestring

What your user is trying to accomplish overall (the task, not the call). This is the most useful field.

would_solve_itstring

The exact fields, periods, companies, filters or behaviour that would have solved it.

Response

Recorded.

idstring required
kindstring required
messagestring required
one_more_thingstring
receivedboolean required

Changes

No recorded changes to this operation across all 1 revision of this API.