eesier

eesier API

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

GitHub OpenAPI

Operations 4

GET /rest/v1/call/{toolName} Invoke a read-only tool from the query string. Any other tool returns 405. #
GET /rest/v1/tools GET /rest/v1/tools #
GET /rest/v1/tools/{toolName} One tool's schema — the same object the catalog lists. #
POST /rest/v1/tools/{toolName} Invoke a tool. The body is a JSON object of named parameters. #

Specifications

⚙
OpenAPI
https://artifacts.apis.io/eesier-com/openapi/_ae-authored/eesier-com-openapi-generated.yml

Schemas & Data

📊
JSONSchema
https://artifacts.apis.io/eesier-com/json-schema/eesier-com-get-rest-v1-tools-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/eesier-com/json-schema/eesier-com-post-rest-v1-tools-toolname-request-schema.json
📊
JSONSchema
https://artifacts.apis.io/eesier-com/json-schema/eesier-com-get-rest-v1-tools-toolname-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/eesier-com/json-schema/eesier-com-get-rest-v1-call-toolname-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/eesier-com/json-schema/eesier-com-post-rest-v1-tools-toolname-response-schema.json

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/eesier-com:eesier-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.

GitHub Google LinkedIn

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

OpenAPI Specification

eesier-com-openapi-generated.yml Raw ↑ 
openapi: 3.1.0
info:
  title: eesier API
  version: '2026-11-06'
  description: 'GENERATED FROM DOCUMENTATION by API Evangelist on 2026-11-06: 4 operation(s) read from 1 public documentation page(s) (each operation
    names its page in x-source). This is not the provider''s published contract; eesier has published no machine-readable contract that the pipeline
    could find. Engine: local.'
  x-evidence-tiers:
    code-example: 3
    documentation: 1
    pages-with-code: 1
    pages-read: 1
  x-generated-from: documentation
  x-provenance: generated
  x-authored-by: API Evangelist
  x-generated: '2026-11-06'
  x-generator: generate-contract-from-docs.py
  x-engine: local
  x-sources:
  - https://eesier.com/rest
servers:
- url: https://mcp.eesier.com
paths:
  /rest/v1/call/{toolName}:
    get:
      operationId: get_rest_v1_call_toolName
      tags:
      - Rest
      summary: Invoke a read-only tool from the query string. Any other tool returns 405.
      x-source: https://eesier.com/rest
      parameters:
      - name: toolName
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Success (status as documented)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GetRestV1CallToolnameResponse'
      x-evidence:
        kind: documentation
  /rest/v1/tools:
    get:
      operationId: get_rest_v1_tools
      tags:
      - Rest
      summary: GET /rest/v1/tools
      x-source: https://eesier.com/rest
      responses:
        '200':
          description: Success (shape read from the example response on the page)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GetRestV1ToolsResponse'
      x-evidence:
        kind: code-example
        language: curl
        snippet: "curl https://mcp.eesier.com/rest/v1/tools  -H \"Authorization: Bearer $EESIER_TOKEN\" \n The machine-readable version of this\
          \ page, straight from the running server. \n A tool with no parameters takes no body at all — an absent body, {} and null all mean \"\
          no arguments\". \n the endpoints \n Four routes. Everything else is a tool name. \n POST \n /rest/v1/tools/{tool_name} \n Invoke a tool.\
          \ The body is a JSO"
  /rest/v1/tools/{toolName}:
    get:
      operationId: get_rest_v1_tools_toolName
      tags:
      - Rest
      summary: One tool's schema — the same object the catalog lists.
      x-source: https://eesier.com/rest
      parameters:
      - name: toolName
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Success (status as documented)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GetRestV1ToolsToolnameResponse'
      x-evidence:
        kind: documentation
    post:
      operationId: post_rest_v1_tools_toolName
      tags:
      - Rest
      summary: Invoke a tool. The body is a JSON object of named parameters.
      x-source: https://eesier.com/rest
      parameters:
      - name: toolName
        in: path
        required: true
        schema:
          type: string
      requestBody:
        required: false
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PostRestV1ToolsToolnameRequest'
      responses:
        '201':
          description: Success (status as documented)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PostRestV1ToolsToolnameResponse'
      x-evidence:
        kind: documentation
components:
  schemas:
    GetRestV1CallToolnameResponse:
      type: object
      properties:
        tool JSON:
          type: object
    GetRestV1ToolsResponse:
      type: object
      properties:
        error:
          type: string
        how_to_fix:
          type: string
        documentation:
          type: string
    GetRestV1ToolsToolnameResponse:
      type: object
      properties:
        tool schema:
          type: object
    PostRestV1ToolsToolnameRequest:
      type: object
      properties:
        named parameters:
          type: object
    PostRestV1ToolsToolnameResponse:
      type: object
      properties:
        tool JSON:
          type: object
  securitySchemes:
    bearer:
      type: http
      scheme: bearer
security:
- bearer: []
tags:
- name: Rest