canonical: https://jentic.com/apis/marmeto.org/marmeto

# Marmeto Feedback by Marmeto API

Jentic publishes the only available OpenAPI specification for Feedback by Marmeto API, keeping it validated and agent-ready. Feedback by Marmeto is a lightweight feedback-collection service that exposes a single endpoint to register or look up a project under a feedback workspace. Customers use it to bootstrap feedback channels for their websites or apps and to verify the configured project metadata. The narrow surface area makes it a quick drop-in for product teams who need a hosted feedback widget without building one.

## For AI agents

Register or fetch a Marmeto Feedback project record using a single project endpoint protected by an `x-feedback-key` header.

## Scope

Does not ingest feedback comments, render the widget, or expose dashboard analytics - use for project registration and lookup against an `x-feedback-key` only.

## Capabilities

- Register a new Marmeto Feedback project under a workspace
- Look up the project record bound to a feedback API key
- Verify a feedback workspace key is correctly configured
- Bootstrap a feedback channel for a new website or app
- Fetch project metadata before rendering the embedded feedback widget

## Use cases

### Feedback Widget Bootstrap

Product teams adding the Marmeto feedback widget to a marketing site need to register the project once and then load its metadata when the widget initialises. The single `/project` endpoint covers both: a POST creates the project, and a GET returns the configuration to inject into the widget at runtime.

Example prompt: Call the project endpoint with the workspace `x-feedback-key` header and confirm the response returns the expected project ID and name.

### Workspace Key Validation

Operations teams rotating feedback workspace keys need a quick way to verify the new key is wired up before swapping it in production config. Marmeto's project endpoint serves as the validation probe - a successful response confirms the key authenticates against the right project record.

Example prompt: Issue a GET to the project endpoint with the candidate `x-feedback-key` header and treat a 200 response as confirmation the key is live.

### Multi-Site Feedback Provisioning

Agencies running Feedback by Marmeto across multiple client sites need to provision a project per site at onboarding time. The lightweight project endpoint is invoked once per new client to create the record and store the returned ID alongside the client's workspace key in the agency's CRM.

Example prompt: For each new client workspace key, call the project endpoint and store the returned project ID against that client in the CRM.

### AI Agent Feedback Setup

An onboarding AI agent that walks a new customer through Marmeto setup can use Jentic to register the feedback project on the customer's behalf. Jentic stores the `x-feedback-key` securely so the agent never embeds it in chat history or scratchpad.

Example prompt: Search Jentic for 'register feedback project', load the Feedback by Marmeto project schema, and execute it with the workspace key supplied during onboarding.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/project` | Register or fetch the Marmeto Feedback project bound to the workspace key |

## Key resources

- **Project** — The Feedback by Marmeto project record; the single resource exposed by the v2 API.

## Why Jentic

- **Setup:** Wiring the Feedback by Marmeto API by hand means reading its x-feedback-key header scheme, pointing at the feedback/v2 host, and handling project lookups yourself. Through Jentic you install once, import Feedback by Marmeto from the API Directory, store the x-feedback-key once, and your agent calls it.
- **Permission scoping:** The listed surface is a single read operation against your project, so you limit the agent to the operations it needs, such as looking up a registered feedback project. It calls only the operations you allow, and nothing else is reachable.
- **Credential handling:** Your Marmeto x-feedback-key is stored once, encrypted, by your own Jentic One instance and injected into the header at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'register a feedback project' or 'look up a Marmeto project', and Jentic returns the matching Feedback by Marmeto operation with its header schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Typeform API** — Typeform offers a full-featured form and survey API with logic and integrations.
- **SurveyMonkey API** — SurveyMonkey provides large-scale survey collection and analytics.
- **Slack API** — Slack is a common destination for forwarding new feedback submissions.

## FAQ

### Why is there no official OpenAPI spec for Feedback by Marmeto API?

Marmeto does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the Feedback by Marmeto API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Feedback by Marmeto API use?

The API uses an `x-feedback-key` header containing the workspace API key. Through Jentic, the key is stored encrypted in your Jentic One instance and applied to the request header at execution time.

### Can I register a new feedback project with the Feedback by Marmeto API?

Yes. The `/project` endpoint registers and returns the project record tied to the supplied `x-feedback-key`. The v2 API exposes this as the single resource you interact with.

### What are the rate limits for the Feedback by Marmeto API?

Marmeto does not publish rate limits in the spec. Because the spec exposes a single endpoint typically called once per page-load, conservative caching of the project response (e.g., 60 seconds) keeps usage well within any reasonable quota.

### How do I bootstrap a feedback widget through Jentic?

Run `pip install jentic`, then use Jentic's search with the query 'register feedback project'. Jentic loads the `/project` operation schema and your agent executes it with the workspace key, returning the project metadata needed to render the widget.

### Why does the API expose only one endpoint?

The v2 spec scopes Feedback by Marmeto to project-level provisioning and lookup. Comment ingestion and dashboard reads are handled in the embedded widget and Marmeto dashboard, not via this public API surface.

### Can I limit what my agent is allowed to do with the Marmeto Feedback API?

Yes. Because you self-host Jentic One, your own rules decide which operations and credentials the agent may use, and this API exposes just a single project operation against the `/project` endpoint. You can restrict the agent to only looking up or registering the feedback project bound to your `x-feedback-key`, and it can call nothing beyond the operations you allow. The workspace key is stored encrypted in your own instance and applied at execution time, so the agent never sees it in its prompt or logs.