BuyingMesh Tariffs API

The Tariffs API from BuyingMesh — 1 operation(s) for tariffs.

Operations 1

POST /v1/tariffs/lookup Return a preliminary HS-code and destination duty range #

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/buyingmesh-com:buyingmesh-com-tariffs-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

buyingmesh-com-tariffs-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: BuyingMesh Procurement Tariffs API
  version: 0.5.4
  description: Structured supplier and product API for buying agents. Product discovery exposes reviewed merchant listings with explicit price, lead-time and inventory evidence; the current public catalog contains 86 approved production SKUs from one reviewed supplier and reports confirmed inventory in the current snapshot. Read each SKU inventoryStatus and dataFreshness before quoting. x402 payments and real order creation are disabled until production settlement and fulfillment are ready. All REST responses use the JSON envelope {status, data, error}; MCP remains JSON-RPC. Merchant applications are open now.
servers:
- url: https://buyingmesh.com
tags:
- name: Tariffs
paths:
  /v1/tariffs/lookup:
    post:
      operationId: lookupTariffs
      summary: Return a preliminary HS-code and destination duty range
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
              - hsCode
              - destinationCountry
              properties:
                hsCode:
                  type: string
                destinationCountry:
                  type: string
                customsValue:
                  type: number
                currency:
                  type: string
      responses:
        '200':
          description: Non-binding tariff estimate requiring broker confirmation
        '422':
          $ref: '#/components/responses/ValidationError'
      tags:
      - Tariffs
components:
  schemas:
    Error:
      type: object
      required:
      - status
      - data
      - error
      properties:
        status:
          type: string
          const: error
        data:
          type: 'null'
        error:
          type: object
          required:
          - code
          - message
          - requestId
          properties:
            code:
              type: string
            message:
              type: string
            requestId:
              type: string
  responses:
    ValidationError:
      description: Validation failed
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
    adminReviewKey:
      type: apiKey
      in: header
      name: X-Admin-Key