Skip to main content
POST
One tool's input schema, price and docs — what you need to build a valid `input`.

Authorizations

Authorization
string
header
required

An API key minted in the console, sent as Authorization: Bearer <key>. Keys are project-scoped and carry per-operation scopes. A gck_test_… key runs the full request path — including the real upstream call — and bills nothing.

Every scope is enumerated in x-scopes below and in the RFC 9728 protected-resource metadata at https://cloud.gomry.com/.well-known/oauth-protected-resource, which is also what a 401 points at through its WWW-Authenticate: Bearer resource_metadata="…" header.

Body

application/json
vendor
any

Required for run/inspect. Catalogue vendor slug, e.g. "apify". Monid calls this provider; here it is vendor, because provider already means an adapter.

endpoint
any

Required for run/inspect. The tool's path within that vendor, e.g. "/apidojo/tweet-scraper". Both halves come from discover or inspect.

input
any

Required for run. An object matching the tool's own inputSchema from inspect. Passed through unvalidated by us — the tool rejects what it does not accept.

query
any

Required for discover. 1–2000 characters of natural language describing the task.

limit
any

Discover only. How many tools to return, 1–20. Values above the ceiling are clamped, not refused.

timeout
any

Milliseconds before the catalogue call is abandoned. 1000–90000. The run route is capped at 120s server-side.

Response

Success. lookups reports what was metered.

The response is of type object.