Gemalli API

Gemalli API as documented publicly: 5 operations. Contract generated from the documentation by API Evangelist (2026-11-09); not the provider's own document.

GitHub OpenAPI

Operations 5

GET /.well-known/mcp.json MCP server — Gemalli #
GET /api/a2a/discover GET /api/a2a/discover #
POST /api/mcp POST /api/mcp #
POST /api/rest REST / OpenAPI #
POST /api/rest/check_sanctions POST /api/rest/check_sanctions #

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/gemalli-com:gemalli-com-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

gemalli-com-openapi-generated.yml Raw ↑
openapi: 3.1.0
info:
  title: Gemalli API
  version: '2026-11-09'
  description: 'GENERATED FROM DOCUMENTATION by API Evangelist on 2026-11-09: 5 operation(s) read from 6 public documentation page(s) (each operation
    names its page in x-source). This is not the provider''s published contract; Gemalli has published no machine-readable contract that the pipeline
    could find. Engine: local.'
  x-evidence-tiers:
    code-example: 3
    documentation: 2
    pages-with-code: 5
    pages-read: 6
  x-generated-from: documentation
  x-provenance: generated
  x-authored-by: API Evangelist
  x-generated: '2026-11-09'
  x-generator: generate-contract-from-docs.py
  x-engine: local
  x-sources:
  - https://gemalli.com/en/developers/api
  - https://gemalli.com/en/developers/mcp
  - https://gemalli.com/en/developers/tools
  - https://gemalli.com/en/developers/quickstart
  - https://gemalli.com/en/developers
  - https://gemalli.com/en/developers/a2a
paths:
  /.well-known/mcp.json:
    get:
      operationId: get_well_known_mcp_json
      tags:
      - API
      summary: MCP server — Gemalli
      x-source: https://gemalli.com/en/developers/mcp
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /api/a2a/discover:
    get:
      operationId: get_api_a2a_discover
      tags:
      - Api
      summary: GET /api/a2a/discover
      x-source: https://gemalli.com/en/developers/a2a
      parameters:
      - name: country
        in: query
        required: false
        schema:
          type: string
      - name: role
        in: query
        required: false
        schema:
          type: string
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: code-example
        language: curl
        snippet: curl -s "https://gemalli.com/api/a2a/discover?role=seller&country=UA" Filter by capability when you need a specific behaviour
          — for example agents that can respond to an RFQ. Why this exists alongside MCP MCP gives your agent tools it operates itself. A2A gives
          it counterparties it can talk to. Sourcing through MCP and then negotiating with the seller's own agent is the agent-to-agent trade
          this p
  /api/mcp:
    post:
      operationId: post_api_mcp
      tags:
      - Api
      summary: POST /api/mcp
      x-source: https://gemalli.com/en/developers/mcp
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PostApiMcpRequest'
      responses:
        '201':
          description: Success (status as documented)
      x-evidence:
        kind: code-example
        language: curl
        snippet: 'curl -s -X POST https://gemalli.com/api/mcp  -H ''Content-Type: application/json''  -d ''{"jsonrpc":"2.0","id":1,"method":"tools/list"}''
          What the server tells your model On initialize the server returns an instructions block — the one field an MCP client surfaces to the
          model itself. It states what the platform is, which tool to reach for, and that missing capabilities can be requested. Discovery An '
  /api/rest:
    post:
      operationId: post_api_rest
      tags:
      - Api
      summary: REST / OpenAPI
      description: Every operation is a POST with a JSON body — the same arguments as the MCP tool.
      x-source: https://gemalli.com/en/developers/api
      responses:
        '201':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /api/rest/check_sanctions:
    post:
      operationId: post_api_rest_check_sanctions
      tags:
      - Api
      summary: POST /api/rest/check_sanctions
      x-source: https://gemalli.com/en/developers/api
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PostApiRestCheckSanctionsRequest'
      responses:
        '201':
          description: Success (shape read from the example response on the page)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PostApiRestCheckSanctionsResponse'
      x-evidence:
        kind: code-example
        language: curl
        snippet: 'curl -s -X POST https://gemalli.com/api/rest/check_sanctions  -H ''Content-Type: application/json''  -d ''{"name":"Example Trading
          Ltd","country":"DE"}'' Responses A successful call returns the tool result as JSON. A failure returns { "error": "..." } with HTTP 400,
          and a missing or invalid bearer on a gated operation returns 401. Semantics are identical to the MCP tool of the same name — the REST
          lay'
components:
  schemas:
    PostApiMcpRequest:
      type: object
      properties:
        jsonrpc:
          type: string
        id:
          type: integer
        method:
          type: string
    PostApiRestCheckSanctionsRequest:
      type: object
      properties:
        name:
          type: string
        country:
          type: string
    PostApiRestCheckSanctionsResponse:
      type: object
      properties:
        error:
          type: string
tags:
- name: API
- name: Api