Agent-ready OpenAPI document · curated by JenticIOTDevice ManagementapiKey129 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Provision sites, manage access rules and entry points, send invitations, and read entry-point logs across a Kindoo access-control deployment.
Use for: Authenticate against Kindoo and capture a SessionTokenID, Create a new site with the address and contact details, Add an access rule to a site for a specific entry point, List the currently active API sessions on my Kindoo account
Not supported: Does not handle billing, video surveillance, or building HVAC - use for Kindoo site provisioning, access rules, entry points, and session management only.
Jentic publishes the only available OpenAPI specification for Kindoo.Tech, keeping it validated and agent-ready. Kindoo is an access-control and smart-property platform whose API exposes sites (called environments), entry points, access rules, users, agents, licenses, and the session lifecycle that authorizes every request. The 129-endpoint surface covers creating sites, configuring access rules, customising invitation emails per language, retrieving entry-point logs, and managing the SessionTokenID issued by ApiLogin. Use it to wire access control into property management or guest workflow systems.
Install Jentic One Beta
Connect the Kindoo.Tech to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Kindoo.Tech, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fkindoo.tech%2Fkindoo" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fkindoo.tech%2Fkindoo" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Kindoo.Tech API.
Authenticate against Kindoo with ApiLogin and manage the resulting SessionTokenID
Create and edit sites (environments) with property metadata and contact details
Configure access rules and bind them to entry points
Customise invitation emails per language for both new and existing Kindoo users
Retrieve entry-point logs for a site, user, or rule
List and manage active API sessions, including killing one or all sessions
Search agents and assign them to a site during creation
Use Cases
Patterns agents use Kindoo.Tech API for, with concrete tasks.
★ Provision a new managed property
When a property manager onboards a new building, an integration can call POST /ApiLogin, then POST /KindooSaveEnvironmentNewWithoutType with the property details and the agent ID returned by KindooSearchAgents. The site is then ready for entry-point and rule configuration.
Authenticate with /ApiLogin, search for the right agent with /KindooSearchAgents, then POST /KindooSaveEnvironmentNewWithoutType with the property details.
Per-language invitation customisation
Operations teams can pull the available languages with POST /KindooGetAvailableLanguages and the keyword list with POST /KindooGetSiteInvitationEmailKeywords, then customise the invitation email for an existing or new Kindoo user. The same surface lets them remove a custom email and revert to Kindoo's default.
Call POST /KindooGetAvailableLanguages, then POST /KindooGetSiteInvitationVerifiedKindooUserEmailByLanguage for the chosen language and update the email body.
Entry-point log review
Security and operations teams can call POST /KindooGetSiteUserEntryPointLogs to retrieve the logs for an entry point, a specific user, or all access events on a site. Combined with POST /KindooGetEnvRuleWithEntryPoints the team can correlate access events with the rules that authorised them.
Call POST /KindooGetSiteUserEntryPointLogs with the site ID and date range and write the results to a daily security report.
Session hygiene
If an integration suspects a stale or compromised SessionTokenID, it can call POST /KindooGetAPISessions to inspect active sessions and POST /KillAllApiSessions or POST /KillMySession to invalidate them. This keeps the access-control plane locked down without rotating the underlying credentials.
List sessions via /KindooGetAPISessions and POST /KillAllApiSessions if more than one unexpected session is active.
Agent integration via Jentic
An access-control agent can use Jentic to discover the Kindoo login and site-creation operations, load their schemas, and execute them in sequence. The SessionTokenID is held in vault context, so the agent never sees the raw value once it has been issued.
Search Jentic for 'create a Kindoo site', load POST /ApiLogin and POST /KindooSaveEnvironmentNewWithoutType, and execute them in order.
Key Endpoints
129 endpoints — jentic publishes the only available openapi specification for kindoo.
METHOD
PATH
DESCRIPTION
POST
/ApiLogin
Authenticate and receive a SessionTokenID
POST
/KindooSaveEnvironmentNewWithoutType
Create a new site
POST
/KindooSaveEnvironment
Edit site details
POST
/KindooGetEnvironments
List or read environment objects
POST
/KindooGetSiteUserEntryPointLogs
Read entry-point logs
POST
/KindooGetEnvironmentRules
List access rules for a site
POST
/KillAllApiSessions
Invalidate all active sessions
POST
/KindooSearchAgents
Find an agent ID before creating a site
POST
/ApiLogin
Authenticate and receive a SessionTokenID
POST
/KindooSaveEnvironmentNewWithoutType
Create a new site
POST
/KindooSaveEnvironment
Edit site details
POST
/KindooGetEnvironments
List or read environment objects
POST
/KindooGetSiteUserEntryPointLogs
Read entry-point logs
POST
/KindooGetEnvironmentRules
List access rules for a site
POST
/KillAllApiSessions
Invalidate all active sessions
POST
/KindooSearchAgents
Find an agent ID before creating a site
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
K
Kindoo.Tech
- Non-Ready (F)38/100
43
Foundational Compliance41
Developer Experience & Jentic Compatibility19
AI-Readiness & Agent Experience75
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
43
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: DSignals: 4
74%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
41
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: D-Signals: 4
1%
Example Density
How richly the API is illustrated with examples.
14%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
19
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
27%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
1%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
75
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A-Signals: 1
75%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Kindoo.Tech by hand means logging in for a SessionTokenID, replaying it on every SOAP-style POST to the webservice.asmx host, and managing session teardown yourself. Through Jentic you install once, import Kindoo.Tech from the API Directory, store the credential once, and your agent calls it.
Permission scoping
Kindoo.Tech drives everything through POST operations that carry the site and environment targets in the request body rather than as a URL path resource, so scope by operation: limit the agent to the operations it needs, such as reading environments or entry-point logs, and leave session-killing or rule changes out unless you add them.
Credential isolation
Your Kindoo.Tech credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list Kindoo site environments' or 'read entry-point access logs', and Jentic returns the matching Kindoo.Tech operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Kindoo.Tech API through Jentic.
Why is there no official OpenAPI spec for Kindoo.Tech?
Kindoo does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Kindoo.Tech via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Kindoo.Tech API use?
Authentication is two-step: call POST /ApiLogin to obtain a SessionTokenID, then send that value in the SessionTokenID header on every subsequent request. Jentic stores the login credentials in the vault and manages the session token internally.
Can I create a new site with the Kindoo.Tech API?
Yes. After ApiLogin, call POST /KindooSearchAgents to get the right agent ID, then POST /KindooSaveEnvironmentNewWithoutType with the property name, contact details, and description. Edit the site later with POST /KindooSaveEnvironment.
What are the rate limits for the Kindoo.Tech API?
The OpenAPI specification does not declare explicit rate limits across the 129 endpoints. Reuse a single SessionTokenID across calls rather than logging in for every request, and call POST /KindooGetAPISessions if you need to inspect concurrent session counts.
How do I read entry-point logs with the Kindoo.Tech API through Jentic?
Run pip install jentic, search Jentic for 'read Kindoo entry point logs', load the POST /KindooGetSiteUserEntryPointLogs operation, and execute it with the site ID and date range. Jentic handles the ApiLogin step and supplies the SessionTokenID header.
Can I limit what my agent is allowed to do with the Kindoo.Tech API?
Yes. Because Jentic One is self-hosted, you decide which of the 129 Kindoo operations your agent may call, and your own rules are enforced at execution time. Kindoo carries its site and environment targets in the request body rather than in the URL, so you scope by operation: grant read-only calls like POST /KindooGetEnvironments or POST /KindooGetSiteUserEntryPointLogs while withholding write and destructive ones such as POST /KindooSaveEnvironment, rule changes, or POST /KillAllApiSessions. The credential is held by your own instance and injected only for the operations you have allowed, so the agent can never reach beyond that set.
GET STARTED