Invoket

Send feedback (/review)

/review is a free feedback channel to the Invoket team: tell us about an unsupported case, an improvement you need, a bug, a missing data point or a pricing concern. It is meant to be called by an agent when it hits something it cannot do — but it is just as usable by a human with curl.

Unlike the endpoints in the catalog, /review is not a paid endpoint: there is no payment, no account and no API key. It does not appear in /catalog, it has no price, and there is nothing to settle. Submitted feedback is read by the team through an internal control tower. We read everything, but this is a one-way channel: we do not promise an individual reply.

Request

POST to /review with a JSON body. Set Content-Type: application/json.

POST /review
Content-Type: application/json
{
  "category": "unsupported_case",
  "target": "POST /iban/screen",
  "message": "I need sanctions screening for account holders, not just the bank.",
  "context": {
    "example_input": { "iban": "DE89370400440532013000", "name": "ACME GmbH" },
    "severity": "medium"
  }
}
FieldTypeRequiredDescription
categorystringyesOne of unsupported_case, improvement, bug, data_gap, pricing, other.
targetstringnoThe endpoint the feedback is about, e.g. POST /iban/screen. Omit for general platform feedback.
messagestringyesFree-text description of the need, bounded in length.
contextobjectnoOptional details: example_input (any JSON) and severity (low, medium, high).

Response

A well-formed submission is accepted with 202 Accepted:

{ "status": "recorded", "id": 1234 }

The id identifies the recorded item internally. A malformed body (missing message, unknown category, invalid JSON) returns a 4xx with an error payload:

{ "error": "invalid category", "code": "bad_request" }

Example (curl)

curl -i -X POST "https://api.invoket.com/review" \
  -H "Content-Type: application/json" \
  -d '{
    "category": "data_gap",
    "target": "GET /climate/point",
    "message": "Please cover elevation for mountain grid cells.",
    "context": { "severity": "low" }
  }'

The base URL above is the production gateway; the flow is identical against any Invoket deployment.

  • For agents — how an agent discovers and calls Invoket’s paid endpoints.
  • Quickstart — probe a 402, then settle and replay a paid call.