Feedbucket App Feedbucket REST API
45
AI ReadinessFoundational (D)45/100
Official vendor OpenAPI document · agent-readyDeveloper ToolsProject Managementbearer15 EndpointsREST
For Agents
List and triage website feedback and bug reports across projects, comment on them, and read the console log captured with each bug. Create, update, and archive projects and their feedback widgets.
Use for: List new feedback for one of my projects, Update the status of a feedback item to resolved, Add a comment to a feedback item for my teammate, Get the console log captured with a bug report
Not supported: Does not handle session replay, uptime monitoring, or analytics dashboards. Use for collecting and triaging website feedback and bug reports only.
The Feedbucket REST API manages the website feedback and bug reports your team collects through the Feedbucket widget. It lists, reads, and updates feedback items on a project, threads comments on each one, and returns the browser console log captured alongside a bug so a developer can reproduce it. Projects can be created, updated, and archived with their widget settings, and a presigned upload URL lets you attach screenshots and recordings to a feedback item.
Install Jentic One Beta
Connect the Feedbucket REST API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Feedbucket REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffeedbucket.app%2Ffeedbucket" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffeedbucket.app%2Ffeedbucket" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Feedbucket REST API.
Collect and list website feedback and bug reports as feedback items on a project
Filter feedback and update an item, including its status and resolution
Read the browser console log captured with a bug report to reproduce it
Add and edit comments on a feedback item to discuss it with your team
Create, update, and archive projects, each with its own feedback widget settings
Mint a presigned upload URL to attach screenshots and recordings to feedback
Use Cases
Patterns agents use Feedbucket REST API for, with concrete tasks.
★ Agent triage of website feedback through Jentic
An AI agent polls a project for new feedback, reads each item with its captured console log, sets a status, and leaves a comment summarising the likely cause. Because every item carries the widget-captured context, the agent can route a reproducible bug to engineering and a vague note back to the reporter without a person opening the dashboard first.
List open feedback for a project, read the console log on the newest bug, and update that item's status to resolved with a comment
Sync feedback into an engineering workflow
Teams want website feedback to become tracked work. The API lists feedback per project and exposes each item's details and comments, so a connector can mirror new bugs into an issue tracker and write the issue link back as a comment, keeping the reporter and the developer on the same thread.
Fetch feedback created since yesterday for a project and add a comment on each one linking the mirrored issue
Reproduce bugs from captured console logs
A website bug report is only useful if a developer can reproduce it. Feedbucket captures the browser console log with the feedback, and the API serves that log on demand, so a debugging assistant can pull the errors, correlate them with the described steps, and attach its findings as a comment before a human picks it up.
Retrieve the console log for a specific feedback item and summarise the errors it contains in a new comment
Project and widget setup automation
Agencies onboard new client sites repeatedly. The API creates a project, updates its widget settings such as visibility and enabled features, and archives it when the engagement ends, so onboarding and offboarding a site becomes a scripted step instead of manual dashboard work.
Create a project for a new client site, set its visibility to members only, then archive a completed project
Key Endpoints
15 endpoints — the feedbucket rest api manages the website feedback and bug reports your team collects through the feedbucket widget.
METHOD
PATH
DESCRIPTION
GET
/projects
List projects
POST
/projects
Create a project
GET
/projects/{project}/feedback
List feedback for a project
GET
/projects/{project}/feedback/{feedback}
Get a feedback item
PATCH
/projects/{project}/feedback/{feedback}
Update a feedback item
GET
/projects/{project}/feedback/{feedback}/console-log
Get the console log captured with a bug
POST
/projects/{project}/feedback/{feedback}/comments
Add a comment to a feedback item
POST
/attachments
Mint a presigned upload URL for an attachment
GET
/projects
List projects
POST
/projects
Create a project
GET
/projects/{project}/feedback
List feedback for a project
GET
/projects/{project}/feedback/{feedback}
Get a feedback item
PATCH
/projects/{project}/feedback/{feedback}
Update a feedback item
GET
/projects/{project}/feedback/{feedback}/console-log
Get the console log captured with a bug
POST
/projects/{project}/feedback/{feedback}/comments
Add a comment to a feedback item
POST
/attachments
Mint a presigned upload URL for an attachment
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
F
Feedbucket REST API
- Foundational (D)45/100
93
Foundational Compliance64
Developer Experience & Jentic Compatibility20
AI-Readiness & Agent Experience94
Agent Usability60
Security63
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
93
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
75%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
64
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: BSignals: 4
6%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
20
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
21%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
60%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
63
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: BSignals: 1
63%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Feedbucket by hand means creating a personal access token with the api:use scope, sending it as a Bearer token, and handling its team-scoped requests and rate limiting yourself. Through Jentic you install once, import it from the API Directory, store the token once, and your agent calls it.
Permission scoping
Feedbucket puts the project id in the URL path (/projects/{project}/...), so a rule can pin your agent to one project: it reads and triages that project's feedback and nothing else. You choose the operations it may call, so project deletion stays out unless you add it.
Credential isolation
Your Feedbucket access token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list website feedback' or 'add a comment to a bug', and Jentic returns the matching Feedbucket operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Feedbucket REST API through Jentic.
What authentication does the Feedbucket REST API use?
It authenticates every request with a personal access token sent as a Bearer token in the Authorization header, per its OpenAPI spec. The token must carry the api:use scope, and requests run as that user within their current team.
Can I read the browser console log from a bug report with the Feedbucket API?
Yes. Each bug captured through the widget stores the browser console log, and the API serves it for a given feedback item so a developer or an agent can see the errors that fired when the report was filed. It is read-only and sits alongside the feedback item's details and comments.
What are the rate limits for the Feedbucket REST API?
Feedbucket limits the API to 60 requests per minute per user, as stated in its API documentation. Plan larger feedback syncs around that ceiling and watch for a 429 response when you approach it.
Is there a Feedbucket MCP server?
Yes, Feedbucket offers an official MCP server. You can also connect Feedbucket directly through Jentic: your agent gets the full 15-endpoint surface without loading another server's tool definitions into its context, your token is injected at call time by your self-hosted instance instead of living in an MCP config, and your rules decide which operations the agent may call.
Can I limit what my agent is allowed to do with the Feedbucket API?
Yes. Write a rule that allows the feedback-list, feedback-read, and comment operations under one project id, so the agent can triage and reply to feedback for that site while project creation and deletion stay off the list. Every call it makes is recorded in your Jentic One audit log.
How do I triage website feedback with the Feedbucket API through Jentic?
Search Jentic for 'list website feedback', add the Feedbucket API from the directory, and store your access token once; your agent then lists a project's feedback, reads the console log on each bug, and updates statuses and comments. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED