DOCUMENT API · V1
Query a document corpus through an API
Retrieve facts, relationships, conflicts, revision changes, and supporting source pages over HTTP.
CURL
curl https://api.mgenie.dev/v1/corpora/mx/query \
-H "Authorization: Bearer $MGENIE_KEY" \
-d '{ "question":
"Can B14 run firmware 7.3?" }'
{ "answer": false,
"requirement": "firmware >= 7.4",
"sources": [ "compatibility-matrix-v8#p17",
"service-bulletin-143#p2" ] }
Endpoints
{{ e.method }}
{{ e.path }}
{{ e.desc }}
Quickstart
01
Create an API key
Scoped per workspace. Revoke any time.
02
Import documentation
Point at a docs URL or upload PDFs. Products are identified automatically.
03
Query the model
Specifications, compatibility, changes, and answers with citations.
{{ codeSample }}
Webhooks
Webhooks fire after mGenie extracts and reconciles facts from a new document.
{{ w.event }}
{{ w.desc }}
POST https://yourapp.com/hooks/mgenie
{ "event": "product.updated",
"product": "MX900",
"changes": {
"facts_changed": 3,
"procedures_superseded": 1,
"rules_updated": 2
},
"source": "service-bulletin-143" }
RATE LIMIT
600 req/min
P50 LATENCY
180 ms
UPTIME 90D
99.98%
AUTH
Bearer keys · scoped