APIClaw TinyFish Pass-through API

The TinyFish Pass-through API from APIClaw — 1 operation(s) for tinyfish pass-through.

Operations 2

POST /tinyfish/{endpoint} Tinyfish Proxy Route #
GET /tinyfish/{endpoint} Tinyfish Proxy Route #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/apiclaw:apiclaw-tinyfish-pass-through-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

apiclaw-tinyfish-pass-through-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: LiteLLM TinyFish Pass-through API
  description: 'Proxy Server to call 100+ LLMs in the OpenAI format. **Customize Swagger Docs**


    👉 ```LiteLLM Admin Panel on /ui```. Create, Edit Keys with SSO. Having issues? Try ```Fallback Login```


    💸 ```LiteLLM Model Cost Map```.


    🔎 ```LiteLLM Model Hub```. See available models on the proxy. **Docs**'
  version: 1.105.1
tags:
- name: TinyFish Pass-through
paths:
  /tinyfish/{endpoint}:
    post:
      tags:
      - TinyFish Pass-through
      summary: Tinyfish Proxy Route
      description: 'Pass-through for the TinyFish Agent API (goal-based web automation).


        Forwarded endpoints:

        - POST /v1/automation/run — run to completion (blocking)

        - POST /v1/automation/run-async — submit a run, poll GET /v1/runs/{id} for the result

        - POST /v1/automation/run-sse — run with SSE progress events

        - GET /v1/runs/{id} — run status / result

        - POST /v1/runs/{id}/cancel — cancel a run


        Every other Agent API endpoint (vault, wallet, browser profiles, and the GET /v1/runs

        listing, which would let any caller discover other callers'' run ids) returns 403: all

        proxy callers share one upstream key.


        Credential lookup order:

        1. passthrough_endpoint_router (config.yaml deployments with use_in_pass_through)

        2. TINYFISH_API_KEY environment variable


        Docs'
      operationId: tinyfish_proxy_route_tinyfish__endpoint__post
      security:
      - APIKeyHeader: []
      parameters:
      - name: endpoint
        in: path
        required: true
        schema:
          type: string
          title: Endpoint
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
    get:
      tags:
      - TinyFish Pass-through
      summary: Tinyfish Proxy Route
      description: 'Pass-through for the TinyFish Agent API (goal-based web automation).


        Forwarded endpoints:

        - POST /v1/automation/run — run to completion (blocking)

        - POST /v1/automation/run-async — submit a run, poll GET /v1/runs/{id} for the result

        - POST /v1/automation/run-sse — run with SSE progress events

        - GET /v1/runs/{id} — run status / result

        - POST /v1/runs/{id}/cancel — cancel a run


        Every other Agent API endpoint (vault, wallet, browser profiles, and the GET /v1/runs

        listing, which would let any caller discover other callers'' run ids) returns 403: all

        proxy callers share one upstream key.


        Credential lookup order:

        1. passthrough_endpoint_router (config.yaml deployments with use_in_pass_through)

        2. TINYFISH_API_KEY environment variable


        Docs'
      operationId: tinyfish_proxy_route_tinyfish__endpoint__get
      security:
      - APIKeyHeader: []
      parameters:
      - name: endpoint
        in: path
        required: true
        schema:
          type: string
          title: Endpoint
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
components:
  schemas:
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
            - type: string
            - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
      - loc
      - msg
      - type
      title: ValidationError
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
  securitySchemes:
    APIKeyHeader:
      type: apiKey
      description: Bearer token
      in: header
      name: x-litellm-api-key
    HTTPBearer:
      type: http
      scheme: bearer