Developers
RMG Circular is API-first: every capability exists first as a versioned endpoint and an MCP tool, and the human interface consumes it. All of it is public, unauthenticated and rate limited.
REST API
GET /api/v1/health- Liveness check. Calls no upstream service.
GET /api/v1/company/{cui}- Romanian company data by CUI, from the ANAF public VAT-payer registry.
GET /api/v1/openapi.json- The OpenAPI 3.1 description, generated from the same definitions the code dispatches on.
Published data
Read endpoints over published data: countries, materials, routes, authorities, destinations, sources, mirrored official registers and operator data. Every fact carries its own source, its exact locator and its trust level. Draft and withheld data never appear. The complete, authoritative list is in the OpenAPI description.
GET /api/v1/countries- Published data
GET /api/v1/materials- Published data
GET /api/v1/routes- Published data
GET /api/v1/registries- Published data
GET /api/v1/operators/{cui}- Published data
MCP server
MCP endpoint over Streamable HTTP, stateless and unauthenticated. POST JSON-RPC to it. The tools call exactly the same modules as the REST API.
POST /mcp
For agents
Every page has a Markdown twin at the same path with a .md extension, and also answers the Accept: text/markdown header. See llms.txt for an overview.
Every response carries its source and the time the data was retrieved. Information only, not legal advice.