Can I edit or delete comments with the Huddlekit API?

No. The spec states that status is the only field PATCH /comments/{id} can change: sending text returns 400, and there is no delete operation for comments. You can create comments with POST /comments and move them between open, in-review, in-progress, and resolved.

What are the rate limits for the Huddlekit API?

Huddlekit's OpenAPI spec states that limits are counted per API key, per endpoint group, and separately for reads and writes: up to 200 reads and 30 writes a minute. Going over returns 429 with a Retry-After header in seconds, and refused calls count toward the limit too.

Does the Huddlekit API need a paid plan?

According to the spec, every call except DELETE /hooks/{id} requires an active or trialing Team subscription, and a past-due payment fails the check with a 403 that lists requiredPlans. Deleting a webhook is deliberately not plan-gated so automations can always be switched off.

How do I resolve a Huddlekit comment through Jentic?

Search Jentic for 'resolve a review comment' to get PATCH /comments/{id}, then call it with the comment id and status resolved, passing surface when the comment is on a web app or document. To run it on your own infrastructure, install Jentic One from its GitHub repo, add the Huddlekit API from the directory, and store your key once.

Is there a Huddlekit MCP server?

You don't need an MCP server to give your agent Huddlekit. Jentic connects it directly from the API Directory: import it, store your workspace key once, and your agent calls the operations you allow, without another server's tool definitions sitting in its context.

Can I limit what my agent is allowed to do with the Huddlekit API?

Yes. For example, write a rule that allows only GET /projects, GET /comments, and PATCH /comments/{id}, so the agent can read feedback and change comment statuses but cannot post new comments or create webhook subscriptions. Every call it makes is logged by your Jentic One instance.