myBots Identity (OAuth 2.0 / OpenID Connect)

The myBots identity provider, running OpenIddict. This is the only surface in the estate that publishes a complete, anonymous, machine-readable contract: RFC 8414 authorization-server metadata and an OpenID Connect discovery document, both live at /.well-known/. It issues the bearer tokens the tenant API requires, advertising the authorization_code, client_credentials, password and refresh_token grants plus two non-standard grants (verification_token, session_token), with PKCE S256 supported.

GitHub

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/mybotspro:mybots-identity-oauth-20-openid-connect"
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.

API entry from apis.yml

apis.yml Raw ↑
name: myBots Identity (OAuth 2.0 / OpenID Connect)
description: 'The myBots identity provider, running OpenIddict. This is the only surface in the estate
  that publishes a complete, anonymous, machine-readable contract: RFC 8414 authorization-server metadata
  and an OpenID Connect discovery document, both live at /.well-known/. It issues the bearer tokens the
  tenant API requires, advertising the authorization_code, client_credentials, password and refresh_token
  grants plus two non-standard grants (verification_token, session_token), with PKCE S256 supported.'
humanURL: https://mybots.pro
baseURL: https://auth.mybots.pro
tags:
- Authentication
- OAuth
- OpenID Connect
tags_raw:
- Authentication
- OAuth
- OpenID Connect
properties:
- type: OpenIDConnect
  url: https://auth.mybots.pro/.well-known/openid-configuration
- type: Authentication
  url: authentication/mybotspro-authentication.yml
- type: OAuthScopes
  url: scopes/mybotspro-scopes.yml
- type: WellKnown
  url: well-known/mybotspro-well-known.yml