Clerkie
Clerkie, operated by Henry Labs Inc. and founded in San Francisco in 2016, is an AI-powered debt management and loan-recovery platform serving both consumers and institutional lenders. The consumer side offers a conversational financial assistant for budgeting, debt negotiation, and personalized repayment planning, while the B2B side — marketed as Fiber, launched in 2021 and now sold on its own domain getfiber.ai — gives lenders, banks, credit unions, and collection agencies an AI-driven recovery suite spanning CRM, an inventory management system (IMS), an AI agent, omnichannel communications, borrower scoring, a self-service payment portal, and workflow automation. Clerkie markets a RESTful API and multi-currency payment processing for lenders to integrate loan portfolios, real-time reporting, and automated repayment arrangements, but publishes no public developer documentation, machine-readable API contract, or self-serve developer portal — integration is arranged through a sales conversation. The company has raised over $41M from Left Lane Capital, Flourish Ventures, Vestigo Ventures, and Citibank.
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 Clerkie the way a machine reads it — 2 machine-readable artifacts across 1 API, 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 — Clerkie scores 18.6/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.
Why this profile is thin
Clerkie markets a RESTful API to lenders on www.clerkie.io/lenders ("For developers, by developers") but ships no developer portal at all — docs.clerkie.io and developers.clerkie.io have no DNS, api.clerkie.io answers its root with a health payload and returns HTTP 500 on every documentation and discovery path, api.getfiber.ai returns 403 Forbidden on every path behind an AWS load balancer, and the only route to the API is a HubSpot "Contact Sales" form.
An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is Clerkie's to change: publishing the reference and a machine-readable spec at a public URL, while keeping key issuance behind whatever gate they like, would let an integrator evaluate the API before committing to a call.
What we probed
https://www.clerkie.io/lenders→ HTTP 200https://api.clerkie.io/openapi.json→ HTTP 500https://api.getfiber.ai/openapi.json→ HTTP 403https://www.getfiber.ai/docs→ HTTP 404https://share.hsforms.com/1EslFlOk3Q6Gc5rFLq26n1w5n2wx→ HTTP 200
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-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from Clerkie'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/clerkie/"
title="Clerkie on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/clerkie.svg"
alt="Clerkie Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/clerkie/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/clerkie/"
title="Clerkie on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/clerkie/card.svg"
alt="Clerkie 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 Clerkie
Each block below is one kind of artifact we hold for Clerkie. 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 1
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.
Clerkie API
RESTful API marketed to lenders for integrating loan portfolios with Clerkie's recovery platform — payment arrangement recommendations, multi-currency payment processing, delinq...
Security Posture 1
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 Clerkie — 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 2
Portal, sign-up, and the first successful call
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Access & Security 1
Authentication, authorization, and security posture
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/clerkie · machine-readable index on apis.io
This is an independent, third-party profile of Clerkie, 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.