# 1ToolRing

> One key and one prepaid wallet for a catalog of paid tools, for the AI a person already uses. Every entry carries its price; a failed call is never charged. Formerly StudioAPI; some service hosts are still on studioapi.dev while they move to 1toolring.com.

## Core facts

- Product: 1ToolRing (spoken "one tool ring"). Tagline: Every tool, one ring.
- Install prompt for a person to paste into their AI: `Set up 1ToolRing from 1toolring.com/install` (the older `studioapi.dev/install` redirects here)
- Money: the wallet is kept in credits, 1 credit = Rp1 (Indonesian rupiah); prices on the site are shown in USD at the ECB rate and are indicative. A new account gets 3,000 credits once, when its email is verified. AI models bill per token from a separate USD wallet. Only successful calls are charged.
- Auth: `Authorization: Bearer <API key>`. Keys are created at https://app.1toolring.com/keys, shown once, stored hashed.
- Catalog today: email verification (7 entries) and OpenAI-compatible AI models (3 entries). More third-party tools are being onboarded on the platform's own accounts; a tool is listed only once its price has provenance.

## Links

- Install page (read this to set up): https://1toolring.com/install
- Landing page: https://1toolring.com
- Dashboard / console: https://app.1toolring.com
- Documentation: https://docs.studioapi.dev
- MCP server (streamable HTTP, Bearer key): https://mcp.studioapi.dev/mcp
- Public API host: https://use.studioapi.dev (moving to https://api.1toolring.com)
- AI host (OpenAI-compatible): https://ai.studioapi.dev/v1 (moving to https://api.1toolring.com/v1)

## How an agent uses it

1. Discover, no key, no charge: `GET https://use.studioapi.dev/api/v1/catalog/search?q=<job>`
2. Read one entry: `GET https://use.studioapi.dev/api/v1/catalog/<id>` — fields: id, name, summary, category, method, path, price_credits, price_unit, freshness.
3. Call it: send the entry's own `method` + `path` to https://use.studioapi.dev with the Bearer key.
4. Reconcile: the response carries the exact charge in `X-ToolRing-Credits`; builds deployed before the rename emit only `X-StudioAPI-Credits`. Read whichever is present — same value.

## MCP tools

- `search_catalog(query, category?, capability?, limit?)` — find a tool by the job.
- `call_service(id, query?, body?, path_params?)` — builds the real request from the catalog entry and sends it.
- Fixed tools for the live entries are also exposed.

## Not offered (do not assume)

- No OAuth on the MCP endpoint yet: the key is pasted once by the person.
- No x402 or on-chain payment on the tool surface; top-ups are made in the console.
- No per-agent budgets beyond what the console's key management provides.