Mitchell 1 Intent Registry Discovery API

Discovery endpoint (GET api/service/v1/discovery) that a partner application calls on startup to resolve the current RESTful URI patterns for the Web-Intent resources it needs, rather than hardcoding them. Confirmed on Mitchell 1's public sandbox API help index; production access requires an approved integration partner account.

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/mitchell1-intent-registry-discovery-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

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

API entry from apis.yml

apis.yml Raw ↑
aid: mitchell1:mitchell1-intent-registry-discovery-api
name: Mitchell 1 Intent Registry Discovery API
tags:
- Discovery
- Web-Intent
- Integration
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
humanURL: https://testintents.mitchell1.com/Help/Api
baseURL: https://testintents.mitchell1.com/api
properties:
- url: https://mitchell1.com/resources/api-request/
  type: Documentation
- url: https://testintents.mitchell1.com/Help/Api
  type: APIReference
description: Discovery endpoint (GET api/service/v1/discovery) that a partner application calls on startup
  to resolve the current RESTful URI patterns for the Web-Intent resources it needs, rather than hardcoding
  them. Confirmed on Mitchell 1's public sandbox API help index; production access requires an approved
  integration partner account.