Trufla
Trufla Technology is a Calgary, Alberta insurtech that builds digital distribution software for independent property and casualty insurance brokerages, serving 300+ brokerages primarily across Canada with some UK clients. Founded in 2018 by Sherif Gemayel out of Sharp Insurance's in-house tooling (SharpMobile plus the E-Method digital agency), Trufla sells a broker-channel suite rather than underwriting risk itself: truWeb for broker websites, SEO and digital marketing; truMarket, an insurance CRM with a "Quote Bind Issue" rating workflow, lead management, an app store and a marketplace; truMobile, a customer self-service app and broker portal with policy access, document delivery, claim reporting and a marketplace for auxiliary products such as travel, roadside and pet; DataHub with the Policy KPI Dashboard and AI Retention X-Ray; Trudi, an AI insurance assistant; and PolicyPro, a contracted back-office outsourcing service. Its API posture is entirely partner-gated and inbound. Trufla publishes no public developer portal and no self-serve API — developer.trufla.com, developers.trufla.com, docs.trufla.com and api.trufla.com do not resolve (NXDOMAIN), and every OpenAPI, Swagger, GraphQL and API-docs path probed on www.trufla.com returns 404. Integration happens the way it does across the Canadian broker channel: through broker management system connectors (Acturis, Power Broker, Vertafore, Applied Epic/TAM), Salesforce, SEH Systems, telephony, e-signature and payment apps subscribed from the truMarket app store, and through a CSIO implementation step during onboarding. Trufla makes no reference to ACORD, AL3 or IVANS anywhere on its public site; CSIO — Canada's insurance data-standards body — is the standards seam here, and Trufla's own terms of service require the brokerage client to supply its own CSIO account and mailbox plus its own insurer contracts and APIs. What Trufla does publish machine-readably sits outside the developer surface entirely: an llms.txt at www.trufla.com/llms.txt that licenses AI summarization while forbidding training and pricing extraction, a SafeBase trust center at trust.trufla.com that names AWS as its sole subprocessor and no completed certification, dated per-product release notes, a GitHub organization at trufla-technology holding only forks, and one first-party npm package, the Angular JSON-Schema form library @trufla/ngx-tru-forms.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Trufla the way a machine reads it — 3 machine-readable artifacts, 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 — Trufla scores 24.2/100 (emerging), with a separate agent-readiness read of 0/100 (human only). 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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Trufla
Each block below is one kind of artifact we hold for Trufla. 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.
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.
Resources
Every other property we hold for Trufla — 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 1
Portal, sign-up, and the first successful call
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 6
The organization behind the API
Other 5
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/trufla · machine-readable index on apis.io