> ## Documentation Index
> Fetch the complete documentation index at: https://anything.notte.cc/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Catalog

> Ready-made endpoints across real sites.

The [marketplace](https://anything.notte.cc/marketplace) is the catalog of published APIs. Building one takes minutes; running one that exists takes seconds. Search before you build.

Entries are organised by site, and a site usually has several endpoints. Each listing shows its parameters, response schema, run count, call snippets, and thirty days of health checks. Filter by category, or by site with `?q=`.

## Running someone else's API

Call its `function_id` with your Notte API key like any other. The run is billed to **you**, and secrets resolve from **your** workspace. There is no version pinning: a published API runs its latest version, so an author's change reaches you immediately.

## Publishing

Publish from the API's menu, or with the `publish` MCP tool. Nothing is copied: the listing points at your API in your workspace, so run counts accrue to it and your improvements reach every consumer. Category and tagline are filled in automatically by reading the code.

Two separate consents, and neither implies the other:

| Flag        | Grants                                          |
| ----------- | ----------------------------------------------- |
| `published` | A stranger may **run** it, billed to themselves |
| `shared`    | A stranger may **fork** it into their workspace |

Publishing authorises against the **workspace** that owns the API, so any member can list it or take it down. Unpublishing takes effect immediately.

<Note>
  A new listing starts as a **draft**: browsable, linkable, and runnable straight away, but absent from the MCP `search` tool until someone reviews it. Not seeing it from an agent right after publishing is the review queue, not a failed publish. Re-publishing to refresh metadata does not demote a listing that is already reviewed.
</Note>

Today the publish flow sets both flags together, so "listed but not forkable" is a state the data model allows but the current flow cannot reach.

## Health checks and verified

The status strip answers one question: when we last ran this, did it work?

| Status           | Meaning                                                  |
| ---------------- | -------------------------------------------------------- |
| **ok**           | The probe ran it and got a usable result                 |
| **failed**       | The probe ran it and it did not work                     |
| **not observed** | The probe never got an answer back. Nothing was measured |

**Not observed** is our side (expired key, quota, timeout), not a negative result. Treat it as unchecked.

The probe calls each API with **no arguments**, relying on its declared defaults, so one whose defaults do not produce a real result will read as broken. Check your defaults before publishing.

A listing is **verified** when it has been reviewed and the reviewed version is still the version that runs. Deploy new code and it re-enters the review queue on its own. MCP `search` serves verified entries only.