Operations 2
2 of 2 operations are conformant: apis.io called them with no credentials and the responses matched this contract. Checked 2026-11-12. how this works · status file
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.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/codai-ro:codai-ro-discovery-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
openapi: 3.2.0
info:
title: Codai Ro Discovery API
version: '1'
description: 'Operations tagged Discovery across 2 of this provider''s published API definitions: codai-ro-auth-openapi.json, codai-ro-auth-openapi.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://auth.codai.ro
description: Production
security: []
tags:
- name: Discovery
description: Metadata and signing keys.
paths:
/.well-known/openid-configuration:
get:
operationId: getOpenIdConfiguration
tags:
- Discovery
summary: OpenID Provider metadata
description: 'Discovery document (OpenID Connect Discovery 1.0 + RFC 8414). Lists every endpoint,
the supported grant types, response types, client authentication methods, scopes,
claims, `S256` as the only PKCE method, `acr_values_supported`, and back-channel /
RP-initiated logout support. Cache it; it changes only on deploys.'
responses:
'200':
description: Provider metadata.
content:
application/json:
schema:
$ref: '#/components/schemas/OpenIdConfiguration'
servers:
- url: https://auth.codai.ro
description: Production
/jwks:
get:
operationId: getJwks
tags:
- Discovery
summary: Public signing keys (JWKS)
description: 'RS256 public keys used to sign ID tokens, JWT access tokens (MCP resource) and
back-channel logout tokens. Every non-revoked key is published so rotation never breaks
verification; the newest key signs. Match by `kid`.'
responses:
'200':
description: JSON Web Key Set.
content:
application/json:
schema:
$ref: '#/components/schemas/Jwks'
servers:
- url: https://auth.codai.ro
description: Production
components:
schemas:
Jwks:
type: object
title: JSON Web Key Set
required:
- keys
properties:
keys:
type: array
items:
type: object
required:
- kty
- kid
- use
- alg
- n
- e
properties:
kty:
type: string
const: RSA
kid:
type: string
use:
type: string
const: sig
alg:
type: string
const: RS256
n:
type: string
e:
type: string
OpenIdConfiguration:
type: object
title: OpenID Provider metadata
description: Subset of the discovery document that integrators rely on; the live document contains more keys.
required:
- issuer
- authorization_endpoint
- token_endpoint
- jwks_uri
- response_types_supported
- subject_types_supported
- id_token_signing_alg_values_supported
properties:
issuer:
type: string
format: uri
const: https://auth.codai.ro
authorization_endpoint:
type: string
format: uri
token_endpoint:
type: string
format: uri
userinfo_endpoint:
type: string
format: uri
jwks_uri:
type: string
format: uri
introspection_endpoint:
type: string
format: uri
revocation_endpoint:
type: string
format: uri
device_authorization_endpoint:
type: string
format: uri
end_session_endpoint:
type: string
format: uri
registration_endpoint:
type: string
format: uri
description: Dynamic client registration for public MCP clients (not documented here).
response_types_supported:
type: array
items:
type: string
grant_types_supported:
type: array
items:
type: string
token_endpoint_auth_methods_supported:
type: array
items:
type: string
scopes_supported:
type: array
items:
type: string
claims_supported:
type: array
items:
type: string
code_challenge_methods_supported:
type: array
items:
type: string
const: S256
acr_values_supported:
type: array
items:
type: string
subject_types_supported:
type: array
items:
type: string
id_token_signing_alg_values_supported:
type: array
items:
type: string
backchannel_logout_supported:
type: boolean
securitySchemes:
oauth2:
type: oauth2
description: codai OpenID Connect provider. PKCE `S256` required on the authorization code flow.
flows:
authorizationCode:
authorizationUrl: https://auth.codai.ro/auth
tokenUrl: https://auth.codai.ro/token
refreshUrl: https://auth.codai.ro/token
scopes:
openid: Verify your codai identity
profile: See your name and profile picture
email: See your email address
inference: Run AI inference through your codai account
keys:manage: Create and manage codai API keys on your behalf
usage:read: Read your codai usage statistics
subscriptions:read: Read your codai subscription plan
mcp: Use codai tools and memory from an MCP client
offline_access: Stay signed in on this device
deviceCode:
deviceAuthorizationUrl: https://auth.codai.ro/device/auth
tokenUrl: https://auth.codai.ro/token
scopes:
openid: Verify your codai identity
profile: See your name and profile picture
email: See your email address
inference: Run AI inference through your codai account
keys:manage: Create and manage codai API keys on your behalf
usage:read: Read your codai usage statistics
subscriptions:read: Read your codai subscription plan
mcp: Use codai tools and memory from an MCP client
offline_access: Stay signed in on this device
bearerAuth:
type: http
scheme: bearer
description: OAuth access token issued by `/token` (used by `/me` and `/connect/key`).
clientSecretBasic:
type: http
scheme: basic
description: '`client_secret_basic` client authentication. `client_secret_post` and `private_key_jwt` go in the form body instead; public clients send only `client_id`.'
x-refined-from:
- codai-ro-auth-openapi.json
- codai-ro-auth-openapi.yml