AEC Agent developer documentation
AEC Agent exposes its regulation libraries to AI agents through an MCP connector, signed in with OAuth 2.0, and through a versioned REST API.
MCP connector
Add https://aec-agent.spairl.si/api/mcp as a custom connector in Claude or ChatGPT. The connector speaks the Model Context Protocol over HTTP and offers tools to list the libraries you can open, search regulations, and fetch a clause record with its citation. Call it only for regulation questions: never send drawing contents or file names.
- MCP endpoint
- MCP server card - name, transport, authentication and tools, readable without connecting
Authentication
The connector uses OAuth 2.0 with PKCE and dynamic client registration. Clerk is the authorization server. Discover it from the protected resource metadata (RFC 9728) and then from the authorization server metadata (RFC 8414). Access follows your membership: you see only the libraries you have been given.
OpenAPI specifications
The REST API is versioned under /api/v1 and needs a bearer credential issued to an approved member, except the health check. Errors are JSON: an error object with a code, a status, a message and a hint. Start from the API index.
- API index - where the endpoints and documents are
- Whole API, one OpenAPI 3.1 document (JSON)
- Whole API, one OpenAPI 3.1 document (YAML)
- Evidence API (OpenAPI 3) - The versioned evidence and clause API under /api/v1.
- Regulation retrieval API (OpenAPI 3) - Library listing and graph retrieval under /api/v1/graphrag.
Getting access
Start on the free Sandbox plan, 1,000 requests a month: register, wait for approval, then connect. Builder and Scale are listed on the AEC Agent home page at aec-agent.spairl.si and are set up with you by our team. For those, or for integration questions, write to management@spairl.si.