feedback
participation
free
free

Send product feedback from an agent session

Closed-vocab notes for agents after a Locus session: what helped, what did not, a catalog or schema UX gap, or an improvement idea. Set target (or tool or toolName) to the exact catalog name; summary allows up to 1000 characters. No place, person, wallet, or payment fields. POST /feedback. Product signal, not a record lookup. Direct flat-body route for this one free resource; no API key, payment, or catalog wrapper. Return only the cited bounded evidence described here; this route never produces a paid brief or full report.

post/api/locus_agent_feedback

Request

  • Base URL: https://api.locus.report
  • URL: https://api.locus.report/api/locus_agent_feedback
  • Auth: none required

Request body

kind'helpful' | 'not_helpful' | 'ux_gap' | 'schema_issue' | 'coverage_gap' | 'docs_issue' | 'idea' required

What this note is: helpful, not_helpful, ux_gap, schema_issue, coverage_gap, docs_issue, or idea.

targetstring

Exact catalog tool, surface, or skill this note is about. Use locus-before-you-sign, locus-pfas-occurrence, or llms.txt. Do not put the tool name only in summary.

toolstring

Alias for target. Exact catalog name of the tool this note is about.

toolNamestring

Alias for target. Exact catalog name of the tool this note is about.

summarystring required

One sentence about what helped, what failed, or the gap. Max 1000 characters. No address, person, or wallet. Set target/tool for the related catalog name.

helpfulstring[]

Short bullets of what worked.

unhelpfulstring[]

Short bullets of friction, missing schema, or confusing copy.

ideastring

Optional improvement the next agent should see in catalogs or the skill.

skillVersionstring

Optional installed skill version, for example 1.20.0.

clientstring

Optional harness name such as claude, grok, or codex. Not a user id.

Response

Free cited evidence response.

object required

Changes

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