Ask Sage
Ask Sage is a secure, government- and defense-grade generative AI platform that gives regulated organizations access to a broad catalog of commercial and open large language models behind a strict compliance boundary (FedRAMP High, DoD Impact Level 5/6, CMMC, NIST 800-53, GDPR). Beyond chat, it offers retrieval over private datasets, agents and an Agent Builder, plugins, a Deep Agent, and Model Context Protocol (MCP) integrations for Microsoft 365, GitHub, and Box. The platform is exposed through two REST APIs — a Server API for core AI operations (models, completions, agents, datasets, training) and a User API for authentication, API keys, and dataset management — plus OpenAI-, Anthropic-, and Gemini-style compatibility endpoints and an official Python client.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Ask Sage the way a machine reads it — 37 machine-readable artifacts across 32 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Ask Sage scores 52.3/100 (developing), with a separate agent-readiness read of 65/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Ask Sage
Each block below is one kind of artifact we hold for Ask Sage. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 32
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Ask Sage Admin API
Admin operations for organization management
Ask Sage Agent Builder API
Agent builder workflow and agent management
Ask Sage Allocation API
Token allocation and distribution policies
Ask Sage API Key Management API
API key operations
Ask Sage Audio API
Audio processing (TTS/STT)
Ask Sage Authentication API
User authentication and authorization
Ask Sage Chat Management API
Chat session operations
Ask Sage Completions API
Text generation and completions
Ask Sage Configuration API
System configuration endpoints
Ask Sage Dataset Management API
Dataset operations and permissions
Ask Sage Datasets API
Knowledge dataset management
Ask Sage Deep Agent API
Deep agent operations
Ask Sage Execute Agent API
The Execute Agent API from Ask Sage — 1 operation(s) for execute agent.
Ask Sage Feedback API
User feedback operations
Ask Sage Files API
File processing and analysis
Ask Sage List Agents API
The List Agents API from Ask Sage — 1 operation(s) for list agents.
Ask Sage MCP Servers API
Model Context Protocol server management
Ask Sage Memos API
Memo management within workbooks
Ask Sage Models API
AI model management
Ask Sage Plugins API
Plugin execution and management
Ask Sage Sources API
Source management within workbooks
Ask Sage Superadmin API
Superadmin system operations
Ask Sage System API
System utilities and health checks
Ask Sage Tabular Data API
Tabular data ingestion and querying
Ask Sage Token Requests API
Token request and approval workflow
Ask Sage Training API
Model training and content ingestion
Ask Sage Usage API
Token usage tracking
Ask Sage User Information API
User data and logs
Ask Sage User Management API
User profile and settings management
Ask Sage Utilities API
Utility endpoints
Ask Sage Widgets API
Widget/bot management
Ask Sage Workbooks API
Workbook management
Scroll within the panel for all 32 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
ask-sage-mcp.yml
MCP SERVERSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Ask Sage — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/ask-sage · machine-readable index on apis.io