CubeNexus Inc User Info API

The User Info API from CubeNexus Inc — 1 operation(s) for user info.

Operations 1

GET /userinfo Get User Info #

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/cubenexus-inc:cubenexus-inc-user-info-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 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

cubenexus-inc-user-info-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Fast Userinfo API
  version: 0.1.0
tags:
- name: User Info
paths:
  /userinfo:
    get:
      summary: Get User Info
      description: 'Cached, off-loop wrapper. Kept as the single entry point so the endpoint and

        the internal `await get_user_info(...)` callers on the chat path share one cache.


        `refresh=1` bypasses the cache, which is what the client''s forceRefresh means --

        without it a server-side TTL would silently outlive an explicit client refresh.

        Declared as a plain `bool = False`, not `Query(default=False)`: the ~15 internal

        callers invoke this as an ordinary coroutine, and a Query object default is

        truthy, so every one of them would have skipped the cache.'
      operationId: get_user_info_userinfo_get
      security:
      - OAuth2PasswordBearer: []
      parameters:
      - name: refresh
        in: query
        required: false
        schema:
          type: boolean
          default: false
          title: Refresh
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - User Info
components:
  schemas:
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
            - type: string
            - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
      type: object
      required:
      - loc
      - msg
      - type
      title: ValidationError
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
  securitySchemes:
    OAuth2PasswordBearer:
      type: oauth2
      flows:
        password:
          scopes: {}
          tokenUrl: login