account

Submit platform feedback only from an interactive MCP agent flow after showing the user the exact proposed summary an...

Submit platform feedback only from an interactive MCP agent flow after showing the user the exact proposed summary and details, asking first, and receiving explicit approval. Open search({ entity: "guide:platform_friction" }) first for the approval flow and content guidance. Each account may create at most 20 submissions per rolling 24 hours; call metaPlatformFeedbackList first and check submissions_remaining (and next_slot_at when at the cap) before asking the user to approve multiple submissions. After submit, use metaPlatformFeedbackGet with the returned feedback_id (or metaPlatformFeedbackList) to check status — including open, triaged, resolved, and dismissed — without a full account export. The exact approved summary and details plus the account user id, username, and email may be delivered immediately to deployment admins through admin-configured notifications. Copies already delivered outside Kody may remain after Kody account deletion under the deployment operator’s retention and deletion controls. Non-interactive package code and package apps cannot submit. Do not include secrets or unrelated private content.

Org permission: none (touches no org data).

post/v1/account/feedback

Request

  • Base URL: https://api.kody.codes
  • URL: https://api.kody.codes/v1/account/feedback
  • Auth: HTTP bearer

Request body

category'friction' | 'bug' | 'experience' | 'suggestion' | 'cancellation' | 'other' required

Stable feedback category: "bug" for reproducible defects, "friction" for capability/guide/package text that caused a wrong turn, "experience" for a poor overall experience, "suggestion" for a problem-first improvement idea, "cancellation" for why the user is ending a paid subscription, "other" when nothing fits.

summarystring required

Specific, scannable summary naming the affected area and symptom or need (1–200 characters); admins triage from this line alone, so avoid vague summaries like "search is broken".

detailsstring required

Feedback details (1–8000 characters), one issue per submission: goal context, exact capability or package names, minimal reproduction steps, expected vs actual behavior, verbatim error text, frequency, impact, and any workaround. Do not include secrets or unrelated private content.

user_confirmedtrue required

Must be true only after the agent shows the exact proposed summary and details and the user explicitly approves sending them, with the account user id, username, and email, immediately to deployment admins through admin-configured notifications, after being told that copies already delivered outside Kody may remain after Kody account deletion under the deployment operator’s retention and deletion controls.

Response

Success.

feedback_idstring required

Submitted feedback id. Pass to metaPlatformFeedbackGet to check status later, or use metaPlatformFeedbackList to browse the signed-in user's submissions.

status'open' required
created_atstring required

Changes

No recorded changes to this operation across all 2 revisions of this API.