Marmeto Feedback by Marmeto API

Name: Feedback by Marmeto API
Brand: Feedback by Marmeto API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityForms SurveysapiKey1 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the Feedback by Marmeto API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Feedback by Marmeto 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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Feedback by Marmeto API.

Look up the project record bound to a feedback API key

Verify a feedback workspace key is correctly configured

GET STARTED

Start building with Feedback by Marmeto API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Feedback by Marmeto API for, with concrete tasks.

★ 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.

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.

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.

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.

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

1 endpoints — jentic publishes the only available openapi specification for feedback by marmeto api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/project

GET

/project

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Marmeto `x-feedback-key` is stored encrypted in the Jentic vault (MAXsystem) and applied to the header at execution time. Agents receive scoped session references — the raw key never enters the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'register feedback project') and Jentic returns the single Marmeto project operation with its header schema.

Time to first call

Direct Feedback by Marmeto integration: under 1 hour for the single endpoint. Through Jentic: a few minutes — search, load schema, execute.

FAQs

Specific to using Feedback by Marmeto API through Jentic.

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 at https://app.jentic.com/sign-up.

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 the MAXsystem vault 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.