gnt.ai Brain API
The brain API from gnt.ai — 2 operation(s) for brain.
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/gntai-dev:gntai-dev-brain-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: AI GNT Brain API
version: 0.1.0
servers:
- url: https://api.gntai.dev
description: Production
tags:
- name: brain
paths:
/v1/brain/summary:
get:
tags:
- brain
summary: Brain Summary
operationId: brain_summary_v1_brain_summary_get
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
security:
- HTTPBearer: []
/v1/onboarding/status:
get:
tags:
- brain
summary: Onboarding Status
description: 'This org''s onboarding progress — "how close is this org to a working
setup" — aggregated off onboarding_events (gnt/onboarding_metrics.py).
Planned future ROI metering will read off the same table, so counts
stay a flat event_type -> count map here rather than baking in today''s
five known types.
connected_cli isn''t an onboarding_event (gnt login has no event-log
call site, unlike the Slack/GitHub connect routes and rule proposal) —
it''s read straight off mcp_api_keys instead. A CLI key, once minted,
always stays a row here even if later revoked, so this answers "has
this org ever completed gnt login", not "is a CLI key live right now".
apps/web/components/onboarding-status.tsx polls this for the /welcome
page''s live step checklist.
reached_five_rules_milestone is this product''s "org reaches N approved
rules in first session" success metric, N=5 — derived straight off
the same counts, not a second query,
since rules_approved already is that lifetime-cumulative count (see
onboarding_metrics.RULES_APPROVED_MILESTONE for why that''s an
accurate proxy for "first session" here).'
operationId: onboarding_status_v1_onboarding_status_get
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
security:
- HTTPBearer: []
components:
securitySchemes:
HTTPBearer:
type: http
scheme: bearer