timzinin-com

timzinin-com .well Known API

The .well Known API from timzinin-com — 1 operation(s) for .well known.

GitHub OpenAPI

Operations 1

GET /.well-known/x402 Well Known X402 #

Specifications

⚙
OpenAPI
https://artifacts.apis.io/timzinin-com/openapi/timzinin-com-well-known-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-well-known-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-well-known-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Zinin M2M Hub .well Known 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: .well Known
paths:
  /.well-known/x402:
    get:
      summary: Well Known X402
      description: 'Not gated by x402scan''s own compliance check (their discovery

        precedence is /openapi.json first, runtime 402 header second — see

        custom_openapi()/call_actor() below for those) and this hub has no known

        v1 consumer of THIS specific endpoint (v1 REST clients call

        `/api/{slug}` directly and read its own 402 body — preserved separately

        in call_actor()), so this manifest is migrated to pure v2 rather than

        dual-emitted like the runtime 402 response is.'
      operationId: well_known_x402__well_known_x402_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                additionalProperties: true
                type: object
                title: Response Well Known X402  Well Known X402 Get
      tags:
      - .well Known