Conxai
Conxai (CONXAI Technologies GmbH) is a Munich, Germany-based startup building a no-code, agentic AI platform purpose-built for the construction and AEC (architecture, engineering, construction) industry. The modular platform contextualizes fragmented project-lifecycle data — site photos and video, documents, CAD drawings and tender submissions — and turns it into actionable knowledge across three areas: transparency, automation, and knowledge management. Marquee products include SiteLens (real-time construction-site camera analysis, progress tracking and firestop detection) and DocNostic (document extraction, classification and workflow automation). Conxai exposes several REST APIs — a Customer/SiteLens API, a Docnostic document API, a Firestop API and a Production Tracking API — documented on ReadMe and secured with an X-Api-Key header (Docnostic also accepts a JWT bearer token). The company is backed by Earlybird, Pi Labs, Cemex Ventures, Zacua Ventures, Capricorn Partners and BayBG Venture Capital.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Conxai the way a machine reads it — 39 machine-readable artifacts across 4 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Conxai scores 40.7/100 (developing), with a separate agent-readiness read of 26/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Put this on your own site. The badge is drawn live from Conxai's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/conxai/"
title="Conxai on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/conxai.svg"
alt="Conxai Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/conxai/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/conxai/"
title="Conxai on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/conxai/card.svg"
alt="Conxai Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Conxai
Each block below is one kind of artifact we hold for Conxai. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 17
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Conxai annotations API
The annotations API from Conxai — 1 operation(s) for annotations.
Conxai camera API
The camera API from Conxai — 4 operation(s) for camera.
Conxai document-types API
The document-types API from Conxai — 4 operation(s) for document-types.
Conxai documents API
The documents API from Conxai — 26 operation(s) for documents.
Conxai exports API
The exports API from Conxai — 2 operation(s) for exports.
Conxai Images API
The Images API from Conxai — 2 operation(s) for images.
Conxai integrations API
The integrations API from Conxai — 5 operation(s) for integrations.
Conxai production_tracking API
The production_tracking API from Conxai — 4 operation(s) for production_tracking.
Conxai project API
The project API from Conxai — 5 operation(s) for project.
Conxai projects API
The projects API from Conxai — 2 operation(s) for projects.
Conxai samples API
The samples API from Conxai — 16 operation(s) for samples.
Conxai schema API
The schema API from Conxai — 1 operation(s) for schema.
Conxai summary-table API
The summary-table API from Conxai — 12 operation(s) for summary-table.
Conxai use-cases API
The use-cases API from Conxai — 6 operation(s) for use-cases.
Conxai users API
The users API from Conxai — 3 operation(s) for users.
Conxai workflow API
The workflow API from Conxai — 3 operation(s) for workflow.
Conxai workflow-table API
The workflow-table API from Conxai — 3 operation(s) for workflow-table.
Scroll within the panel for all 17 ·
Open Collections 18
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONCustomer annotations API
OPEN COLLECTIONCustomer annotations camera API
OPEN COLLECTIONCustomer annotations document-types API
OPEN COLLECTIONCustomer annotations documents API
OPEN COLLECTIONCustomer annotations exports API
OPEN COLLECTIONCustomer annotations Images API
OPEN COLLECTIONCustomer annotations integrations API
OPEN COLLECTIONCustomer annotations production_tracking API
OPEN COLLECTIONCustomer annotations project API
OPEN COLLECTIONCustomer annotations projects API
OPEN COLLECTIONCustomer annotations samples API
OPEN COLLECTIONCustomer annotations schema API
OPEN COLLECTIONCustomer annotations summary-table API
OPEN COLLECTIONCustomer annotations use-cases API
OPEN COLLECTIONCustomer annotations users API
OPEN COLLECTIONCustomer annotations workflow API
OPEN COLLECTIONCustomer annotations workflow-table API
OPEN COLLECTIONScroll within the panel for all 18 ·
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Conxai — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Access & Security 4
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/conxai · machine-readable index on apis.io
This is an independent, third-party profile of Conxai, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.