timzinin-com

timzinin-com Openapi.json API

The Openapi.json API from timzinin-com — 1 operation(s) for openapi.json.

GitHub OpenAPI

Operations 1

GET /openapi.json Custom Openapi #

Specifications

⚙
OpenAPI
https://artifacts.apis.io/timzinin-com/openapi/timzinin-com-openapi-json-api-openapi.yml

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/timzinin-com:timzinin-com-openapi-json-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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.

GitHub Google LinkedIn

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

OpenAPI Specification

timzinin-com-openapi-json-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Zinin M2M Hub Openapi.json API
  description: Pay-per-call data & tool APIs
  version: 1.0.0
  x-guidance: 'Zinin M2M Hub — pay-per-call data & tool APIs for AI agents. Each POST /api/{slug} operation below is a distinct paid tool: call GET /api/{slug}/schema first for the exact input shape, then POST with a signed PAYMENT-SIGNATURE header (x402 v2, USDC — see x-payment-info per operation) or omit it to receive a 402 with full payment requirements in the PAYMENT-REQUIRED header. The same catalog is also available as MCP JSON-RPC tool bundles at POST /mcp/{bundle} — see GET /.well-known/x402 for the list of bundles.'
tags:
- name: Openapi.json
paths:
  /openapi.json:
    get:
      summary: Custom Openapi
      description: 'FastAPI''s auto-generated schema only has one *templated* path

        (`/api/{slug}`) since that''s how the route is declared — not useful to an

        API-discovery client that can''t literally call a `{slug}` placeholder.

        We swap it for one concrete, fully-typed entry per active actor (own

        input schema as requestBody, own price in x-payment-info), which is what

        "x-payment-info on every /api/* endpoint" actually needs to mean here.


        x-payment-info shape follows x402scan''s discovery spec exactly

        (x402scan.com/discovery/spec, fetched 27.07.2026): `price.mode` +

        `price.currency` + `price.amount` (decimal USD, NOT atomic units — their

        own docs: "OpenAPI x-payment-info.price.amount is decimal USD; runtime

        x402 v2 accepts[].amount is token atomic units") and `protocols: [{x402:

        {}}]`. `network`/`payTo`/`asset` are additive beyond their required

        fields — their spec says x-payment-info is "a superset of the IETF API

        payment spec... the fields do not collide" so extra fields are safe.'
      operationId: custom_openapi_openapi_json_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                additionalProperties: true
                type: object
                title: Response Custom Openapi Openapi Json Get
      tags:
      - Openapi.json