Catalog

How the looot catalog is organized, categories, platforms, jobs, endpoints and providers, how to find a provider, access states, and the counts behind them.

The catalog is one list of provider endpoints, organized four ways:

category > platform > job > endpoint (each backed by a provider)

A category is a broad area, such as Enrichment or SEO/AEO.
A platform groups a provider’s endpoints by product, for example a provider that ships both a search API and a scraping API is two platforms under one provider.
A job is the task, not the provider, for example people.email.verify. Several endpoints from different providers can do the same job; looot ranks them against each other. See Jobs.
An endpoint is one callable operation from one provider, with its own id, input schema and price.

Find a provider or an endpoint

Search, in plain words: looot search "verify an email", or the search and search_catalog MCP tools.
catalog_overview (MCP tool, or GET /v1/catalog/overview): what exists, as categories, platforms and jobs, with counts at every level. Pass topic=email for the jobs that match a word, or category=/platform= to walk one branch.
The public catalog, no account needed: GET /v1/public-catalog and looot.ai/catalog. See Browse without an account.
An endpoint’s own card, plain Markdown, no token: https://api.looot.ai/catalog/<endpointId>.md.
A provider’s own card, every endpoint it has: https://api.looot.ai/catalog/providers/<provider>.md.

Access states

Every endpoint carries an access value:

`access`	Meaning
`runs_now`	Callable now: no key needed, or looot already has a platform key for it.
`needs_your_account`	Acts on your own connected account with that provider (for example Instantly or Gmail). Connect it first.
`coming_soon`	A registered provider with no platform key yet. Calling it returns a `provider_error`, not a result.