AINumbers.co

AINumbers.co Nft API

The nft API from AINumbers.co — 1 operation(s) for nft.

Documentation GitHub OpenAPI

Operations 1

POST /v1/tools/validate_nft_metadata NFT Metadata Validator #

Specifications

⚙

OpenAPI

https://artifacts.apis.io/ainumbers-co/openapi/ainumbers-co-nft-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/ainumbers-co:ainumbers-co-nft-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

openapi: 3.2.0
info:
  title: AINumbers.co Fintech Intelligence Suite Nft API
  version: 1.0.0
  description: '**1255 fintech intelligence tools** covering ISO 20022, A2A payments, CFPB §1033, EU AI Act, DORA, MiCA, AML/KYC, BaaS, DLT/tokenization, ESG/climate finance, agentic payments (AP2, ACP, x402, Visa TAP, Mastercard Agent Pay), PQC migration, sanctions screening, and OpenChainGraph v0.4 computation chains.


    ## Transport


    > **The live transport is MCP JSON-RPC 2.0 at `https://mcp.ainumbers.co/mcp` — not REST.**

    >

    > This OpenAPI file is a **descriptive data-room artifact** — a machine-readable index of all tools and their input/output schemas. The REST paths (`POST /v1/tools/{name}`) described here are a projection; they become functional only if the optional REST shim (Area 2 Path B) is deployed.

    >

    > To call tools today, connect via the official MCP client SDKs. TypeScript: `@modelcontextprotocol/sdk`. Python: `mcp`.


    ## Architecture


    All tools run **entirely client-side** (browser JavaScript). Zero PII. Zero server calls after page load. Deterministic, reproducible outputs. Licensed CC BY 4.0.


    OpenChainGraph v0.4 compute-binding nodes additionally run **server-side on the MCP Worker** and emit verifiable artifacts with `execution_hash` (WebCrypto SHA-256 over RFC 8785 canonical JSON).'
  contact:
    name: Post Oak Labs
    url: https://postoaklabs.com
    email: tim@postoaklabs.com
  license:
    name: CC BY 4.0
    url: https://creativecommons.org/licenses/by/4.0/
servers:
- url: https://ainumbers.co
  description: Static browser-based tool host (DreamHost). Tools run client-side — no REST gateway is active on this origin. See x-mcp for the live MCP endpoint.
tags:
- name: NFT
paths:
  /v1/tools/validate_nft_metadata:
    post:
      operationId: validate_nft_metadata
      summary: NFT Metadata Validator
      description: 'Validates NFT metadata JSON against the ERC-721/ERC-1155 standard and the OpenSea metadata schema. Checks required fields (name, description, image), recommended fields (external_url, animation_url, attributes array structure), and optional license fields. Returns a pass/warn/fail verdict with per-field check results. Runs entirely client-side.


        **Tool URL:** https://ainumbers.co/tools/528-nft-metadata-validator.html'
      tags:
      - NFT
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
              - metadata
              properties:
                metadata:
                  type: object
                  description: NFT metadata object (parsed from JSON)
      responses:
        '200':
          description: Successful tool execution result
          content:
            application/json:
              schema:
                type: object
                properties:
                  valid:
                    type: boolean
                  allPass:
                    type: boolean
                  requiredPass:
                    type: boolean
                  anyWarn:
                    type: boolean
                  failCount:
                    type: integer
                  warnCount:
                    type: integer
                  fieldCount:
                    type: integer
                  checks:
                    type: array
                    items:
                      type: object
                      properties:
                        field:
                          type: string
                        status:
                          type: string
                          enum:
                          - pass
                          - fail
                          - warn
                        message:
                          type: string
      x-mcp-tool-name: validate_nft_metadata
      x-tool-url: https://ainumbers.co/tools/528-nft-metadata-validator.html
      x-source: manifest
x-mcp:
  transport: MCP JSON-RPC 2.0 (streamable HTTP)
  endpoint: https://mcp.ainumbers.co/mcp
  protocol_version: '2025-11-25'
  authentication: none
  registry: co.ainumbers/tools (official MCP registry)
  note: Connect any MCP-compatible client (Claude, ChatGPT, custom agent) directly to this endpoint. The REST paths in this file are descriptive only — they do not exist on the live server unless the REST shim is deployed.