generated: '2026-08-23' method: searched source: https://site.imsglobal.org/certifications/kiddom-inc/kiddom note: >- Kiddom publishes no OpenAPI, so nothing here is derived from a contract. Every positive entry is backed by an active 1EdTech certification registry record for the product "Kiddom v1", plus a live probe of the LTI endpoints on api.kiddom.co. Read the roles carefully: for OneRoster, Kiddom is certified as a DATA CONSUMER, meaning it CALLS a district SIS/rostering provider's OneRoster REST service — it does not publish a OneRoster server of its own, and probes for /ims/oneroster/* on api.kiddom.co return 404. standards: - id: lti-advantage-1.3 name: 1EdTech LTI Advantage 1.3 (Tool) conforms: true role: tool certified: '2026-04-23' status: active services: - LTI v1.3 Core - Assignment and Grade Services 2.0 - Names and Role Provisioning Services 2.0 - Deep Linking 2.0 evidence: - kind: certification-registry url: https://site.imsglobal.org/certifications/kiddom-inc/kiddom detail: 'Kiddom v1, LTI Advantage 1.3, Tool, certified 2026-04-23, status Active' - kind: live-probe url: https://api.kiddom.co/lti/login status: 400 detail: >- Returns {"message":"bad request","code":"400"} to an unparameterized GET, while an invented path on the same host returns the Go router's plain-text "404 page not found" — so this is a live LTI OIDC login handler, not a catch-all. - kind: live-probe url: https://api.kiddom.co/lti/launch status: 400 detail: 'Same 400 JSON envelope; live launch/redirect handler.' - id: oneroster-1.1 name: 1EdTech OneRoster 1.1 REST (Data Consumer) conforms: true role: data-consumer certified: '2026-05-21' status: active services: - REST Data Consumer Rostering Core - REST Data Consumer Resources Core evidence: - kind: certification-registry url: https://site.imsglobal.org/certifications/kiddom-inc/kiddom detail: >- Kiddom v1, OneRoster 1.1, Data Consumer, certified 2026-05-21, status Active. Earlier consumer certifications 2024-05-13 and 2025-05-14 are listed Out of Date on the same page. - kind: provider-claim url: https://get.kiddom.co/rostering-and-integrations/ detail: '"Kiddom is 1EdTech, OneRoster 1.1, and LTI 1.3 Certified to support ClassLink rostering and SSO."' - kind: negative-probe url: https://api.kiddom.co/ims/oneroster/v1p1/orgs status: 404 detail: 'No OneRoster server is published by Kiddom; the certification is consumer-side.' - id: oidc name: OpenID Connect conforms: true evidence: >- LTI 1.3 launches are an OIDC third-party-initiated login; api.kiddom.co/lti/login is that endpoint. No OIDC discovery document is published (/.well-known/openid-configuration 404s on every Kiddom host), so the issuer metadata is exchanged out of band with each LMS platform. - id: oauth2 name: OAuth 2.0 conforms: false evidence: >- No OAuth authorization server, token endpoint, or scope reference is published. /oauth/token and /oauth/authorize on api.kiddom.co return 404, and /.well-known/oauth-authorization-server is absent. - id: rfc9457-problem-details name: RFC 9457 Problem Details conforms: false evidence: >- The only observable error body, {"message":"bad request","code":"400"} from the LTI endpoints, is a bespoke envelope served as application/json, not application/problem+json. - id: rfc9116-security-txt name: RFC 9116 security.txt conforms: false evidence: '/.well-known/security.txt returns 404 on www.kiddom.co, api.kiddom.co and app.kiddom.co.' - id: caliper name: 1EdTech Caliper Analytics conforms: false evidence: 'No Caliper certification on the 1EdTech registry entry and no event surface published.' - id: qti name: 1EdTech QTI conforms: false evidence: >- Kiddom ships a large assessment surface (question types, high-stakes testing item types) but holds no QTI certification on the registry and publishes no QTI import/export contract. - id: edfi name: Ed-Fi Data Standard conforms: false evidence: 'No Ed-Fi certification or endpoint found.' domain_standard: market: K-12 education technology standards_probed: - oneroster - lti - caliper - qti - edfi - oai-pmh finding: >- Kiddom is genuinely a 1EdTech interoperability participant — active LTI Advantage 1.3 Tool and OneRoster 1.1 Data Consumer certifications — but the conformance is asserted through the certification registry and live launch endpoints, NOT through a machine-readable contract Kiddom publishes. A district that already speaks LTI/OneRoster can integrate without a bespoke connector; a developer who wants to read the contract has nothing to read. first_party_specification: name: Open Academic Format (OAF) v0.0 DRAFT url: https://github.com/kiddom/open-academic-format spec_file: https://raw.githubusercontent.com/kiddom/open-academic-format/master/versions/00/oaf-00.md status: draft, repository archived detail: >- Kiddom authored and open-sourced a draft data format for describing academic content (curriculum, assignments, materials) with RFC 2119 conformance language and JSON structures. It is a real first-party specification, but it is a v0.0 draft with TODO sections, the repository is archived, and no Kiddom endpoint is documented as producing or consuming it.