RouterPlus API
RouterPlus API as documented publicly: 27 operations. Contract generated from the documentation by API Evangelist (2026-10-29); not the provider's own document.
Operations 27
GET
/v1/chat/completions
Use the endpoint's model id in place of a catalog model id. Everything else stays the same: both surfaces (/v1/chat/completions and /v1/messages), streaming or not, and every reque
#
Specifications
Schemas & Data
JSONSchema
https://artifacts.apis.io/routerplus-com/json-schema/routerplus-com-get-v1-generation-response-schema.json
JSONSchema
https://artifacts.apis.io/routerplus-com/json-schema/routerplus-com-get-api-identity-workspaces-response-schema.json
JSONSchema
https://artifacts.apis.io/routerplus-com/json-schema/routerplus-com-get-api-identity-organizations-response-schema.json
JSONSchema
https://artifacts.apis.io/routerplus-com/json-schema/routerplus-com-get-api-identity-members-response-schema.json
JSONSchema
https://artifacts.apis.io/routerplus-com/json-schema/routerplus-com-get-v1-chat-completions-response-schema.json
JSONSchema
https://artifacts.apis.io/routerplus-com/json-schema/routerplus-com-post-api-identity-members-request-schema.json