75F

75F is an IoT-based building management and automation company (Burnsville, Minnesota; acquired by Carrier Global in July 2026) whose vertically integrated platform pairs wireless sensors, thermostats and Central Control Units with cloud software — Facilisight, Portfolio Analytics, Hayloft and Saffron AI — to control and optimize HVAC, lighting and equipment in commercial buildings. Its developer surface is a Project Haystack-compliant REST API published through an Azure API Management gateway at api.75f.io, exposing Haystack ops (read, hisReadMany, pointWrite, hisWriteMany) over Haystack-tagged JSON and ZINC grids, plus a v2 Special Schedules API for exception-based scheduling. Access is OAuth 2.0 client-credentials bearer tokens layered on a product-scoped APIM subscription key, and integrators also reach the system over BACnet IP/MS-TP, Modbus and a Niagara driver.

75F is listed with 2 APIs on the APIs.io network. Tagged areas include Company, Building Automation, Smart Buildings, HVAC, and IoT.

75F’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, signup flow, changelog, and 24 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

39.9/100 developing ▬ flat Agent 9/100 agent aware Front door AI 3/6 light Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

2 APIs 2 Agent Skills

Company Building Automation Smart Buildings HVAC IoT Energy Management Project Haystack Facilities Management SensorsBuilding Management System

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 39.9/100 · developing

Contract Quality 0.0 / 21

Developer Ergonomics 11.2 / 17

Access Clarity 8.5 / 17

Operational Transparency 3.5 / 11

Contract Governance 1.9 / 10

Discoverability 5.6 / 9

Regulatory Posture 5.8 / 15

Agent readiness — 9/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Energy & Utilities regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/75f/"><img src="https://apis.io/badge/75f/card.svg" alt="75F on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

9 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Access Clarity scores 50.0 — up to +10.0 composite points
Contract Governance scores 18.2 — up to +9.8 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/75f/apis.yml: open an issue on github.com/api-evangelist/75f to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Building Automation (HVAC, BACnet, KNX, smart buildings)	standard	34.9 (thin)	-	1

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

75F Haystack API

75F's Project Haystack-compliant external REST API. Reads Haystack entity records by filter or by id (read), reads time-series history for many points at once (hisReadMany), and...

75F Special Schedules API

A v2 REST API for exception-based ("special") schedules applied at building or zone level — create, update and delete date-bounded occupancy overrides with mode and heating/cool...

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

read-building-data

AGENT SKILL

write-points-and-schedules

AGENT SKILL

75F API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

75F Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

75F Rate Limits

0 limits

RATE LIMITS

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

75F Authentication

oauth2/http/apiKey · 2 schemes

SECURITY

75F Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

75F Trust Center

SOC 2, VAPT

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

75F Scopes

2 scopes · clientCredentials

2 scopes

SCOPES

Resources

Get Started 5

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Login

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

AgentSkill

AgentSkill

X-MCPServerCandidate

X-MCPServerCandidate

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

ErrorCatalog

Conventions

Lifecycle

Conformance

DataModel

Build 1

SDKs, sample code, and the tooling you integrate with

IntegrationEdges

IntegrationEdges

Access & Security 5

Authentication, authorization, and security posture

Compliance

Authentication

OAuthScopes

DomainSecurity

TrustCenter

Operate 5

Status, limits, changes, and where to get help

Support

StatusPage

ChangeLog

ChangeLog

RateLimits

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 2

Properties that don't map to a standard resource type

Hosts

Hosts

Vendors

Vendors

Source (apis.yml)

aid: 75f
name: 75F
description: 75F is an IoT-based building management and automation company (Burnsville, Minnesota; acquired by Carrier Global
  in July 2026) whose vertically integrated platform pairs wireless sensors, thermostats and Central Control Units with cloud
  software — Facilisight, Portfolio Analytics, Hayloft and Saffron AI — to control and optimize HVAC, lighting and equipment
  in commercial buildings. Its developer surface is a Project Haystack-compliant REST API published through an Azure API Management
  gateway at api.75f.io, exposing Haystack ops (read, hisReadMany, pointWrite, hisWriteMany) over Haystack-tagged JSON and
  ZINC grids, plus a v2 Special Schedules API for exception-based scheduling. Access is OAuth 2.0 client-credentials bearer
  tokens layered on a product-scoped APIM subscription key, and integrators also reach the system over BACnet IP/MS-TP, Modbus
  and a Niagara driver.
url: https://raw.githubusercontent.com/api-evangelist/75f/refs/heads/main/apis.yml
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  probe_state: gated
  source:
  - authentication
  - scopes
  - rate-limits
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://www.datocms-assets.com/55631/1643443175-75f-logo.jpg?w=1000&fit=max&fm=jpg
x-type: company
x-source: harvest:secondary-market
x-tier: profiled
x-tier-reason: 'enrichment pass 2026-09-05: full contract discovery run; documented Project Haystack REST API, no public machine-readable
  spec'
specificationVersion: '0.20'
created: '2026-09-05'
modified: '2026-10-20'
position: Producing
tags:
- Company
- Building Automation
- Smart Buildings
- HVAC
- IoT
- Energy Management
- Project Haystack
- Facilities Management
- Sensors
- Building Management System
tags_raw:
- Company
- Building Automation
- Smart Buildings
- HVAC
- Internet of Things
- Energy Management
- Project Haystack
- Facilities Management
- Sensors
- Building Management System
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Hosts
  url: hosts/75f-hosts.yml
- type: IntegrationEdges
  url: integrations/75f-integration-edges.yml
- type: Vendors
  url: vendors/75f-vendors.yml
- type: Website
  url: https://www.75f.io/
- type: DeveloperPortal
  url: https://api-management-75f-dev.developer.azure-api.net/
- type: Documentation
  url: https://support.75f.io/hc/en-us/sections/5484889695123-API-s-for-Integrations
- type: APIReference
  url: https://support.75f.io/hc/en-us/articles/5459129016595-75F-External-API-s-Overview
- type: GettingStarted
  url: https://support.75f.io/hc/en-us/articles/5509604551443-Accessing-the-API
- type: Support
  url: https://support.75f.io/hc/en-us
- type: Blog
  url: https://www.75f.io/news/
- type: SignUp
  url: https://api-management-75f-dev.developer.azure-api.net/
- type: Login
  url: https://fs.75f.io/
- type: TermsOfService
  url: https://www.datocms-assets.com/55631/1648491708-75f-terms-of-service-pdf-2022.pdf
- type: PrivacyPolicy
  url: https://www.datocms-assets.com/55631/1650987646-75f-website-privacy-notice-march-2022.pdf
- type: StatusPage
  url: https://75f.statuspage.io/
- type: ChangeLog
  url: https://support.75f.io/hc/en-us/categories/11037028410771-Feature-Release-History
- type: Compliance
  url: https://www.75f.io/software/security/
- type: Authentication
  url: authentication/75f-authentication.yml
- type: OAuthScopes
  url: scopes/75f-scopes.yml
- type: ErrorCatalog
  url: errors/75f-problem-types.yml
- type: Conventions
  url: conventions/75f-conventions.yml
- type: Lifecycle
  url: lifecycle/75f-lifecycle.yml
- type: ChangeLog
  url: changelog/75f-changelog.yml
- type: Conformance
  url: conformance/75f-conformance.yml
- type: DomainSecurity
  url: security/75f-domain-security.yml
- type: RateLimits
  url: rate-limits/75f-rate-limits.yml
- type: DataModel
  url: data-model/75f-data-model.yml
- type: Sandbox
  url: sandbox/75f-sandbox.yml
- type: AgentSkill
  url: skills/_index.yml
- type: X-MCPServerCandidate
  url: mcp/75f-mcp.yml
- type: TrustCenter
  url: security/75f-trust-center.yml
apis:
- name: 75F Haystack API
  description: 75F's Project Haystack-compliant external REST API. Reads Haystack entity records by filter or by id (read),
    reads time-series history for many points at once (hisReadMany), and writes to writable points and historized points (pointWrite,
    hisWriteMany). Requests carry an OAuth 2.0 bearer token plus a product-scoped Ocp-Apim-Subscription-Key; responses are
    Haystack grids in JSON or ZINC.
  humanURL: https://support.75f.io/hc/en-us/articles/5459129016595-75F-External-API-s-Overview
  baseURL: https://api.75f.io/ph
  image: https://www.datocms-assets.com/55631/1643443175-75f-logo.jpg?w=1000&fit=max&fm=jpg
  tags:
  - Project Haystack
  - Building Data
  - Time Series
  - Building Automation
  properties:
  - type: Documentation
    url: https://support.75f.io/hc/en-us/sections/5484889695123-API-s-for-Integrations
  - type: APIReference
    url: https://support.75f.io/hc/en-us/articles/5460066903827-Read-API
  - type: GettingStarted
    url: https://support.75f.io/hc/en-us/articles/5509604551443-Accessing-the-API
  aid: 75f:75f-haystack-api
- name: 75F Special Schedules API
  description: A v2 REST API for exception-based ("special") schedules applied at building or zone level — create, update
    and delete date-bounded occupancy overrides with mode and heating/cooling setpoints, with conflict and validation rules
    enforced server-side. OAuth 2.0 bearer token with schedules:read and schedules:write scopes.
  humanURL: https://support.75f.io/hc/en-us/articles/45325600917651-Special-Schedules-Via-API
  baseURL: https://api.75f.io/v2
  image: https://www.datocms-assets.com/55631/1643443175-75f-logo.jpg?w=1000&fit=max&fm=jpg
  tags:
  - Scheduling
  - Building Automation
  - HVAC
  properties:
  - type: APIReference
    url: https://support.75f.io/hc/en-us/articles/45325600917651-Special-Schedules-Via-API
  aid: 75f:75f-special-schedules-api
x-enrichment:
  date: '2026-10-20'
  status: nochange
  artifacts_added: 0
  pass: local-v5
x-coverage:
  state: gated
  reason: partner-login
  detail: 75F documents its Haystack and Special Schedules APIs in public support articles but publishes no anonymous machine-readable
    contract; the OpenAPI sits behind Azure APIM portal registration.
  evidence:
  - url: https://api.75f.io/openapi.json
    status: 404
  - url: https://www.75f.io/
    status: 200
  checked: '2026-10-20'

75F API — frequently asked questions

Does 75F have an API?

Yes. APIs.io lists 2 APIs from 75F, including 75F Haystack API and 75F Special Schedules API.

How do I authenticate with the 75F API?

75F uses bearer-token authentication (oauth2/http/apiKey · 2 schemes). The details are profiled on APIs.io as 75F Authentication.

Is the 75F API ready for AI agents?

75F has a Kin Score of 39.9 out of 100 (developing) and an Agent Readiness score of 8.8 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/75f"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/75f/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/75f/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.