How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Handle

Handle (Handle Inc., handle.com) is a San Francisco software company, founded in 2018 by Patrick Hogan, Blake Robertson, Lucas Azevedo and Chris Woodard, that builds financial-operations software for the construction industry. The Handle platform covers lien and notice management, automated lien-waiver exchange, full-service research and verification, automatic state-by-state compliance deadlines, job sheets, credit applications, collections and construction-native online payments, unified by what the company calls its Construction Data Graph. It is sold to material suppliers, equipment dealers and subcontractors — customers named on its own site include Ferguson, ABC Supply, US LBM, Oldcastle, EquipmentShare, The Home Depot, Cemex, Builders FirstSource, Vulcan, Heidelberg Materials, Herc Rentals and Floor & Decor. Handle markets ERP integrations ("Handle integrates with any ERP") and operates a real API host at api.handle.com, and its own status page monitors components named "Main Portal API" and "Payment Portal API", but it publishes no developer portal, no API reference, and no machine-readable specification of any kind; the only public route to the integration surface is a Contact Sales form. Handle is SOC 2 Type 1 and Type 2 compliant and publishes a Vanta-hosted trust center. It raised a $27M Series B led by Marbruck with Energize Capital, Suffolk Technologies, Liquid 2 Ventures, RXR, WEX and Amex Ventures participating.

human only

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.

Kin Score

API Evangelist profiles Handle the way a machine reads it — 5 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 — Handle scores 21.8/100 (emerging), with a separate agent-readiness read of 3/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.

Behind a wall

Why this profile is thin

Handle's ERP Integrations page promises "Handle integrates with any ERP" and its own status page has monitored a component named "Main Portal API" since 2023-02-08, but the page's only CTAs are a Contact Sales form and an "Explore the docs" button that links to the trust page rather than to any documentation — there is no developer portal (developers/docs/developer.handle.com do not resolve) and api.handle.com answers unauthenticated callers with nothing but a JSON route hint, {"message":"specify a valid api route like {/api/integrations/{integration_name}/{action}"}.

An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is Handle'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.handle.com/erp-integrations/HTTP 200
  • https://www.handle.com/contact-sales/HTTP 200
  • https://api.handle.com/apiHTTP 404
  • https://api.handle.com/openapi.jsonHTTP 404
  • https://www.handle.com/developersHTTP 404
  • https://developers.handle.com/HTTP 0
  • https://docs.handle.com/HTTP 0
  • https://handle.statuspage.io/api/v2/components.jsonHTTP 200

Checked 2026-08-22. If this is out of date, tell us on the provider's repo and we will re-run the profile.

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 Kin Score How this is scored →
scored 2026-08-24 · rubric v0.12.1
Composite quality — 21.8/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 1.0 / 20
Access Clarity 7.4 / 20
Operational Transparency 3.4 / 13
Contract Governance 2.2 / 12
Discoverability 5.7 / 10
Regulatory · Payments 7.0 / 15
Agent readiness — 3/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling documented 3.5 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Handle Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from Handle'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/handle/"
   title="Handle on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/handle.svg"
       alt="Handle Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile Handle

Each block below is one kind of artifact we hold for Handle. 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.

Pricing Plans 1

Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.

Published pricing tiers and plan structures.

Handle Plans Pricing

0 plans

PLANS

Rate Limits 1

Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.

Documented rate limits and quota policies.

Handle Rate Limits

0 limits

RATE LIMITS

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.

Handle Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Handle Vulnerability Disclosure

Hackerone · security.txt

SECURITY

Handle Trust Center

SOC 2 Type 1, SOC 2 Type 2

SECURITY

Resources

Every other property we hold for Handle — 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 2

Pagination, idempotency, versioning, errors, and events

Commercial 3

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/handle · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of Handle, 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.