OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
MCP & Tooling

Monid

Monid is a connector layer that lets AI agents discover and call tools from multiple providers through a shared base URL and key. Its TypeScript repository defines a declarative format for provider authentication, endpoint requests, input schemas, and usage models.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Monid — OpenViST project profile in MCP & Tooling.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Monid when an agent needs to discover or call tools across providers through one connector interface, or when developers want to add integrations through a shared declarative framework.

Who it is for

  • Developers building AI agents that need access to tools from multiple providers.
  • Teams implementing or contributing provider connectors.
  • Agent builders who want endpoint discovery at call time rather than a fixed provider choice.

Documented uses

  • Discover candidate tool endpoints for a task across providers.
  • Inspect a provider endpoint’s contract and browse the compiled catalog.
  • Call a provider endpoint through the shared connector layer.
  • Describe and contribute a new provider integration using the repository’s connector format.
Before you choose

Requirements & limits

The public GitHub repository lists an MIT license. Its quickstart requires Deno 2.x. The README says real endpoint calls require the relevant vendor credential; live tests run only when provider credentials are available.

  • The README describes discover as ranking endpoints across the catalog and returning price, live health, observed p50 and p95 latency, and hints for cheaper or better-fitting choices.
  • Usage accounting is declared per connector and may be based on calls, returned results, or units such as characters or video seconds.
  • The repository separates provider definitions from endpoint definitions and uses recorded fixtures for replay tests.
  • A real provider call depends on that provider’s credentials; fixture-based replay tests do not require vendor keys.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Add a provider endpoint connector

Describe a provider and endpoint in Monid’s declarative connector format, then prepare the change for contribution.

Before you start

  • Deno 2.x
  • The Monid repository and its development guide
  • The provider’s API documentation
  • Provider credentials only if running gated live tests

Steps

  1. Read the Exa reference connector and the authoring guide in DEVELOPMENT.md.

  2. Define the provider’s identity, authentication, defaults, and usage model, then describe the endpoint, request, and input schema.

  3. Record and trim a response fixture with deno task record.

  4. Run deno task check && deno task test, then open a pull request.

Expected outcome

A declarative provider endpoint connector prepared for contribution; once merged, its endpoints are available to agents through catalog discovery.

Guide limitations

  • The repository says replay tests use fixtures and need no vendor keys; live tests run only when provider credentials are available.
  • This workflow describes connector authoring and contribution, not a guarantee that a provider integration will be accepted or work with every API.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
10 October 2026
Original website title
monid-ai/monid · Official homepage title · retained in its source language
How we review sourcesSuggest a correction