VergeSense

VergeSense is the occupancy intelligence platform for corporate real estate and workplace teams. It combines first-party AI-powered area, entryway and infinity sensors with a cloud analytics platform (Meridian, including a Large Spatial Model) to measure how buildings, floors, neighborhoods and individual spaces are actually used. The public VergeSense API is a key-authenticated REST surface at api.vergesense.com covering buildings, floors, spaces, space types, detections, threshold crossings, hourly and aggregate occupancy metrics, hardware inventory (sensors and gateways), a Predict API built on the Large Spatial Model, and a fully managed webhook subscription surface that pushes space_report, space_availability and motion_detected events to customer endpoints. Collection responses follow the JSON:API specification, timestamps are ISO 8601, and the API is date-versioned (YYYY-MM-DD) via the vs-version request header. VergeSense also operates an OAuth-protected remote MCP server at mcp.vergesense.com for agent access.

VergeSense publishes 1 API on the APIs.io network. Tagged areas include Occupancy Intelligence, Workplace Analytics, Corporate Real Estate, PropTech, and IoT Sensors.

The VergeSense catalog on APIs.io includes 1 event-driven AsyncAPI specification.

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

🌐 Visit website 📡 Source on GitHub
52.0/100 developing Agent 38/100 agent ready Full breakdown ↓
scored 2026-09-02 · rubric v0.18.0
1 APIs 1 MCP Servers
Occupancy IntelligenceWorkplace AnalyticsCorporate Real EstatePropTechIoT SensorsBuilding DataSpace UtilizationFacilities ManagementSmart BuildingsWebhooksMCPJSON:API

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-02 · rubric v0.18.0
Composite quality — 52.0/100 · developing
Contract Quality 15.9 / 25
Developer Ergonomics 12.7 / 20
Access Clarity 6.8 / 20
Operational Transparency 7.5 / 13
Contract Governance 2.2 / 12
Discoverability 6.9 / 10
Agent readiness — 38/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 7 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 6 / 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 5 / 5
Registration Without a Human 0 / 6
Agentic Commerce Surface 0 / 5
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 github.com/api-evangelist/vergesense: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

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

VergeSense API

REST and webhook API for the VergeSense Cloud occupancy intelligence platform. Read buildings, floors, spaces, space types, neighborhoods, space groups, detections and threshold...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

VergeSense MCP Server

MCP SERVER

Pricing Plans 1

Published pricing tiers and plan structures.

Vergesense Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Vergesense Rate Limits

1 limits

RATE LIMITS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Vergesense Webhooks

ASYNCAPI

Examples 1

Example request and response payloads for these APIs.

Vergesense Api Examples

3 fields

EXAMPLE

Security Posture 2

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

Vergesense Authentication

apiKey/oauth2 · 2 schemes

SECURITY

Vergesense Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Vergesense Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal
DeveloperPortal
 GettingStarted
GettingStarted
 SignUp
SignUp
 Login
Login

Documentation 2

Reference material describing how the API behaves

Documentation
Documentation
 APIReference
APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt
LLMsTxt
 WellKnown
WellKnown
 MCPServer
MCPServer
 AgentSkill
AgentSkill

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

ErrorCatalog
ErrorCatalog
 Conventions
Conventions
 Lifecycle
Lifecycle
 Conformance
Conformance
 DataModel
DataModel
 Webhooks
Webhooks

Build 5

SDKs, sample code, and the tooling you integrate with

Postman
Postman
 GitHubOrganization
GitHubOrganization
 Examples
Examples
 Packages
Packages
 ToolCrosswalk
ToolCrosswalk

Access & Security 3

Authentication, authorization, and security posture

Authentication
Authentication
 OAuthScopes
OAuthScopes
 DomainSecurity
DomainSecurity

Operate 5

Status, limits, changes, and where to get help

ChangeLog
ChangeLog
 Support
Support
 RateLimits
RateLimits
 Deprecation
Deprecation
 ChangeLog
ChangeLog

Commercial 3

Pricing, plans, and the legal terms of use

TermsOfService
TermsOfService
 PrivacyPolicy
PrivacyPolicy
 Plans
Plans

Company 2

The organization behind the API

Website
Website
 Blog
Blog

Source (apis.yml)

apis.yml Raw ↑ 
aid: vergesense
name: VergeSense
description: VergeSense is the occupancy intelligence platform for corporate real estate and workplace teams. It combines
  first-party AI-powered area, entryway and infinity sensors with a cloud analytics platform (Meridian, including a Large
  Spatial Model) to measure how buildings, floors, neighborhoods and individual spaces are actually used. The public VergeSense
  API is a key-authenticated REST surface at api.vergesense.com covering buildings, floors, spaces, space types, detections,
  threshold crossings, hourly and aggregate occupancy metrics, hardware inventory (sensors and gateways), a Predict API built
  on the Large Spatial Model, and a fully managed webhook subscription surface that pushes space_report, space_availability
  and motion_detected events to customer endpoints. Collection responses follow the JSON:API specification, timestamps are
  ISO 8601, and the API is date-versioned (YYYY-MM-DD) via the vs-version request header. VergeSense also operates an OAuth-protected
  remote MCP server at mcp.vergesense.com for agent access.
image: https://www.vergesense.com/hubfs/assets/logo/vergesense-logo--color.png
url: https://raw.githubusercontent.com/api-evangelist/vergesense/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.20'
created: '2026-09-02'
modified: '2026-09-02'
tags:
- Occupancy Intelligence
- Workplace Analytics
- Corporate Real Estate
- PropTech
- IoT Sensors
- Building Data
- Space Utilization
- Facilities Management
- Smart Buildings
- Webhooks
- MCP
- JSON:API
apis:
- aid: vergesense-api
  name: VergeSense API
  description: REST and webhook API for the VergeSense Cloud occupancy intelligence platform. Read buildings, floors, spaces,
    space types, neighborhoods, space groups, detections and threshold crossings; pull hourly and aggregate occupancy, utilization
    and headcount metrics at portfolio, building, floor, neighborhood, space-type, space-group and space level; inventory
    sensors and gateways; call the Predict API (space usage, space shortage, normalized space type distribution) built on
    the VergeSense Large Spatial Model; and create, patch, enable, disable, delete and inspect the delivery logs of webhooks
    that push space_report, space_availability and motion_detected events.
  humanURL: https://vergesense.readme.io/reference/reference-getting-started
  baseURL: https://api.vergesense.com
  tags:
  - Occupancy Intelligence
  - Workplace Analytics
  - Building Data
  - Space Utilization
  - IoT Sensors
  - Webhooks
  properties:
  - type: OpenAPI
    url: openapi/vergesense-api-openapi.json
  - type: Overlay
    url: overlays/vergesense-api-overlay.yaml
  - type: Documentation
    url: https://vergesense.readme.io/reference/reference-getting-started
  - type: APIReference
    url: https://vergesense.readme.io/reference/buildings-1
  - type: GettingStarted
    url: https://vergesense.readme.io/reference/reference-getting-started
  - type: Postman
    url: https://documenter.getpostman.com/view/6835591/2s9Y5Wx3QL
  - type: Authentication
    url: authentication/vergesense-authentication.yml
  - type: RateLimits
    url: rate-limits/vergesense-rate-limits.yml
  - type: ErrorCatalog
    url: errors/vergesense-problem-types.yml
  - type: Examples
    url: examples/vergesense-api-examples.json
  - type: Webhooks
    url: asyncapi/vergesense-webhooks.yml
  - type: DataModel
    url: data-model/vergesense-data-model.yml
  - type: Conventions
    url: conventions/vergesense-conventions.yml
  - type: ChangeLog
    url: changelog/vergesense-changelog.yml
  - type: MCPServer
    url: mcp/vergesense-mcp.yml
  - type: ToolCrosswalk
    url: mcp/vergesense-tool-crosswalk.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://www.vergesense.com/
- type: DeveloperPortal
  url: https://vergesense.readme.io/
- type: Documentation
  url: https://vergesense.readme.io/reference/reference-getting-started
- type: APIReference
  url: https://vergesense.readme.io/reference/buildings-1
- type: GettingStarted
  url: https://vergesense.readme.io/reference/reference-getting-started
- type: Postman
  url: https://documenter.getpostman.com/view/6835591/2s9Y5Wx3QL
- type: ChangeLog
  url: https://headwayapp.co/vergesense-changelog/
- type: Blog
  url: https://www.vergesense.com/resources/blog
- type: Support
  url: https://support.vergesense.com/hc/en-us
- type: SignUp
  url: https://cloud.vergesense.com/
- type: Login
  url: https://cloud.vergesense.com/
- type: TermsOfService
  url: https://www.vergesense.com/legal
- type: PrivacyPolicy
  url: https://www.vergesense.com/privacy-policy
- type: GitHubOrganization
  url: https://github.com/vergesense
- type: Authentication
  url: authentication/vergesense-authentication.yml
- type: OAuthScopes
  url: scopes/vergesense-scopes.yml
- type: RateLimits
  url: rate-limits/vergesense-rate-limits.yml
- type: ErrorCatalog
  url: errors/vergesense-problem-types.yml
- type: Examples
  url: examples/vergesense-api-examples.json
- type: Conventions
  url: conventions/vergesense-conventions.yml
- type: Lifecycle
  url: lifecycle/vergesense-lifecycle.yml
- type: Deprecation
  url: lifecycle/vergesense-lifecycle.yml
- type: ChangeLog
  url: changelog/vergesense-changelog.yml
- type: Conformance
  url: conformance/vergesense-conformance.yml
- type: DataModel
  url: data-model/vergesense-data-model.yml
- type: Webhooks
  url: asyncapi/vergesense-webhooks.yml
- type: Packages
  url: packages/vergesense-packages.yml
- type: Plans
  url: plans/vergesense-plans-pricing.yml
- type: LLMsTxt
  url: llms/vergesense-llms.txt
- type: WellKnown
  url: well-known/vergesense-well-known.yml
- type: MCPServer
  url: mcp/vergesense-mcp.yml
- type: ToolCrosswalk
  url: mcp/vergesense-tool-crosswalk.yml
- type: AgentSkill
  url: skills/_index.yml
- type: DomainSecurity
  url: security/vergesense-domain-security.yml
x-enrichment:
  date: '2026-09-02'
  status: enriched
  artifacts_added: 26
  pass: local-v1

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/vergesense"
All providers 
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose 
curl "https://apis.io/api/v1/providers/vergesense/operations?limit=25"
How their score was established 
curl "https://apis.io/api/v1/providers/vergesense/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

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