Skip to content
A clean API for useful work

Browser-tested tools, ready for your product.

Use a focused execution API for approved Tool Swim families. Every available endpoint documents its permission, cost, limits, errors, and data boundary.

Live-only keysRequest logsClear credit accounting
First request
curl https://toolswim.com/api/tools/qr-code-generator \
  -H "Authorization: Bearer ts_live_..." \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: qr-order-1042" \
  -d '{
    "operation": "url",
    "value": "https://example.com"
  }'

200 response

{
  "requestId": "req_01k...",
  "tool": "qr-code-generator",
  "operation": "url",
  "result": { "dataUrl": "data:image/png;base64,..." },
  "creditsUsed": 1
}

16

approved executable families

17

discoverable tool families

1

stable live API surface

Designed for production

A small surface with explicit guarantees

Tool Swim keeps account access simple while making each operation’s behavior visible before it reaches your application.

One live-key model

No test/live switch and no version maze. Keys are live, scoped, revocable, and easy to reason about.

Explicit permissions

Each executable family declares the permission, credit cost, limits, and privacy boundary before you call it.

Consistent contracts

Predictable envelopes, normalized errors, request IDs, and examples make integrations easier to maintain.

Documentation that scales

Find one family. Read one contract.

The API landing page should not render a thousand operations. Documentation is searchable, grouped by family, and opens only the contract you are working with.

Search by task, family, operation, or permission.
Filter by availability instead of scanning unavailable endpoints.
See authorization and privacy boundaries beside every example.

Know the boundary

Browser tools and APIs are intentionally separate

Public browser tools do their work locally and do not silently call the developer API. API execution happens only when an authenticated developer deliberately invokes it.

In the browser

Immediate and local-first

No signup for public tools. Sensitive inputs stay on the device for local-capable workflows.

Through the API

Explicit and accountable

Authenticated requests use scoped permissions, defined limits, credit accounting, and visible logs.

Start with the contract, then ship with confidence.

Review available families, permissions, examples, limits, and errors in one place.

Open API docs