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

# Discovering Public ToolSets

> Find public ToolSets published by other organizations on the Explore page and run their tools with your own API key

Organizations can publish ToolSets as **Public**. Public ToolSets are listed on the **Explore** page, where anyone can browse their tools and schemas, and any organization with a Jinba Toolbox API key can execute them.

## The Explore Page

Open `https://toolbox.jinba.io/explore`. No sign-in is required.

* **Search** -- the **Search tool sets...** box matches the ToolSet name, description and slug.
* **Tags** -- up to eight popular tags are shown as pills; click one to filter, and **Clear filter** to remove it. The search text and tag are kept in the URL (`?q=&tag=`), so a filtered view can be shared.
* **Cards** -- each result shows the ToolSet slug, description, up to four tags, the language and the ToolSet's latest version number (which may be newer than the version public calls execute). Only public ToolSets with a version published to their `default` environment are listed.

Clicking a card opens the ToolSet page at `/explore/{organizationId}/{toolsetSlug}`. It carries a **Public** badge and shows the tools with their input schemas (output schemas are available through the discovery API below), the **Versions**, the **Details** (language, creation date and, when the ToolSet has packages, their names under **Dependencies**) and a **Quick Start** with the endpoint to call. Source code is never shown.

## Using a Public ToolSet

**1. Find the ToolSet**

Note the organization ID and ToolSet slug from the page URL. The organization ID has to be the canonical ID shown there; organization slugs are not accepted by the public endpoints.

**2. Create an API key**

Any valid Jinba Toolbox API key works, including one from your own organization. See [API Key Management](/en/pages/toolbox/console/api-keys).

**3. Execute via REST or MCP**

```bash theme={null}
curl -X POST https://toolbox-api.jinba.io/v1/public/{organizationId}/{toolsetSlug}/run/{toolSlug} \
  -H "Authorization: Bearer $JINBA_TOOLBOX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"input": {"query": "Hello"}}'
```

The response contains `runId`, `version`, `success`, `output`, `error` and `durationMs`. A call from another organization runs the version the provider published to its `default` environment; a call with the provider's own key runs the version published for that key's environment. The unpublished draft is never executed, and the call is refused with `400` and "No published version available" when nothing is published for that environment. If the ToolSet has MCP enabled, the same tools are available at `/v1/public/{organizationId}/{toolsetSlug}/mcp` -- see [MCP Integration](/en/pages/toolbox/developer/mcp).

Each successful execution costs **one credit from your organization**, not from the provider's. See [Credits](/en/pages/toolbox/console/credits).

## Discovery API

The listing is also available without authentication:

```bash theme={null}
# All public ToolSets
curl "https://toolbox-api.jinba.io/v1/explore/toolsets"

# Text search
curl "https://toolbox-api.jinba.io/v1/explore/toolsets?q=weather"

# Filter by tag
curl "https://toolbox-api.jinba.io/v1/explore/toolsets?tag=slack"
```

`limit` (default 50, at most 100) and `offset` paginate the list. `GET /v1/explore/toolsets/{organizationId}/{toolsetSlug}` returns one ToolSet with its tools and versions, and `GET /v1/explore/tags` returns the popular tags. Details are in the [REST API](/en/pages/toolbox/developer/api#explore-routes) reference.

## Publishing Your Own ToolSet

To appear on the Explore page, a ToolSet must be set to **Public** and have a version published to its `default` environment. A ToolSet published only to another environment profile (for example `staging`) is not listed. The visibility switch and its implications are described in [Visibility Settings](/en/pages/toolbox/console/toolsets#visibility-settings).

## Related

* [ToolSet Management](/en/pages/toolbox/console/toolsets) -- visibility and publishing
* [Credits](/en/pages/toolbox/console/credits) -- who pays for an execution
* [REST API](/en/pages/toolbox/developer/api) -- public and explore routes


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.