Serves the canonical model of the last build over HTTP, for the service screens and for the tools that cannot read model.json. Nothing of it exists in this version. The contract lists three operations, which the contract import matches to the operation notes; the suggestion review screen is declared as a consumer although it works on the lock file directly, which the consumer mismatch check reports.
Model query API
APISpace specs
Operations
Matched to the contract by operation name. The rows in italics are gaps: present in the contract without a page, or described without existing in the contract.
| Method | Path | Operation | Callers |
|---|---|---|---|
| GET | /entities | List the entities | 3 callers |
| GET | /entities/{id} | Read an entity | 1 caller |
| GET | /search | Search the model | 1 caller |
| GET | /findings | GET /findings | present in the contract, without a page |
unknown path | Suggest links | described, absent from the contract |
Interface contract
No schema is copied into the text: the page shows the contract, it does not duplicate it.
Properties5
- Protocol
- rest
- Exposure
- apim
- Version
- 0
- Status
- target
- Contract
- contracts/model-query.openapi.json
Five keys, no more. The operations come from the contract, not from the header.
See the neighbourhood map6 pages6Neighbourhood mapModel query API
Neighbourhood map Model query API
Distance1 hop
9 neighbours in total, more than the map shows.
The 6 neighbourstextual equivalent
- List the entitiesOperationexposes3
- Read an entityOperationexposes1
- Search the modelOperationexposes1
- Document viewerScreenserves2
- Pinned trailScreenserves2
- EntityBusiness objectaccesses3
Six neighbours at most, always named. Beyond that the map teaches nothing: the list takes over.