datavessel API

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

Operations 5

GET /djr4/datavessel-cli/main/skills/datavessel/SKILL.md GET /djr4/datavessel-cli/main/skills/datavessel/SKILL.md #
GET /v1/auth/me Who the key belongs to. #
POST /v1/providers/execute POST /v1/providers/execute #
GET /v1/tools The full tool catalogue with every parameter schema. #
GET /v1/users/me/usage Plan, tool calls used this period and what is left. #

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/datavessel-io:datavessel-io-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

datavessel-io-openapi-generated.yml Raw ↑
openapi: 3.1.0
info:
  title: datavessel API
  version: '2026-11-05'
  description: 'GENERATED FROM DOCUMENTATION by API Evangelist on 2026-11-05: 5 operation(s) read from 3 public documentation page(s) (each operation
    names its page in x-source). This is not the provider''s published contract; datavessel has published no machine-readable contract that the
    pipeline could find. Engine: local.'
  x-evidence-tiers:
    code-example: 2
    documentation: 3
    pages-with-code: 3
    pages-read: 3
  x-generated-from: documentation
  x-provenance: generated
  x-authored-by: API Evangelist
  x-generated: '2026-11-05'
  x-generator: generate-contract-from-docs.py
  x-engine: local
  x-sources:
  - https://datavessel.io/docs
  - https://datavessel.io/cli
  - https://datavessel.io/de/cli
servers:
- url: https://api.datavessel.io
paths:
  /djr4/datavessel-cli/main/skills/datavessel/SKILL.md:
    get:
      operationId: get_djr4_datavessel_cli_main_skills_datavessel_SKILL_md
      tags:
      - Djr4
      summary: GET /djr4/datavessel-cli/main/skills/datavessel/SKILL.md
      x-source: https://datavessel.io/cli
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: code-example
        language: curl
        snippet: curl -sL https://raw.githubusercontent.com/djr4/datavessel-cli/main/skills/datavessel/SKILL.md  -o .cursor/rules/datavessel.mdc
          Building on the Claude Agent SDK or the API instead? Give the model a shell tool, add SKILL.md to its context, and authenticate headless
          with DATAVESSEL_TOKEN . The CLI's stable --json output and exit codes are built for it. One command away. terminal $ npm i -g datavesse
  /v1/auth/me:
    get:
      operationId: get_v1_auth_me
      tags:
      - Auth
      summary: Who the key belongs to.
      x-source: https://datavessel.io/docs
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /v1/providers/execute:
    post:
      operationId: post_v1_providers_execute
      tags:
      - Providers
      summary: POST /v1/providers/execute
      x-source: https://datavessel.io/docs
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PostV1ProvidersExecuteRequest'
      responses:
        '201':
          description: Success (status as documented)
      x-evidence:
        kind: code-example
        language: curl
        snippet: 'curl https://api.datavessel.io/v1/providers/execute  -H "X-API-Key: $DATAVESSEL_API_KEY"  -H "Content-Type: application/json"  -d
          ''{"tool_name": "get_top_queries", "params": {"site_url": "https://shop.example.com", "limit": 10}}'' Copy The catalogue Every tool,
          in plain English. What follows is the surface area your agent sees. Connect a source and link it to your store, and these tools become
          avai'
  /v1/tools:
    get:
      operationId: get_v1_tools
      tags:
      - Tools
      summary: The full tool catalogue with every parameter schema.
      x-source: https://datavessel.io/docs
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /v1/users/me/usage:
    get:
      operationId: get_v1_users_me_usage
      tags:
      - Users
      summary: Plan, tool calls used this period and what is left.
      x-source: https://datavessel.io/docs
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
components:
  schemas:
    PostV1ProvidersExecuteRequest:
      type: object
      properties:
        tool_name:
          type: string
        params:
          type: object
          properties:
            site_url:
              type: string
            limit:
              type: integer
  securitySchemes:
    apiKey:
      type: apiKey
      in: header
      name: X-API-Key
security:
- apiKey: []
tags:
- name: Auth
- name: Djr4
- name: Providers
- name: Tools
- name: Users