How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

ydb-qdrant-tech MCP API

Streamable HTTP MCP transport.

ydb-qdrant-tech MCP API is one of 10 APIs that ydb-qdrant-tech publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 18 JSON Schema definitions.

Tagged areas include MCP. The published artifact set on APIs.io includes an OpenAPI specification and 18 JSON Schemas.

This API exposes 14 operations across 11 paths, and defines 11 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://gravity-ai.ydb-qdrant.tech, https://pets.ydb-qdrant.tech.

14 operations 11 paths 11 schemas 1 DELETE10 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://gravity-ai.ydb-qdrant.tech
Authentication
OAuth 2.0, API Key, HTTP Basic
Resource Areas
1

Authentication & Security 3

ydb-qdrant-tech MCP API declares 3 security schemes for authenticating requests. It supports OAuth 2.0 (OAuth2Metadata) using the authorizationCode flow, exposing 2 scopes. An API key is passed in the cookie as codex_pets_session (AppSessionCookie). It accepts HTTP basic authentication (ProxyBasic).

  • OAuth2Metadata — Discovery metadata is published for agent compatibility. Token issuance is disabled in the current public demo.
  • AppSessionCookie — Optional app-session cookie used by browser account flows. Public read endpoints do not require it.
  • ProxyBasic — Deployment mode for trusted reverse proxies. Public agent endpoints are designed to be readable without credentials.

Paths & Operations 14

Across 11 paths, the API surfaces 14 operations — 1 DELETE, 10 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

MCP 14

Streamable HTTP MCP transport.

GET
/mcp
Reject unsupported MCP method
rejectMcpGet → 405
POST
/mcp
Call the Gravity AI UI MCP server
callMcpServer 1 param body → 200403500
DELETE
/mcp
Reject unsupported MCP method
rejectMcpDelete → 405
POST
/.well-known/mcp
Call the Gravity AI UI MCP server
callWellKnownMcpServer 1 param body → 200403500
GET
/.well-known/mcp
Fetch the Gravity AI UI MCP server card
getWellKnownMcpServerCard → 200
GET
/.well-known/mcp.json
Fetch MCP well-known compatibility metadata
getMcpWellKnownDocument → 200
GET
/mcp.md
Get markdown MCP server guide
getMcpMarkdown → 200
GET
/.well-known/oauth-protected-resource/mcp
Get OAuth Protected Resource metadata for the MCP endpoint
getMcpOAuthProtectedResourceMetadata → 200
GET
/server.json
Get MCP Registry server metadata
getMcpRegistryServer → 200
GET
/.well-known/mcp/server.json
Get well-known MCP Registry server metadata
getWellKnownMcpRegistryServer → 200
GET
/.well-known/mcp/server-card.json
Get Codex Pets MCP server card
getMcpServerCard → 200
POST
/api/pet-generations
Start an anonymous server-paid pet generation
generatePet body → 202400403409413429503
GET
/api/pet-generations/{id}
Read an unlisted generation by its private ID
getPetGeneration 1 param → 200404410503
GET
/api/pet-generations/{id}/files/{file}
Download an unlisted completed generation before expiry
getPetGenerationFile 2 params → 200404410503

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are McpWellKnownDocument (11 properties), McpServerCard (8 properties), OAuthProtectedResourceMetadata (8 properties), ErrorResponse (5 properties). Each schema is shown below with its type and property counts.

JsonRpcResponse
object
4 properties 1 required
McpServerCard
object
8 properties 8 required
McpWellKnownDocument
object
11 properties 11 required
JsonRpcRequest
object
4 properties 2 required
McpRegistryServer
object
JsonRpcResponse_2
object
McpServerCard_2
object
JsonRpcErrorResponse
object
3 properties 3 required
OAuthProtectedResourceMetadata
object
8 properties 8 required
ErrorResponse
object
5 properties 3 required
JsonRpcRequest_2
object

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ydb-qdrant-tech-mcp-api-openapi.yml Raw ↑

Other APIs ydb-qdrant-tech publishes across the network.

ydb-qdrant-tech Agent API
ydb-qdrant-tech Collections API
ydb-qdrant-tech Discovery API
ydb-qdrant-tech Feedback API
ydb-qdrant-tech Pets API
ydb-qdrant-tech Points API
ydb-qdrant-tech Requests API
ydb-qdrant-tech Service API
ydb-qdrant-tech Submissions API
Where this information came from

This is an independent, third-party profile of ydb-qdrant-tech MCP API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.