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/ask-sage:ask-sage-memos-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
openapi: 3.2.0
info:
title: Ask Sage User API — Full Response Reference Memos API
description: 'Ask Sage User API for account management, organization administration, billing, and platform configuration.
## Base URL
`https://api.asksage.ai/user`
## Authentication
Most endpoints require a valid JWT token sent in the `x-access-tokens` HTTP header. Secured endpoints show a padlock in Swagger UI / Redoc — click **Authorize** and paste your token once to apply it to every request.
Get a token from `/get-token-with-api-key` (your email + 64-character API key), then send it on each call:
`x-access-tokens: `
**No token required:** `/get-token-with-api-key`, `/register`, `/verify-email`, `/lost-pass`, and `GET /get-headers`.
Beyond a valid token, admin (`admin-*`) and superadmin (`superadmin-*`) endpoints require the caller to hold the matching role, and many identify the target user via an `email` field in the request body.
## Key Features
- **User Management** — Profile updates, API key management, login history
- **Chat Sessions** — Create, retrieve, and manage conversation history
- **Dataset Management** — Create datasets, manage permissions and assignments
- **Workbooks** — Organize research with sources and memos
- **Organization Admin** — User management, token allocation, usage reporting
- **Superadmin** — Platform-wide administration and analytics'
version: '2.0'
contact:
name: Support
email: support@asksage.ai
url: https://asksage.ai
servers:
- url: '{baseUrl}/user'
description: Ask Sage User API
variables:
baseUrl:
default: https://api.asksage.ai
description: API base URL. Use https://api.asksage.ai for production, or your self-hosted instance URL.
security:
- ApiKeyAuth: []
tags:
- name: Memos
description: Memo management within workbooks
paths:
/memo:
put:
summary: Add memo to workbook
tags:
- Memos
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- content
- title
- type
- workbook_id
properties:
workbook_id:
type: integer
description: Numeric id of the workbook the memo is added to; caller must have access to it.
type:
type: string
description: 'Kind of memo: ''response'' for a memo generated from a model response, or ''written'' for a user-authored memo.'
enum:
- response
- written
title:
type: string
description: Title of the memo; required and must be non-empty.
minLength: 1
content:
type: string
description: Body text of the memo; required and must be non-empty.
minLength: 1
references:
type: string
default: ''
description: Optional references associated with the memo (e.g. citation/source references), stored as text.
references_descriptions:
type: string
default: ''
description: Optional human-readable descriptions for the memo's references, stored as text.
responses:
'200':
description: Memo added to workbook
content:
application/json:
schema:
type: object
properties:
response:
type: string
description: Literal 'OK'
status:
type: integer
example: 200
'400':
description: 'Bot disabled, server issue, or ''Contact customer support'' service error (envelope status 400). NOTE: this outcome is returned with HTTP 200; the code appears only in the JSON body ''status'' field.'
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
example:
response: Bad request
status: 400
'404':
description: 'Workbook not found or not owned by user (envelope status 404). NOTE: this outcome is returned with HTTP 200; the code appears only in the JSON body ''status'' field.'
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
example:
response: Not found
status: 404
'408':
description: 'Missing required fields or invalid type (envelope status 408). NOTE: this outcome is returned with HTTP 200; the code appears only in the JSON body ''status'' field.'
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
example:
response: Error
status: 408
operationId: putMemo
x-operation-id-source: derived
delete:
summary: Delete memo
tags:
- Memos
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- memo_id
properties:
memo_id:
type: integer
description: Numeric id of the memo to delete; caller must be owner or organization admin of the workbook the memo belongs to.
responses:
'200':
description: Memo deleted
content:
application/json:
schema:
type: object
properties:
response:
type: string
description: Literal 'Memo deleted successfully'
status:
type: integer
example: 200
'400':
description: 'Bot disabled, server issue, or ''Contact customer support'' service error (envelope status 400). NOTE: this outcome is returned with HTTP 200; the code appears only in the JSON body ''status'' field.'
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
example:
response: Bad request
status: 400
'404':
description: 'Memo or workbook not found / not owned by user (envelope status 404). NOTE: this outcome is returned with HTTP 200; the code appears only in the JSON body ''status'' field.'
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
example:
response: Not found
status: 404
'407':
description: 'No owner/admin access (envelope status 407). NOTE: this outcome is returned with HTTP 200; the code appears only in the JSON body ''status'' field.'
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
example:
response: Error
status: 407
operationId: deleteMemo
x-operation-id-source: derived
/get-memos:
post:
summary: Get memos for workbook
tags:
- Memos
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- workbook_id
properties:
workbook_id:
type: integer
description: Numeric id of the workbook whose memos are returned; caller must have access to it.
responses:
'200':
description: List of memos for the workbook
content:
application/json:
schema:
type: object
properties:
response:
type: array
items:
type: object
properties:
id:
type: integer
example: 123
user_id:
type: integer
example: 123
workbook_id:
type: integer
date_time:
type: string
description: Timestamp serialized as string
example: '2026-01-01T00:00:00Z'
type:
type: string
title:
type: string
content:
type: string
references:
type: string
references_descriptions:
type: string
status:
type: integer
example: 200
'400':
description: 'Bot disabled or ''Server issue'' (envelope status 400). NOTE: this outcome is returned with HTTP 200; the code appears only in the JSON body ''status'' field.'
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
example:
response: Bad request
status: 400
operationId: postGetMemos
x-operation-id-source: derived
components:
schemas:
ErrorResponse:
type: object
description: Standard Ask Sage error envelope.
properties:
response:
type: string
description: Human-readable error message.
status:
type: integer
example: 400
description: HTTP-style status code (usually an integer; some endpoints return it as a numeric string).
securitySchemes:
ApiKeyAuth:
type: apiKey
in: header
name: x-access-tokens
description: JWT authentication token. Obtain a token by calling `/get-token-with-api-key` with your email and 64-character API key. Some admin and superadmin endpoints also require an email address in the request body to identify the target user.
x-provenance:
method: harvested
publisher: Ask Sage
source: https://docs.asksage.ai/api-docs/specs/user-api-spec.json
note: split by refine-openapis from the provider's own published document, verified by fetch (openapi/_original/*.fetch.json);
stamped by stamp-openapi-provenance.py (roadmap#793)